Skip to main content
Glama

Safe-Send Check: crypto support triage, sanctions and scam screening

OFAC sanctions screening for crypto wallet addresses ($0.005)

screen_wallet_ofac_sanctions
Read-onlyIdempotent

Is this wallet sanctioned? Screens 1-20 addresses (EVM 0x on any chain, Bitcoin, TRON, Solana, Litecoin, XRP, Monero, Zcash, ...) against every digital-currency address on the US Treasury OFAC SDN list (18 asset lists, refreshed from the official data). Use before your agent sends, pays, accepts or onboards crypto. Exact match -> verdict match (do not transact). English + Chinese advice. Not legal advice. PAID: $0.005 per call or 5 prepaid credits, no account. Pay with x402 over MCP (USDC on Base), or with a credits key bought by a plain USDC transfer (credits_quote / credits_claim, then header Authorization: Bearer ssk_...). An unpaid call returns the payment terms and charges nothing; bad input is rejected before any payment; failed work is never charged. Same data as GET /v1/ofac-sanctions-check.

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": {
      "address": "<address>"
    },
    "name": "screen_wallet_ofac_sanctions"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesWallet address to screen (any chain; an ethereum:/bitcoin:/tron: URI prefix is stripped)
addressesNoOptional: more addresses, comma-separated (total max 20 per call)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations only cover read-only, idempotent, and open-world traits; the description adds substantial context beyond them: $0.005 pricing, x402 and prepaid-credit payment paths, unpaid calls returning terms without charge, bad input rejected before payment, failed work never charged, and the 'do not transact' verdict rule. That is exactly the behavioral detail an agent needs before invoking a paid tool.

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-loaded with the core question and scope, then usage timing, then payment mechanics. It is dense and much of the payment detail is necessary for a paid tool, though the string of parenthetical chains and payment instructions makes it slightly cramped rather than fully tight.

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

Completeness4/5

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

For a tool with no output schema, the description explains what a match means ('verdict match (do not transact)') and notes English plus Chinese advice, but does not describe the response shape for non-matches or per-address output. Given the tool's complexity and payment model, it is strong but not fully complete.

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

Parameters3/5

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

Schema description coverage is 100%, so both parameters are already documented, including the URI-prefix stripping and the 20-address cap. The description adds little parameter-specific meaning beyond restating the accepted chains and address volume, so baseline 3 applies.

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 and resource: screens wallet addresses against the US Treasury OFAC SDN digital-currency list. It adds scope details (1-20 addresses, EVM/Bitcoin/TRON/Solana/etc., 18 asset lists) that make it unmistakable against siblings like check_crypto_address_before_sending or screen_payout_recipient_list.

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?

Explicitly says when to use it: 'before your agent sends, pays, accepts or onboards crypto.' It does not name alternatives or state when another screening tool would be preferred, so it falls short of full when/when-not guidance.

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