Onyx AML

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

使うべきか

品質と安全性

A
説明の品質
96%
スキーマの完全性
80%
命名の品質
80%
ポイズニングのリスク
100%
権限の一致
100%
プロトコルへの準拠
100%

検出事項(1)

  • LOWTool 'onyx_balance' description lacks action verbonyx_balance 内

ツール定義とプロトコルへの準拠に関する自動分析に基づいています。

コンテキストコスト

~1,001トークン数(ツール定義)
~690 B一般的なレスポンスサイズ
注意への影響は中程度(128k コンテキストの 0.78%)

これは、サーバーのツールがモデルのコンテキストに読み込まれるたびに消費されるおおよそのトークン数です。数が多いほど、ほかのタスクに使える注意が減ります。

インストール

ワンクリックインストール

これを `claude_desktop_config.json` ファイルに追加してください:

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

リモートエンドポイント

https://onyxprotocol.trade/mcpstreamable-http

できること

ツール一覧

ツール(8)

🟢 読み取り専用🟡 書き込み🔴 削除⚪ 不明
⚪onyx_decide(address, amount_usd, policy)

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.

入力スキーマ

{
  "type": "object",
  "properties": {
    "address": {
      "type": "string",
      "description": "Blockchain address (TRON, Ethereum or other EVM, Solana)"
    },
    "amount_usd": {
      "type": "number",
      "description": "Amount you intend to send, in USD. Used only if your policy caps amounts."
    },
    "policy": {
      "type": "object",
      "description": "Optional. Omit for a conservative default that returns review for anything unknown.",
      "properties": {
        "deny_zones": {
          "type": "array",
          "items": {
            "type": "string"
          }
        },
        "review_zones": {
          "type": "array",
          "items": {
            "type": "string"
          }
        },
        "min_age_days": {
          "type": "integer"
        },
        "max_amount_usd": {
          "type": "number"
        }
      }
    }
  },
  "required": [
    "address"
  ]
}
⚪onyx_screen(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.

入力スキーマ

{
  "type": "object",
  "properties": {
    "address": {
      "type": "string",
      "description": "Blockchain address (TRON, Ethereum or other EVM, Solana)"
    }
  },
  "required": [
    "address"
  ]
}
⚪onyx_screen_batch(addresses)

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.

入力スキーマ

{
  "type": "object",
  "properties": {
    "addresses": {
      "type": "array",
      "items": {
        "type": "string",
        "description": "Blockchain address (TRON, Ethereum or other EVM, Solana)"
      },
      "maxItems": 50
    }
  },
  "required": [
    "addresses"
  ]
}
🟢onyx_preflight(address, known_addresses)

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.

入力スキーマ

{
  "type": "object",
  "properties": {
    "address": {
      "type": "string",
      "description": "Blockchain address (TRON, Ethereum or other EVM, Solana)"
    },
    "known_addresses": {
      "type": "array",
      "items": {
        "type": "string",
        "description": "Blockchain address (TRON, Ethereum or other EVM, Solana)"
      },
      "maxItems": 200,
      "description": "Addresses you have used before, so a lookalike can be spotted. Strongly recommended."
    }
  },
  "required": [
    "address"
  ]
}
⚪onyx_trace(address)

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.

入力スキーマ

{
  "type": "object",
  "properties": {
    "address": {
      "type": "string",
      "description": "Blockchain address (TRON, Ethereum or other EVM, Solana)"
    }
  },
  "required": [
    "address"
  ]
}
🟡onyx_watch(address, callback_url)

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.

入力スキーマ

{
  "type": "object",
  "properties": {
    "address": {
      "type": "string",
      "description": "Blockchain address (TRON, Ethereum or other EVM, Solana)"
    },
    "callback_url": {
      "type": "string",
      "description": "Public https URL to receive events"
    }
  },
  "required": [
    "address",
    "callback_url"
  ]
}
⚪onyx_balance

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

入力スキーマ

{
  "type": "object",
  "properties": {}
}
⚪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. No account or signup is involved. Free, and works without a key.

入力スキーマ

{
  "type": "object",
  "properties": {}
}

コミュニティ

このサーバーを評価する

エビデンス

最近の観測

検証済みバージョンは記録されていませんツール 8 件