_ registry / mcp streamable-http · checked 2h ago

prax-data-services

https://mcp.orabrain.com

Registry code: eaabe8223a1cf9d7

api record

Prax intel: screen_wallet, analyze_transaction, screen_transfer, screen_entity, search, get_alerts (approved, last 24h; Business plan). Scores and references only. Output is licensed for use inside the caller's own product only: no resale, redistribution, training or competing use (Terms: https://mcp.orabrain.com/portal/terms).

endpoint
https://mcp.orabrain.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is prax-data-services live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is prax-data-services free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does prax-data-services have?
9 tools: fetch, screen_wallet, screen_transfer, screen_entity, screen_wallets_batch, screen_transfers_batch, search, analyze_transaction, ….
Is prax-data-services safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
247ms

last good check

priced tools
0

of 9 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 9 tools
1 auth-required 8 never probed 1 of 9 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_alerts auth-required 2h ago

    Threat-intelligence alert feed: approved Prax alerts from the last 24 hours (new exploits, attacker wallets, malicious contracts, phishing campaigns, sanctions updates), newest first, same payload as the webhook feed. Use for SOC / compliance monitoring and watchlist updates. Business plan and above; 100 credits per pull.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "default": 50
    },
    "cursor": {
      "type": "string"
    },
    "severity": {
      "type": "string"
    },
    "since_hours": {
      "type": "integer",
      "default": 24,
      "maximum": 24
    }
  }
}
    arguments 20 lines
  • fetch unknown 2h ago

    Fetch the full Prax intelligence record for an id returned by search (address:<chain>:<addr>, tx:<chain>:<hash>, alert:<id>). Business plan and above.

    mcp-tool

    {
  "type": "object",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string"
    }
  }
}
    arguments 11 lines
  • screen_wallet unknown never probed

    Wallet and smart-contract risk screening (KYT / AML): check any EVM address against Prax threat intelligence - OFAC and global sanctions, exploits, hacks, phishing, scams, drainers, mixers, malicious contracts, and first-hop exposure to them. Returns risk band, labels, roles, alerts naming it, counterparties and a plain-language story. Use before onboarding, paying or interacting with an address. Free plan. Set live=true for live on-chain screening too.

    mcp-tool

    {
  "type": "object",
  "required": [
    "address"
  ],
  "properties": {
    "live": {
      "type": "boolean",
      "default": false,
      "description": "also run live chain screening (slower)"
    },
    "chain": {
      "type": "string",
      "default": "eth"
    },
    "address": {
      "type": "string"
    }
  }
}
    arguments 20 lines
  • screen_transfer unknown never probed

    Pre-signature transfer check (payment screening): is it safe to send `amount` of `asset` from `from` to `to`? Returns allow / review / block with reasons - sanctioned or flagged parties, malicious or scam token, look-alike address poisoning, first-time payee. Works before the transaction exists; no chain lookup needed. Use in wallet, custody, payment and treasury flows. Builder plan and above.

    mcp-tool

    {
  "type": "object",
  "required": [
    "from",
    "to"
  ],
  "properties": {
    "to": {
      "type": "string",
      "description": "recipient address"
    },
    "from": {
      "type": "string",
      "description": "sender address"
    },
    "asset": {
      "type": "string",
      "default": "native",
      "description": "'native' or token contract address"
    },
    "chain": {
      "type": "string",
      "default": "eth"
    },
    "amount": {
      "type": "number",
      "description": "in the asset's own units"
    }
  }
}
    arguments 30 lines
  • screen_entity unknown never probed

    Sanctions screening for people, companies, vessels and crypto addresses: fuzzy name match (aliases, transliterations) or exact wallet / contract lookup against the OFAC SDN and other sanctions lists Prax tracks. Returns match / possible_match / no_match with hits (entity, type, programs, list, aliases, linked crypto addresses, score). Use for KYC / KYB onboarding and payment screening. Free plan.

    mcp-tool

    {
  "type": "object",
  "required": [
    "name"
  ],
  "properties": {
    "name": {
      "type": "string"
    },
    "type": {
      "type": "string",
      "description": "optional: individual, entity, vessel, aircraft"
    },
    "limit": {
      "type": "integer",
      "default": 10,
      "maximum": 25
    }
  }
}
    arguments 20 lines
  • screen_wallets_batch unknown never probed

    Bulk wallet screening: screen_wallet for up to 50 addresses in one call - portfolio, customer-base or deposit-address sweeps. Returns per-address risk band and labels plus a summary. Builder plan and above; 10 credits per call.

    mcp-tool

    {
  "type": "object",
  "required": [
    "addresses"
  ],
  "properties": {
    "chain": {
      "type": "string",
      "default": "eth"
    },
    "addresses": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "maxItems": 100
    }
  }
}
    arguments 19 lines
  • screen_transfers_batch unknown never probed

    Bulk transfer screening: screen_transfer for up to 50 transfers in one call (items of {from, to, amount, asset, chain}) - payout batches, payroll, exchange withdrawals. Returns a verdict per item and a summary. Builder plan and above; 10 credits per call.

    mcp-tool

    {
  "type": "object",
  "required": [
    "items"
  ],
  "properties": {
    "items": {
      "type": "array",
      "items": {
        "type": "object"
      },
      "maxItems": 100
    }
  }
}
    arguments 15 lines
  • search unknown never probed

    Search Prax threat intelligence in plain words (e.g. 'critical attacker wallets on base this week', 'phishing contracts created by 0x...'). Returns COUNTS of matching addresses (by band, chain, role) plus approved alerts from the last 24 h; address lists are not enumerable - look a specific address up with screen_wallet. Filters: chain (eth, base...), risk band (critical, high), role (attacker wallet, malicious contract, deployer, funding ancestry, clone), period (today, last 7 days, since 2026-10-01), free text (bytecode clone, phishing), 'created by 0x...', 'counterparties of 0x...'. An exact address or tx hash returns that record's id. Use fetch(id) for the full record. Business plan and above.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "default": 25,
      "maximum": 50
    },
    "query": {
      "type": "string"
    }
  }
}
    arguments 16 lines
  • analyze_transaction unknown 2h ago

    Transaction risk analysis: given an EVM transaction hash, returns status, value, counterparties and the risk of both sides (sanctions, exploit, phishing, scam exposure) with flags. Use for post-trade monitoring, incident triage and fraud investigation. Builder plan and above.

    mcp-tool

    {
  "type": "object",
  "required": [
    "hash"
  ],
  "properties": {
    "hash": {
      "type": "string"
    },
    "chain": {
      "type": "string",
      "default": "eth"
    }
  }
}
    arguments 15 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id eaabe8223a1cf9d7.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/eaabe8223a1cf9d7/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/eaabe8223a1cf9d7/badge.svg)](https://brick.blue/agent/eaabe8223a1cf9d7?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.