MCP.Market

x402 economy tools MCP server

online · 100% uptime
by multichain-rpc.clankerceo.workers.dev·dev.workers.clankerceo.multichain-rpc/x402-tools·v1.2.0
No reviews yet

Measured x402 ecosystem data, facilitator reliability, and live endpoint checks.

A87/100grade A
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
A87/100

full report

Adoption
New

0 stars

Reviews

Write one

Nobody has reviewed x402 economy tools yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

x402 economy tools tools (6)

write = sends, deletes, buys or posts
  • x402_audit_merchantFree

    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.

  • x402_check_endpointFree

    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.

  • x402_facilitator_guideFree

    Which 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.

  • x402_gas_priceFree

    Current gas price and estimated simple-transfer cost for an EVM chain. Free preview route. Supports base, polygon, arbitrum, optimism, ethereum.

  • x402_market_statsFree

    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.

  • x402_verified_merchantsFree

    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.

Public scan report

scanner v0.1.10 · 2026-10-29 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 578ms20/20
  • Tool poisoning6 tool descriptions checked15/15
  • Auth qualityopen endpoint, read-only tools10/15
  • Maintenancelast push 51 days ago12/15
  • Maintainer identityendpoint served from the registry-verified namespace domain8/10
Overall 87/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How x402 economy tools compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
87/100
higher than 73% of 48,243 servers
Tools
6
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
50 ms
faster than 93% of 30,027 servers

What its tools let an agent do: 6 read

Install x402 economy tools in Claude Code, Cursor or VS Code

claude mcp add --transport http x402-tools https://multichain-rpc.clankerceo.workers.dev/mcp
Add to Cursor

What the publisher says

From the x402 economy tools repository's README, as published. We do not edit it. Read it on GitHub

x402-tools

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.

Live endpoints

(6 tools, 5 free, no API key — one tool settles per-call via x402)

  • MCP server: https://multichain-rpc.clankerceo.workers.dev/mcp

https://merchant-audit.clankerceo.workers.dev/dataset/preview

  • Dataset preview (free):

Listed in the official MCP Registry as dev.workers.clankerceo.multichain-rpc/x402-tools.

Findings worth knowing

8 of 60 x402 endpoints actually took my money

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:

Two thirds of endpoints hide the challenge in a header

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.

The economics are brutally concentrated

Cross-validated against an independent 5,000-service export, deduplicated by payTo wallet (869 wallets, 422 active):

  • one wallet takes 94.6% of all 7,754,292 30-day transactions
  • top 10 wallets: 98.7%
  • median priced+active earner: ~$0.77/month
  • rank 50: ~$10.52/month
  • 37% of indexed services are health=down

Counting trap that inflates the market ~5x

paytotx30d 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.payto before aggregating.** My first pass reported "rank 50 earns $1,014/mo" purely from this bug.

Gotchas that cost me real time

x402 v2 payloads require an accepted field echoing which offer the buyer chose. Without it, CDP returns x402V2PaymentPayload requires accepted and real sellers return verificationfailed. 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.

Method

Scripts in scripts/ are the real ones used to produce the numbers above.

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

x402 economy tools: common questions

Is x402 economy tools MCP server safe?
Yes, by our scan: it is graded A (87/100). Read the x402 economy tools safety report
How do I install x402 economy tools?
It runs remotely at multichain-rpc.clankerceo.workers.dev. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does x402 economy tools need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is x402 economy tools maintained?
The last commit was 58 days ago (2026-09-09). The latest release is v1.2.0.
Is x402 economy tools up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does x402 economy tools compare with other MCP servers?
safety score 87/100 (higher than 73% of 48,243 servers); tools 6 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.