agent402-mcp
Related Servers
Alternatives to agent402-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceMCP server providing 11 pay-per-call web intelligence tools (page reading, PDF extraction, RSS parsing, screenshots, summarization, structured data extraction) for AI agents, paid automatically in USDC via the x402 protocol on Base mainnet with no API keys required.20 npmMIT
- AlicenseBqualityFmaintenanceAn MCP server providing 22 pay-per-call utility tools for AI agents (scrape, validate, embed, store, moderate, notify, convert, prevent loops) without accounts or API keys, using USDC payments via the x402 protocol.1766 npm1MIT
- AlicenseNot gradedqualityDmaintenanceMCP server that provides AI agents with pay-per-call access to a suite of tools (honeypot check, token market, DeFi yields, etc.) via USDC on Base using the x402 protocol.6 npmMIT
- AlicenseCqualityFmaintenanceMCP server bringing 100+ x402-paid APIs to AI agents (Claude, Cursor, MCP-aware clients). Auto-discovers tools from CDP Bazaar; handles USDC micropayments on Base.10035 npm1MIT
- AlicenseNot gradedqualityBmaintenanceMCP server exposing 10 curated tools for AI agents, providing crypto trading signals, on-chain analysis, and web utilities via pay-per-call x402 endpoints on the Base network.MIT

oom-x402-mcpofficial
FlicenseNot gradedqualityBmaintenanceMCP server exposing 1,000+ pay-per-call API endpoints across agent infrastructure (memory, coordination, secrets, verification), data, compute, finance, weather, geography, and reference categories — payments via x402 protocol in USDC on Base.-
TDQS
Scored across 15 tools
Most tools have distinct purposes and the descriptions explicitly cross-reference the alternatives (web.search vs web.news vs web.answer; memory.read vs memory.write). However catalog.search, catalog.find, and route_and_execute all overlap on 'find/reach a tool,' and the discovery-vs-execute boundary requires careful reading to keep straight.
The set mostly follows a clean namespace.action pattern (browser.render, memory.read, web.search, catalog.call, sellers.list). The lone deviation is route_and_execute, which drops the dotted convention while server.describe and payment.info keep it.
15 tools is slightly heavy but justified by the server's dual role as both a flagship tool host and a gateway/broker to an external catalog. A few meta tools (server.describe, payment.info) are lightweight but earn their place for onboarding.
Core workflows are covered: search/answer/news, render, transcribe, memory read/write, market quote, catalog discovery/calling, routing, and seller listing. Minor gaps: delete is folded into memory.write, and frequently referenced tools (extract, stock-history, memory-recall) are only reachable indirectly via catalog.call.