Security & Testing

onyxprotocol.trade

Provides risk screening and compliance checks for cryptocurrency addresses, including sanctions, blacklists, and fraud detection.

x402 supported1 endpoint8 known toolsFirst detected August 29, 2026Last detected August 29, 2026

ENDPOINT 1

https://onyxprotocol.trade/mcp

No auth detected

MCP server metadata

Name: onyx-aml
Version: 1.0.0

Capabilities

tools

Server instructions

Screen a crypto address before sending funds to it. Start with onyx_decide: it returns allow, review or deny against a policy you provide, instead of raw data you have to interpret. A green result means no public risk markers were found; it is not a guarantee that funds are clean, and every response repeats that. Paid operations need an API key: call onyx_payment_info to see how to get one by paying on chain, with no account and no signup.

Known tools 8

onyx_decide

Return allow / review / deny for a counterparty address against your own risk policy, with the reasons named.

Inferred read-only

onyx_screen

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.

Inferred read-only

onyx_screen_batch

Screen up to 50 addresses in a single call, for example before a mass payout.

Inferred read-only

onyx_preflight

Operational safety check for a payment, separate from risk screening.

Potential side effects

onyx_trace

Multi-hop trace of outgoing flows from an address, with attribution where a node is known (exchange labels, deposit addresses).

Inferred read-only

onyx_watch

Subscribe to an address.

Inferred read-only

onyx_balance

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

Inferred read-only

onyx_payment_info

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.

Potential side effects

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

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

Claude Code

.mcp.json

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

Claude Desktop

Settings → Connectors → Add custom connector

Name: onyx-aml
Remote MCP URL: https://onyxprotocol.trade/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

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

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

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

Generic MCP

Client-specific MCP configuration

{
  "name": "onyx-aml",
  "transport": "streamable-http",
  "url": "https://onyxprotocol.trade/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.