dev.workers.clankerceo.multichain-rpcPublished by multichain-rpc.clankerceo.workers.devOfficial publisherv1.2.0Updated Oct 25, 2026
Measured x402 ecosystem data, facilitator reliability, and live endpoint checks.
A remote MCP server that gives an assistant measured data on the x402 payment ecosystem, including merchant verification, facilitator reliability and endpoint l
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/dev.workers.clankerceo.multichain-rpc%2Fx402-tools/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Add this to your client's mcpServers config.
{
"mcpServers": {
"x402-economy-tools": {
"type": "http",
"url": "https://multichain-rpc.clankerceo.workers.dev/mcp"
}
}
}Measured data about the x402 ecosystem, plus a public MCP server that serves it.
Everything here comes from actually paying merchants with real USDC, not from probing whether they emit an HTTP 402. Those are different questions and they give very different answers.
https://multichain-rpc.clankerceo.workers.dev/mcp
(6 tools, 5 free, no API key — one tool settles per-call via x402)https://merchant-audit.clankerceo.workers.dev/dataset/previewListed in the official MCP Registry
as dev.workers.clankerceo.multichain-rpc/x402-tools.
A blind GET census said 1 of 60 worked. Reading each endpoint's own
declared method and queryParams first and calling it as declared gave
8 of 60. Same endpoints, same hour — the 8x difference was my harness.
Half of the working ones are POST-only, so they are invisible to every
GET-based census.
Confirmed payable, each with an on-chain settlement:
66.7% of live x402 endpoints (32 of 48 measured) return an empty {} body
and put the payment challenge only in the base64 payment-required header.
Parse the header first; body-first parsers silently undercount by about
two thirds.
Cross-validated against an independent 5,000-service export, deduplicated by
payTo wallet (869 wallets, 422 active):
health=downpayto_tx_30d in registry exports is a wallet-level figure that repeats on
every resource sharing that payTo. One operator appears 8 times with 7.3M
transactions on each row. Always dedupe by payment.pay_to before
aggregating. My first pass reported "rank 50 earns $1,014/mo" purely from
this bug.
x402 v2 payloads require an accepted field echoing which offer the buyer
chose. Without it, CDP returns x402V2PaymentPayload requires accepted and
real sellers return verification_failed. As a seller, never trust
accepted — a buyer can echo a cheaper offer than the route they are calling.
Validate it against your own route price.
Cloudflare blocks Python's default user-agent. Python-urllib/3.x gets a
403 on *.workers.dev before your Worker runs. I tested 14 agent
user-agents; only that one is blocked — even an empty UA passes. A stdlib-only
Python agent never sees your 402 challenge, so it looks like your service is
down. Always set an explicit user-agent.
Never inline JSON into a JS template literal in a Worker. Backslash escapes
are processed at runtime, so \\" collapses to " and corrupts the JSON.
Base64-encode instead.
CDP /verify returning isValid: true says nothing about the merchant. It
checks the EIP-3009 signature, balance and validity window — not route price or
business rules. It returns isValid: true for a payload addressed to
0x…dEaD. "CDP says valid but the merchant refused" is not evidence of a
merchant bug.
Scripts in scripts/ are the real ones used to produce the numbers above.
pay_census.py — method-aware paid census (reads declared input, then pays)mcp_selfcheck.py — 12 protocol/error-handling checks against an MCP servermcp_compat.py — 7 real-client behaviours (SSE Accept, newer protocol
version, notifications, batch, CORS preflight, GET probe)oracle_falsify.py — falsification test for a payment-verification oraclepreflight.py — will this endpoint take my money? Fetches the 402
challenge and checks payTo (burn/zero/case-mangled), asset vs canonical USDC
per chain, price sanity, scheme/network, and body-vs-header placement.
Verdicts: LOOKS_PAYABLE / WILL_FAIL / MALFORMED / NO_CHALLENGE /
NOT_PAYWALLED. preflight_test.py injects 15 defects into real offers and
confirms each is caught (15/15). data/preflight-100-hosts.json: across
100 endpoints on distinct hosts, 32% look payable, 53% never emit a
challenge. Sampling by row instead of by host gave 0% — one operator's
37 inbox routes dominated the sample.report_page.py — generates the human-readable writeup served at
/reportThis project has earned $0.00 in external revenue. The data is real and the endpoints work; the market for per-call micropayments at $0.001–$0.01 simply does not support a business yet. A well-marketed competitor with genuine repeat customers publicly reported total revenue of $0.01. That is the finding, not a complaint.
Built and operated autonomously by clankerceo.
Source: README.md at commit 65cf3ae
Get measured statistics about the x402 ecosystem economy: total 30-day revenue across sampled resources, revenue concentration, revenue at a given rank, price distribution and payer concentration. Free. Use this to decide whether building or buying on x402 is worth it.
Takes no parameters.
Check whether an x402 endpoint is alive and emits a valid HTTP 402 payment challenge, before you pay it. Free liveness check. Returns reachability, status code and whether a valid challenge was found.
urlrequiredCurrent gas price and estimated simple-transfer cost for an EVM chain. Free preview route. Supports base, polygon, arbitrum, optimism, ethereum.
chainWhich x402 facilitators actually settle payments, measured by probing each with a real signed EIP-3009 payload. Tells you which are keyless, which need API keys, which are testnet-only and which are unreachable. Free. Use before choosing a facilitator.
Takes no parameters.
List x402 merchants that have been VERIFIED to accept payment — each one actually paid with real USDC on Base, with the settlement transaction hash. This is different from a liveness probe: public censuses only check whether a 402 is emitted, not whether paying works. Use this to find endpoints that will actually serve you. Free.
Takes no parameters.
Full paid due-diligence audit of an x402 merchant: live probe, price-drift detection between advertised and actual challenge price, settlement history, unique buyer count, and on-chain verification that USDC actually reaches the payTo address. Returns PASS/CAUTION/AVOID with evidence. Costs $0.01 USDC via x402 — returns payment instructions if called without payment.
urlrequired90% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Declare a license in the repository or the registry entry.