Prax Data Services
REMOTE · MCP.ORABRAIN.COM
Screen EVM wallets, contracts and transactions against sanctions, exploit, phishing and scam intel.
Available components
Last scanned (3 hours ago)
Scores higher than 45% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Security
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability64
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1192 tokens (~132/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage75
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 26% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "screen_transfer" implies "transfer" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Fail
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 117 → 132 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- 30 Oct 26 61
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://mcp.orabrain.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=orabrain.com | CN=WE1,O=Google Trust Services,C=US | 17 Sept 2026 | 16 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 912109809d4945a40ea15684fedd50a2 |
| SANs: orabrain.com, *.orabrain.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.orabrain.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| orabrain.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.orabrain.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.orabrain.com/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
analyze_transaction Analyze transaction ~79
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.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | – |
| hash | string | yes | – |
No output schema declared.
No examples provided.
fetch Fetch intel record ~51
Fetch the full Prax intelligence record for an id returned by search (address:<chain>:<addr>, tx:<chain>:<hash>, alert:<id>). Business plan and above.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
get_alerts Threat-intel alerts (24h) ~102
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.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | – |
| limit | integer | – | – |
| severity | string | – | – |
| since_hours | integer | – | – |
No output schema declared.
No examples provided.
screen_entity Sanctions screening ~122
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| name | string | yes | – |
| type | string | – | optional: individual, entity, vessel, aircraft |
No output schema declared.
No examples provided.
screen_transfer Screen transfer (pre-sign) ~147
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.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | – | in the asset's own units |
| asset | string | – | 'native' or token contract address |
| chain | string | – | – |
| from | string | yes | sender address |
| to | string | yes | recipient address |
No output schema declared.
No examples provided.
screen_transfers_batch Screen transfers (batch) ~75
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.
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | – |
No output schema declared.
No examples provided.
screen_wallet Screen wallet / contract ~133
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
| chain | string | – | – |
| live | boolean | – | also run live chain screening (slower) |
No output schema declared.
No examples provided.
screen_wallets_batch Screen wallets (batch) ~72
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.
| Name | Type | Req | Description |
|---|---|---|---|
| addresses | array | yes | – |
| chain | string | – | – |
No output schema declared.
No examples provided.
search Search Prax intel ~194
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | – |
No output schema declared.
No examples provided.
How do I install the Prax Data Services MCP server?
Prax Data Services is a hosted endpoint at https://mcp.orabrain.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.orabrain.com
claude mcp add --transport http com-orabrain-prax-data-services 'https://mcp.orabrain.com/mcp'
What is the Prax Data Services MCP server?
Prax Data Services is an MCP server listed in the public MCP registry as com.orabrain/prax-data-services. Screen EVM wallets, contracts and transactions against sanctions, exploit, phishing and scam intel. This page covers its hosted endpoint (https://mcp.orabrain.com/mcp).
Is the Prax Data Services MCP server safe to use?
Prax Data Services scores 64 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Prax Data Services MCP server expose?
Prax Data Services exposes 9 tools: screen_wallet, analyze_transaction, screen_transfer, screen_entity, screen_wallets_batch, and 4 more. Their descriptions and schemas cost roughly 975 tokens of context every time the server is loaded.
Does the Prax Data Services MCP server require authentication?
No. We connected to Prax Data Services without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Prax Data Services MCP server still maintained?
Prax Data Services is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.