Onyx AML
REMOTE · ONYXPROTOCOL.TRADE
Crypto address risk checks for agents: USDT/USDC blacklists, sanctions, scam lists, poisoning
Available components
Last scanned (17 hours ago)
Scores higher than 55% of remote servers
Reachable. Last reached 22 Oct 2026.
Category Crypto and Web3
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
- Authorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 813 tokens (~101/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 90% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 20 Oct 26 65
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 22 Oct 2026 · Probed https://onyxprotocol.trade/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=onyxprotocol.trade | CN=YE2,O=Let's Encrypt,C=US | 2 Oct 2026 | 31 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 6d29d122ab1c10b45befb8b0cd76ef91c6d |
| SANs: onyxprotocol.trade, www.onyxprotocol.trade | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of onyxprotocol.trade. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| trade. | present | 64969 | 8 | Verified |
| onyxprotocol.trade. | 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 |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://onyxprotocol.trade/mcp | Verified | 200 | |
| http (plaintext) | http://onyxprotocol.trade/mcp | HTTPS enforced | 301 | https://onyxprotocol.trade/mcp |
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 →
onyx_balance Check remaining credit ~25
How much credit your API key has left, and the current prices. Free.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
onyx_decide Decide whether to transact with an address ~142
Return allow / review / deny for a counterparty address against your own risk policy, with the reasons named. Use this before every outbound transfer. Checks issuer blacklists (USDT, USDC), sanctions across six EVM chains plus the OFAC list, open scam databases, community reports and behavioural patterns. Costs credit.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Blockchain address (TRON, Ethereum or other EVM, Solana) |
| amount_usd | number | – | Amount you intend to send, in USD. Used only if your policy caps amounts. |
| policy | object | – | Optional. Omit for a conservative default that returns review for anything unknown. |
No output schema declared.
No examples provided.
onyx_payment_info How to pay and get an API key ~58
Machine-readable payment terms: which asset and network to send, the address, prices per operation, and how to claim an API key from the address you paid from. No account or signup is involved. Free, and works without a key.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
onyx_preflight Check this is the address you mean, before paying ~171
Operational safety check for a payment, separate from risk screening. Detects address poisoning (a lookalike planted in your history so it gets copied instead of the real address), contract recipients that would swallow the tokens, and addresses that behave differently on different chains. Pass known_addresses (the counterparties you already use) to enable poisoning detection. In our live-traffic sample this class of loss came up far more often than sanctioned counterparties. Dedicated transaction-security services cover part of it; no AML screening does. Run this together with onyx_decide before every payment.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Blockchain address (TRON, Ethereum or other EVM, Solana) |
| known_addresses | array | – | Addresses you have used before, so a lookalike can be spotted. Strongly recommended. |
No output schema declared.
No examples provided.
onyx_screen Screen one address ~80
Return the raw risk markers for one address: risk zone, issuer blacklists, sanctions coverage, scam databases, community reports, address age, balance and exchange attribution where known. Use this when you want the facts rather than a decision. Costs credit.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Blockchain address (TRON, Ethereum or other EVM, Solana) |
No output schema declared.
No examples provided.
onyx_screen_batch Screen many addresses at once ~64
Screen up to 50 addresses in a single call, for example before a mass payout. Priced per address, and only addresses actually screened are charged. Each result carries facts_complete so you can tell whether the behavioural facts finished loading.
| Name | Type | Req | Description |
|---|---|---|---|
| addresses | array | yes | – |
No output schema declared.
No examples provided.
onyx_trace Trace where funds went ~70
Multi-hop trace of outgoing flows from an address, with attribution where a node is known (exchange labels, deposit addresses). Use it to establish provenance after receiving funds. Costs more than a screening call.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Blockchain address (TRON, Ethereum or other EVM, Solana) |
No output schema declared.
No examples provided.
onyx_watch Watch an address and get a webhook when it turns toxic ~104
Subscribe to an address. When it enters an issuer blacklist, a sanctions list or a scam database, we POST a signed event to your callback URL. A one-off check cannot warn you about a freeze that has not happened yet. Billed per address per day. The callback must be public https.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Blockchain address (TRON, Ethereum or other EVM, Solana) |
| callback_url | string | yes | Public https URL to receive events |
No output schema declared.
No examples provided.
How do I install the Onyx AML MCP server?
Onyx AML is a hosted endpoint at https://onyxprotocol.trade/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 · onyxprotocol.trade
claude mcp add --transport http trade-onyxprotocol-onyx-aml 'https://onyxprotocol.trade/mcp'
What is the Onyx AML MCP server?
Onyx AML is an MCP server listed in the public MCP registry as trade.onyxprotocol/onyx-aml. Crypto address risk checks for agents: USDT/USDC blacklists, sanctions, scam lists, poisoning. This page covers its hosted endpoint (https://onyxprotocol.trade/mcp).
Is the Onyx AML MCP server safe to use?
Onyx AML scores 66 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 Onyx AML MCP server expose?
Onyx AML exposes 8 tools: onyx_decide, onyx_screen, onyx_screen_batch, onyx_preflight, onyx_trace, and 3 more. Their descriptions and schemas cost roughly 714 tokens of context every time the server is loaded.
Does the Onyx AML MCP server require authentication?
No. We connected to Onyx AML without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Onyx AML MCP server still maintained?
Onyx AML is still listed as active in the MCP registry. We last reached this channel on 22 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.