mcpbeat Sign in

PayGuard MCP Server

answering

PayGuard is answering right now. Last checked 4 min ago. It exposes 2 tools.

OFAC SDN sanctions screen for crypto addresses, for agents that send payments. By Crypto Money Maker

Uptime history 4 days of history
4 days agonow
100.0%
Uptime 24h
92 of 92 checks
2
Tools
read from the server
77 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 10

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 23 October 2026. No other catalogue keeps this.

24 Oct 2 tool descriptions were rewritten screen_address, screen_batch
23 Oct 2 tool descriptions were rewritten5 times that day screen_address, screen_batch
23 Oct 2 tools changed the parameters they ask for screen_address, screen_batch
23 Oct a tool appeared screen_batch
and 3 more, back to 23 October 2026

Nothing serious here today

Today is the operative word: we check PayGuard every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 4 min ago.

run in your terminal
claude mcp add payguard --transport http https://api.youraitools.co/payguard/mcp
Settings → Connectors → Add custom connector, then paste this address
https://api.youraitools.co/payguard/mcp
~/.codex/config.toml
[mcp_servers.payguard]
url = "https://api.youraitools.co/payguard/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "payguard": {
      "url": "https://api.youraitools.co/payguard/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "payguard": {
      "type": "http",
      "url": "https://api.youraitools.co/payguard/mcp"
    }
  }
}

Available tools 2

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

screen
screen_address
Checks one crypto address against the US Treasury OFAC SDN list of sanctioned digital currency addresses (refreshed daily). For 2 or more addresses use screen_batch (up to 50 per call, counts as one call). Accepts any chain (BTC, ETH and EVM chains, TRX, SOL, LTC, XMR, BCH, XRP, ZEC and more). Free: 30 calls/day per IP with full results (max 10/min; invalid input is not counted); after that the tool returns an error with the x402 pay URL ($0.001 USDC on Base, Polygon, Arbitrum One or Solana per call at https://api.youraitools.co/payguard/v1/address) or prepaid credits. Returns sanctioned (true/false), match_count, matches[] (entity, entity_type, programs, list_date, listed_currency), address (normalized), chain {guess, format, candidates, checksum_valid}, list_updated_at and free_tier usage. Read-only; informational screening, not legal advice.
screen_batch
Checks 1-50 crypto addresses against the US Treasury OFAC SDN list in one call (counts as one call). Use it instead of repeated screen_address calls whenever you have several addresses (payee lists, counterparties, transaction inputs/outputs); use screen_address for a single one. Mixed chains allowed; one invalid entry rejects the whole call. Free: 30 calls/day per IP with full results (max 10/min; invalid input is not counted); after that the tool returns an error with the x402 pay URL ($0.01 USDC on Base, Polygon, Arbitrum One or Solana per call at https://api.youraitools.co/payguard/v1/batch) or prepaid credits. Returns count, sanctioned_count, any_sanctioned, list_updated_at and results[] in input order, each {input, address, sanctioned, match_count, matches[], chain}. Read-only; informational screening, not legal advice.

Endpoints

URLTransportStateLatencyChecked
https://api.youraitools.co/payguard/mcp streamable-http answering 68 ms 4 min ago

Alternatives to PayGuard

same job, measured the same way
Payment Guard MCP
by mlawsonking

Pre-send risk check for AI agents that move money — screen an address or payment URL before sending.

36 installs/wk local only
CounterpartyCheck
by youraitools

Pre-payment check for EVM/Solana addresses: ok/caution/block with reasons. By Crypto Money Maker

389 installs/wk 1 tools answering
PkgGuard
by youraitools

Dependency scan for agents: known CVEs and malicious packages via OSV.dev. By Crypto Money Maker

419 installs/wk 2 tools answering
Publicaml
by publicaml

AML screening for crypto addresses: risk, sanctions, fund tracing and counterparties.

24 installs/wk local only
Pathguard
by cieltech-pathguard

Crypto transaction safety tool — screens addresses and transactions for scam risk.

5 tools answering
Aml
by oceanalt

Pre-payment checks for AI agents: sanctions and AML screening of payees, payment pages and requests.

318 installs/wk 13 tools answering
S
Sentinel
by 448c

Pay-per-call safety checks for AI agents: screen a crypto address or URL before you transact.

2 tools answering
PayPerScreen
by tonythetiger22

Sanctions, crypto wallet, email and IP screening for agents. Pay per check in USDC via x402.

64 installs/wk local only

PayGuard — questions

Answers built from our own checks of this server.

What can PayGuard do?
It exposes 2 tools, read directly from the server on our last check. Among them: screen_address, screen_batch. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is PayGuard working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 77 ms. The bar chart above shows every period we have measured.
How do I connect PayGuard?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does PayGuard need an API key?
No. PayGuard completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 2 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is PayGuard?
It answers our handshake in 77 ms on average, which is faster than 97% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.