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
56 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.21 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.260 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 gradedqualityFmaintenanceEnables AI agents to resolve tokens, get quotes, check for honeypots/rug pulls, build swaps, and retrieve receipts via x402 micropayments.1MIT
TDQS
A3.9/5.0
Scored across 7 tools
Disambiguation4/5
The tools mostly partition cleanly by workflow stage (search → rank → inspect → assess → monitor), and descriptions explicitly cross-reference each other ('Then x402_get_service for the full record'), which resolves most ambiguity. There is residual overlap: x402_search_services vs x402_find_best_service both discover services, and x402_get_service vs x402_check_health both describe a single service's status/uptime.
Naming Consistency4/5
All names share the x402_ prefix and snake_case, and most follow a verb_noun shape (get_service, search_services, assess_services, check_health, find_best_service). Two names break the verb pattern (x402_change_events, x402_facilitator_volumes), a minor but real deviation.
Tool Count5/5
Seven tools is well-scoped for a read-only x402 directory and rail-monitoring server. Each tool occupies a distinct role (discovery, ranking, detail, health, change log, facilitator volumes, paid assessment) with no filler.
Completeness4/5
The discovery-to-decision pipeline (search, rank, get record, health, changes, facilitator volumes) is well covered, plus a paid assessment path. Minor gaps: no explicit category/network enumeration and live endpoint calling exists only as an optional probe, not a first-class tool.
Maintenance
ActivityMaintained
ResponsivenessUnresponsive