x402-discovery-mcp
Related Servers
Alternatives to x402-discovery-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceDiscovers and queries x402-payable APIs at runtime — enables autonomous agents to find, evaluate, and pay for services via USDC micropayments on Base without API keys or subscriptions.MIT
- FlicenseNot gradedqualityAmaintenanceFind and vet paid x402 API services before an agent spends money on them, with live reliability scores and recency-weighted probing.-

@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.54 npmApache 2.0- AlicenseNot gradedqualityDmaintenanceEnables AI agents to discover and pay for x402-enabled services using natural language, with multi-chain support for Solana and EVM payments.2 npm1MIT
- FlicenseNot gradedqualityAmaintenanceEnables agents to discover and verify paid agent services through x402 payment validation and release gate checks.-

Clearhouseofficial
AlicenseNot gradedqualityCmaintenanceOne search across every agent registry — 100K+ MCP, A2A and x402 services, deduplicated. Route calls through one endpoint; every call gets a signed receipt.MIT
TDQS
Scored across 5 tools
x402_browse and x402_discover both return service lists, but browse is a free full-catalog view while discover is a paid keyword search with ranking and code snippets. Health and attest are related to status but distinct: real-time health check vs signed quality attestation.
All tools share a consistent x402_ prefix followed by a single word. Most are imperative verbs (discover, browse, register, attest), while health is a noun, but it clearly maps to a health-check action, so the pattern remains predictable.
Five tools is well-scoped for a discovery-focused server: search, catalog browsing, health checking, registration, and attestation. Each tool has a distinct job and none feels redundant.
The core discovery workflow is covered: search, browse, health, register, and signed attestation. The main gaps are managing existing registrations, such as updating or unregistering a service, but agents can still complete primary discovery tasks.