YourAITools MCP Hub

PayGuard: Sanctions check for one wallet

screen_address

Read-onlyIdempotent

Use for ONE wallet: is this address on the US Treasury OFAC SDN sanctions list (digital currency addresses, refreshed daily)? Any chain (BTC, ETH/EVM, TRX, SOL, LTC, XMR, BCH, XRP, ZEC and more). Returns sanctioned (true/false), match_count, matches[] (entity, programs, list_date), normalized address, chain guess and checksum, list_updated_at. Free: 30 calls/day per IP (max 10/min). Not for: lists of wallets (screen_batch) or a full counterparty risk check (check_counterparty). Informational, not legal advice.

[PayGuard via YourAITools MCP Hub] Free tier: same as PayGuard's own MCP server (call without payment and without tier). Paid: address $0.001 per call, with a credits key (Authorization: Bearer yatc_...) or x402 (USDC; the hub returns the payment terms). Failed tool calls aren't charged: credits are refunded automatically and x402 payments only settle on success.

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_address"
  }
}

Input Schema

Name	Required	Description	Default
`tier`	No	Paid tier: address $0.001. Omit tier (with no credits key or x402 payment) to use the free tier.
`address`	Yes	One blockchain address, e.g. "0x8589427373D6D84E98730D7795D8f6f8731FDA16" or "bc1qxy2kgdygjrsqtzq2n0yrf2493p83kkfjhx0wlh": 20-140 letters/digits, optional URI prefix such as "ethereum:" or "bitcoincash:" (stripped); EVM hex and bech32 match case-insensitively, base58 exactly. The chain is detected automatically. Any chain is accepted; the SDN list covers Bitcoin, Ethereum and other EVM chains (Base, Arbitrum, BNB Chain, Polygon...), Tron, Solana, Litecoin, Monero, Bitcoin Cash/SV/Gold, Dash, Dogecoin, Ethereum Classic, XRP, Verge, Zcash and USDT/USDC addresses.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 30, 2026
- addedInput schema / properties / address / examples
```
Added value: +[
+  "0x8589427373D6D84E98730D7795D8f6f8731FDA16"
+]
```
First observedOct 24, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds materially beyond them: list refresh cadence, free-vs-paid tier mechanics, per-call price, auth forms (credits key or x402), and a refund/no-charge-on-failure policy. It also flags the 'informational, not legal advice' caveat, which colors how results should be presented.

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?

The core purpose, scope, and exclusions are front-loaded in the first two sentences and the return shape is compact. The trailing hub/payment boilerplate is verbose but carries decision-relevant pricing and refund information, so it earns most of its space.

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?

No output schema exists, and the description compensates by enumerating the return fields (sanctioned, match_count, matches[] with entity/programs/list_date, normalized address, chain guess, checksum, list_updated_at). Combined with annotations and the full schema coverage, an agent has everything needed to call and interpret it.

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 100%, so the baseline is 3; the description nonetheless adds that the chain is auto-detected, any chain is accepted, and URI prefixes are stripped. The tier parameter is explained only indirectly through the pricing/free-tier paragraph rather than per-parameter, keeping it below 5.

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: a sanctions check of ONE address against the US Treasury OFAC SDN digital-currency list, with chain coverage and return fields named. It explicitly distinguishes itself from screen_batch (lists) and check_counterparty (full risk check), so an agent can route 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 Guidelines5/5

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

Explicit 'Use for ONE wallet' scoping plus a 'Not for:' clause naming both alternatives and the conditions that select them (lists of wallets, full counterparty risk check). Free-tier limits (30 calls/day, 10/min) further tell the agent when this call is viable.

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

All YourAITools MCP Hub tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?