A
licenseA
qualityD
maintenanceThe MCP gateway that lets any AI agent discover and pay metered APIs on Base or Solana — without the user wiring payments themselves.
3
17 npm
1
Apache 2.0
swarm-x402-mcp
Related Servers
Alternatives to swarm-x402-mcp
No user-submitted related servers found.
Related Servers
monospay-mcpofficial
AlicenseNot gradedqualityDmaintenancePay per MCP tool call in USDC on Base. Non-custodial settlement, no admin keys, 30 bps fee.MIT- AlicenseAqualityFmaintenanceEnables MCP clients to access all endpoints of an x402 gateway by paying real-time microtransactions (USDC on Base) per API call, with automatic tool discovery and spend guardrails.2360 npmMIT
GlianaAI MCP Serverofficial
AlicenseAqualityBmaintenanceEnables pay-per-call access to 90+ generative AI models and utility tools via any MCP client, with no signup or API key, using wallet-based USDC payments on Base, Tempo, or Solana.773 npmMIT
halowerk-mcpofficial
AlicenseAqualityCmaintenanceProvides access to 70 paid APIs as MCP tools with per-call and session budgets, paying via x402/USDC on Base without requiring an account or login. Includes a built-in allowlist of hosts and safe defaults to prevent unintended payments.1445 npmMIT- AlicenseNot gradedqualityCmaintenanceMarketplace of MCP servers and APIs that agents pay for per call in USDC over x402 on Base; connect anonymously, pay only when you callMIT
TDQS
A3.8/5.0
Scored across 4 tools
Disambiguation4/5
Each tool targets a different service: miscellaneous utilities, repo code scanning, web research brief, and web research report. Summary and report overlap in that both do live web research, but the one-page brief versus full Markdown report distinction is clear from descriptions and pricing.
Naming Consistency4/5
All names are lowercase noun-style labels, which is consistent enough for this service-catalog style server. The only minor deviation is code_health using an underscore while the others are single words, but this remains predictable and readable.
Tool Count4/5
Four tools is a reasonable, compact surface for a paid service aggregator where each tool maps to a distinct offering. It is slightly thin, but no tool feels redundant or out of scope.
Completeness3/5
The tools cover four concrete paid operations, but the surface lacks supporting operations for a payment-oriented server, such as checking wallet balance, previewing quotes, or querying transaction status. Agents can perform the main calls, but dead ends around payment state and service discovery remain.
Maintenance
ActivityNo data
ResponsivenessNo issues