check-payment-recipient
https://check-payment-recipient.fuwafuwow.workers.dev/mcpMCP server (Streamable HTTP) exposing two paid tools over x402 v2: check_payment_recipient ($0.05 per check) and check_payment_batch ($0.50 per call, 1-20 checks in one paid call). POST JSON-RPC to /mcp. Free tools: ping, list_capabilities, get_receipt.
Paid verification
How it worksNo sponsored paid call yet.
Pay this endpoint once from your own wallet (Base USDC, up to $1.00) and we call it and record what came back. Your wallet pays the listed recipient directly; Agent Tools never holds funds. Sponsored checks prove delivery; they do not count as demand.
Quality grade
How grading works- ✓ Answers a real HTTP 402 challenge
- ✓ Publishes a /.well-known/x402 descriptor
- ✓ Payment address on record
- ✓ Settlement network declared
- ✓ Price declared
x402 readiness
Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here B, 64.3/100), which weighs availability, payability and on-chain demand. How the two differ
| Valid payment requirements | 10/10 | Payment requirements carry a payee, a mainnet network and a price. |
| Live 402 challenge | 20/25 | Endpoint reachable; its 402 challenge was seen earlier (404 ms). |
| x402 version | n/a | x402 version not observed yet. |
| Signed descriptor | n/a | No x402 standard defines a signed descriptor. |
| Uptime (30 days) | 15/15 | 4/4 probes succeeded; final after 5 probes in 30 days. |
| Resource declaration | 5/10 | Declares 2 paid resource(s). |
| Verified identity | 5/10 | Publisher descriptor (/.well-known/x402 or OpenAPI) on record; claim this listing to verify domain control. |
| Freshness + modern flags | 5/5 | seen in a source within 7 days; declares x402. |
| Security declaration | n/a | Payment is the access control for an x402 resource. |
Compared with peers
Against 10,060 reachable x402 APIs in our daily snapshot (2026-11-12 01:39 UTC). Display only; it does not change search order.
- Readiness
- Higher than 55% of peers
- This listing 80 · peer median 78
- Latency
- Faster than 27% of peers
- This listing 404 ms · peer median 205 ms
Where it loses the most points, and how to win them back
- Live 402 challenge −5
— Answer the paid path with a valid 402 challenge.
Now: Endpoint reachable; its 402 challenge was seen earlier (404 ms).
- Resource declaration −5
— Declare each paid resource with its input and output schema.
Now: Declares 2 paid resource(s).
- Verified identity −5
— Claim the listing and prove control of its domain.
Now: Publisher descriptor (/.well-known/x402 or OpenAPI) on record; claim this listing to verify domain control.
Paid endpoints
2 resource(s) advertised by this origin. Each price below is that resource's own x402 price; the headline price is the range across them.
https://check-payment-recipient.fuwafuwow.workers.dev/mcp#check_payment_recipient
$0.0500 / call
Pre-signing payment safety check: send recipient, amount, asset and network before you sign; get allow / escalate / block with reasons and a verifiable receipt.
https://check-payment-recipient.fuwafuwow.workers.dev/mcp#check_payment_batch
$0.5000 / call
Batch pre-signing payment safety check: 1-20 payment checks in ONE paid call, same rules as check_payment_recipient. Returns per-item decisions plus a summary {total, allow, escalate, block, input_error} and one receipt for the whole batch. Input errors are never charged.
How to call
curl -sS -i -X GET https://check-payment-recipient.fuwafuwow.workers.dev/mcp # expect HTTP 402 Payment Required (about $0.05/call)https://check-payment-recipient.fuwafuwow.workers.dev/mcpListed in
Directories this entry was found in.