Best x402 MCP servers: a buyer's evidence checklist
A criteria-first guide to choosing paid MCP tools by capability, transport, price and connection reality.
DIRECT ANSWER
Choose an x402 MCP server by the tools it exposes, the transport your client supports, the live payment requirements and the usefulness of one paid result. There is no universal standard mcp.json wallet field. Current official guidance uses an x402-aware client or bridge that signs the payment and retries the protected request.
Key takeaways
- A remote MCP URL does not mean a normal MCP client can pay it automatically.
- Tool schemas and safe sample arguments matter as much as price.
- Prefer servers with a recent quote check, provider documentation and a reproducible buyer path.
Current curated shortlist
Choose by task and evidence rather than tool count alone. Paid-call verified is stronger evidence than an unpaid quote check, while provider-documented entries still need a controlled buyer test.
- Confirm the client supports streamable HTTP or the advertised transport.
- Avoid mutating tools during initial testing.
- Use a narrowly funded wallet and explicit maximum payment.
| MCP server | Listed price | Evidence | Tools |
|---|---|---|---|
| TrophyCoach MCP | from $0.005/call | Paid-call verified + quote checked | 4 gaming/data tools |
| glim.sh | from $0.002/call | Quote checked | 11 live-data tools |
| agentsvc.io | from $0.001/call | Provider documented | 20 utility tools |
Understand the payment bridge
MCP describes tool discovery and invocation; x402 describes the paid HTTP exchange. The buyer still needs software that understands payment requirements, signs an allowed scheme and retries. The official MCP example runs an x402-aware bridge as the MCP server exposed to Claude Desktop. Copying an unknown wallet field into a client configuration is not equivalent.
Rank evidence, not badges
Provider-reported live, unpaid quote checked and settled paid-call verified are different levels of evidence. A useful shortlist favors recent checks and complete schemas, then runs one controlled paid call before depending on the server in a production agent.
Related directory entries
Sources and methodology
TOLL·402 distinguishes public claims, registry discovery, unpaid quote checks and settled paid-call verification. Sources below support the visible claims; presence in a registry is not treated as verification.
- Official MCP with x402 guide — Current bridge architecture and signer setup.
- TOLL·402 MCP listings — Curated MCP server and tool evidence.
- x402 buyer quickstart — Authoritative current packages and payment schemes.