A
licenseB
qualityB
maintenanceDiscover, pay for, execute, and publish monetized APIs directly from your agent, settled per call in USDC over x402, through the Model Context Protocol.
42
53 npm
MIT
x402-list-mcp
by mcccsm
Related Servers
Alternatives to x402-list-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to discover and pay for x402-enabled services using natural language, with multi-chain support for Solana and EVM payments.24 npm1MIT
@hpp-io/x402-mcp-bridgeofficial
AlicenseNot gradedqualityBmaintenanceEnables AI agents to autonomously pay for and discover services using HPP USDC.e over the x402 protocol, without API keys or manual signing.252 npmApache 2.0- AlicenseNot gradedqualityCmaintenanceEnables agents to discover, sample, and pay per call in USDC for live threat intelligence, ZK proof generation, and arbitrage signals via the x402 protocol.MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to access paid content by integrating cryptocurrency payments through the x402 protocol, allowing LLMs to verify payments and retrieve paid resources automatically.1-
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to resolve tokens, get quotes, check for honeypots/rug pulls, build swaps, and retrieve receipts via x402 micropayments.1MIT
TDQS
A4.1/5.0
Scored across 7 tools
Disambiguation5/5
Each tool has a distinct, non-overlapping purpose: search, get details, best-match recommendation, health check, volume stats, paid assessment, and change log. No two tools could be confused for one another.
Naming Consistency4/5
All tools share the consistent 'x402_' prefix and snake_case convention. Most use a clear verb (search, get, find_best, check, assess), though 'facilitator_volumes' and 'change_events' are noun phrases—still clear and predictable.
Tool Count5/5
Seven tools is well-scoped for a directory service covering search, retrieval, comparison, health, stats, paid deep-dive, and monitoring. Neither too lean nor bloated.
Completeness5/5
The surface covers the full read-only lifecycle: discover (search), inspect (get), decide (find_best), verify (check_health), analyze (volumes), go deeper (assess), and track changes (change_events). No obvious dead ends or missing operations for the stated purpose.
Maintenance
ActivitySlowing
ResponsivenessUnresponsive