Skip to main content
Glama

Check crypto addresses against OFAC digital-currency sanctions

crypto_address_risk
Read-only

Screens up to 20 crypto addresses (EVM chains, Bitcoin, Solana, Tron, Litecoin, Monero, XRP, Zcash and more; 18 currencies) against the US Treasury OFAC Specially Designated Nationals (SDN) digital currency address list. Reports sanction status, list name, SDN program, and source link. Never declares an address clean: reports 'not on the checked lists'. Information only, not financial advice. Related tools on this server, for a different need: address_parse when you need to parse a postal address into parts and check the postcode. Price: $0.003 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "addresses": "<addresses>"
    },
    "name": "crypto_address_risk"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressesYesUp to 20 addresses, comma-separated (a JSON array also works in a POST-style client)

Output Schema

NameRequiredDescriptionDefault
noteNo
sourceNo
addressesNo
checkedAtNo
disclaimerNo
listsCheckedNo
screenedCountNo
sanctionedCountNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / addresses / description
      Previous value: -"Array of up to 20 cryptocurrency addresses to screen"New value: +"Up to 20 addresses, comma-separated (a JSON array also works in a POST-style client)"
    • addedOutput schema / properties / listsChecked
      Added value: +{}
    • addedOutput schema / properties / note
      Added value: +{}
  2. Added

TDQS

A4.6/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With annotations only covering read-only and open-world traits, the description adds substantial context: the 20-address cap, the reporting fields returned, and the important caveat that results never declare an address clean but report 'not on the checked lists'. It also discloses the billing model ($0.003 per successful call via x402, failures uncharged), which materially affects how an agent should batch and retry.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads what the tool does and what it returns before the caveat, pricing, and cross-reference, so the critical content is read first. The pricing and 'not financial advice' clauses add length but carry real decision value; only the mid-sentence sibling reference feels slightly tacked on.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter, read-only screening tool with an output schema already defining the return shape, everything an agent needs is present: eligibility scope, result semantics, a negative-result caveat, cost model, and a sibling redirect. Nothing material is left to inference.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100%, so baseline is 3; the description earns extra credit by bounding the parameter's scope (18 currencies across EVM, Bitcoin, Solana, Tron, Litecoin, Monero, XRP, Zcash) and confirming the comma-separated/JSON-array input form. That chain coverage information is meaning an agent needs in order to know whether a given address is even eligible.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Screens') plus resource ('up to 20 crypto addresses') and names the exact authority (US Treasury OFAC SDN digital currency address list) along with the supported chain families and 18-currency scope. It also explicitly separates itself from address_parse, so an agent can distinguish it without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a clear triggering context (checking addresses against OFAC sanctions) and explicitly redirects to address_parse for the unrelated postal-address-parsing need, preventing a plausible misfire. It stops short of stating when this tool is the wrong choice relative to the other crypto/sanctions-style siblings, but the positive guidance is unambiguous.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources