Check Payment Recipient MCP Server

by kgninja Your server? Claim it

answering

Check Payment Recipient is answering right now. Last checked 9 min ago. It exposes 5 tools.

Check a payment recipient before signing: sanctions, blocklist and anomaly rules. $0.05 via x402.

Uptime history 23 hours of history

23 hours agonow

100.0%

Uptime 24h

85 of 85 checks

Tools

read from the server

529 ms

Response time

average over 24h

open, no key

Access

streamable-http

What changed 1

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

7 Nov a tool appeared check_payment_batch

Nothing serious here today

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

Connect this server

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

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add check-payment-recipient --transport http https://check-payment-recipient.fuwafuwow.workers.dev/mcp

Settings → Connectors → Add custom connector, then paste this address

https://check-payment-recipient.fuwafuwow.workers.dev/mcp

~/.codex/config.toml

[mcp_servers.check-payment-recipient]
url = "https://check-payment-recipient.fuwafuwow.workers.dev/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "check-payment-recipient": {
      "url": "https://check-payment-recipient.fuwafuwow.workers.dev/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "check-payment-recipient": {
      "type": "http",
      "url": "https://check-payment-recipient.fuwafuwow.workers.dev/mcp"
    }
  }
}

Available tools 5

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

payment

check_payment_batch

Paid ($0.50, x402 v2 exact): batch pre-signing safety check — 1 to 20 payment checks in ONE paid call. Each item takes exactly the same fields as check_payment_recipient and gets its own decision; the result carries per-item decisions plus a summary {total, allow, escalate, block, input_error}. An item with invalid fields is reported per item as INPUT_ERROR and does not fail the batch. Envelope errors (missing batch idempotency_key, items not an array of 1-20) are returned before payment and are never charged. On an uncertain outcome, reuse the same batch idempotency_key; a replay returns the stored result without a new payment.

check_payment_recipient

Paid ($0.05, x402 v2 exact): pre-signing safety check of a planned payment. Returns allow / escalate / block with reasons, evidence and a verifiable receipt. Input errors are returned before payment and are never charged. On an uncertain outcome, reuse the same idempotency_key; a replay returns the stored receipt without a new payment.

capabilities

list_capabilities

Free discovery: price, networks, rule set and list coverage for check_payment_recipient.

ping

ping

Free health check.

receipt

get_receipt

Free: fetch a stored receipt by receipt_id or idempotency_key. Use it to reconcile an uncertain payment before ever paying again.

Endpoints

URL	Transport	State	Latency	Checked
https://check-payment-recipient.fuwafuwow.workers.dev/mcp	streamable-http	answering	556 ms	9 min ago

Alternatives to Check Payment Recipient

same job, measured the same way

X402 Payment Safety

by agenttanuki

Authorize x402 payments before signing with request-bound, signed safety decisions.

1 tools answering

Presidio Hardened X402 MCP

by presidio-v

Pre-payment safety gate for x402 agents: PII screening, spend policy, replay checks before signing.

139 installs/wk local only

Aml

by oceanalt

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

115 installs/wk 13 tools answering

PayPerScreen

by tonythetiger22

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

135 installs/wk local only

Hosannaith MCP

by cameron4316

Check x402 endpoint reliability on Algorand before an agent routes a payment there.

69 installs/wk local only

x402 Endpoint Check (Tanod)

by tanod

Check an x402 endpoint before you pay it, then test a payment and follow it to settlement.

3 tools answering

ReceiptRail

by xka0085-byte

Read-only on-chain receipt check for x402 payments; confirm settlement before trusting a tx.

3 tools answering

Factline

by snefhew

Checks before an agent pays: payees, webshops, invoices, payment files, companies, sanctions, PEP.

19 tools answering

Check Payment Recipient — questions

Answers built from our own checks of this server.

What can Check Payment Recipient do?

It exposes 5 tools, read directly from the server on our last check. Among them: check_payment_batch, check_payment_recipient, get_receipt, list_capabilities, ping. 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 Check Payment Recipient working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 85 of 85 checks got a reply (100.0%), average response time 529 ms. The bar chart above shows every period we have measured.

How do I connect Check Payment Recipient?

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 Check Payment Recipient need an API key?

No. Check Payment Recipient completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 5 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Check Payment Recipient?

It answers our handshake in 529 ms on average, which is faster than 22% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.