x402-buyer-mcp
Related Servers
Alternatives to x402-buyer-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to discover, evaluate, and call any x402 API service with automatic USDC payment, including tools for wallet setup, service catalog browsing, recommendations, health checks, and direct API calls.9 npm-
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to discover, pay for, and invoke x402-priced services such as document OCR, document analysis, media transcription, remote browser sessions, and receive-only email inboxes using USDC on Base, with no API keys and receipt-backed results.38MIT
- AlicenseNot gradedqualityDmaintenanceThe open marketplace for the agent economy — Buy any of 24,000+ live x402 services with USDC on Base.5MIT
- 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

@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.695 npmApache 2.0- AlicenseNot gradedqualityCmaintenanceEnables AI agents to call pay-per-request AI and web tools—including web-to-Markdown reading, PDF extraction, translation, compliance lookups, domain/email/Solana data, and prediction-market intelligence—without accounts or API keys, settling each call in USDC via x402 on Base, Solana, or Arc.MIT
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: checking balance, making a single payment-supported call, discovering endpoints, and running parallel research. No overlap or ambiguity.
All tools follow the 'x402_<action>' pattern with consistent lowercase and underscores. The actions are all verbs except 'balance', which is a noun but commonly understood as a verb in API contexts.
Four tools are exactly appropriate for the server's purpose. Each tool is essential and none feel redundant or missing.
The tool surface covers the full workflow: discover endpoints, check balance, call an endpoint, and run multi-endpoint research. No obvious gaps for the stated purpose of interacting with x402 APIs.