# Onyx AML (remote · onyxprotocol.trade)

Crypto address risk checks for agents: USDT/USDC blacklists, sanctions, scam lists, poisoning

- Trust score: 66/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-22

## Components

- remote · `onyxprotocol.trade`: 66/100 (this document), [markdown](https://verifymcp.io/servers/trade-onyxprotocol-onyx-aml/onyxprotocol.md), [page](https://verifymcp.io/servers/trade-onyxprotocol-onyx-aml/onyxprotocol)

## Channel facts

- Endpoint: `https://onyxprotocol.trade/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-22.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 74/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 813 tokens (~101/item across 8 items; 8 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 7/100
  - Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 97/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 90% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http trade-onyxprotocol-onyx-aml 'https://onyxprotocol.trade/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "trade-onyxprotocol-onyx-aml": {
      "url": "https://onyxprotocol.trade/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "trade-onyxprotocol-onyx-aml": {
      "type": "http",
      "url": "https://onyxprotocol.trade/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.trade-onyxprotocol-onyx-aml]
url = "https://onyxprotocol.trade/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "trade-onyxprotocol-onyx-aml": {
      "type": "remote",
      "url": "https://onyxprotocol.trade/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add trade-onyxprotocol-onyx-aml --url 'https://onyxprotocol.trade/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  trade-onyxprotocol-onyx-aml:
    url: "https://onyxprotocol.trade/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "trade-onyxprotocol-onyx-aml": {
      "Transport": "http",
      "Url": "https://onyxprotocol.trade/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add trade-onyxprotocol-onyx-aml -t streamable-http -u 'https://onyxprotocol.trade/mcp'
```

### Other

```json
{
  "mcpServers": {
    "trade-onyxprotocol-onyx-aml": {
      "type": "http",
      "url": "https://onyxprotocol.trade/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-22 (score 66, +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.

### 2026-10-21 (score 65, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-20 (score 65)

First indexed and scored.

## MCP tools (8)

### `onyx_decide` (~142 tokens)

Decide whether to transact with an address

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.

Input parameters:

- `address` (string, required): 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.

### `onyx_screen` (~80 tokens)

Screen one address

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.

Input parameters:

- `address` (string, required): Blockchain address (TRON, Ethereum or other EVM, Solana)

### `onyx_screen_batch` (~64 tokens)

Screen many addresses at once

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.

Input parameters:

- `addresses` (array, required)

### `onyx_preflight` (~171 tokens)

Check this is the address you mean, before paying

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.

Input parameters:

- `address` (string, required): Blockchain address (TRON, Ethereum or other EVM, Solana)
- `known_addresses` (array): Addresses you have used before, so a lookalike can be spotted. Strongly recommended.

### `onyx_trace` (~70 tokens)

Trace where funds went

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.

Input parameters:

- `address` (string, required): Blockchain address (TRON, Ethereum or other EVM, Solana)

### `onyx_watch` (~104 tokens)

Watch an address and get a webhook when it turns toxic

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.

Input parameters:

- `address` (string, required): Blockchain address (TRON, Ethereum or other EVM, Solana)
- `callback_url` (string, required): Public https URL to receive events

### `onyx_balance` (~25 tokens)

Check remaining credit

How much credit your API key has left, and the current prices. Free.

### `onyx_payment_info` (~58 tokens)

How to pay and get an API key

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.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/trade-onyxprotocol-onyx-aml/onyxprotocol#diagnostics

## Score history

- 2026-10-22: 66
- 2026-10-21: 65
- 2026-10-20: 65

## Common questions

### 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.

## Links

- Remote endpoint: https://onyxprotocol.trade/mcp
- Website: https://onyxprotocol.trade/en/agents
- Changelog RSS feed: https://verifymcp.io/servers/trade-onyxprotocol-onyx-aml/onyxprotocol.xml
- Changelog JSON feed: https://verifymcp.io/servers/trade-onyxprotocol-onyx-aml/onyxprotocol.json
- HTML version of this page: https://verifymcp.io/servers/trade-onyxprotocol-onyx-aml/onyxprotocol