x402 Utility
Related Servers
Alternatives to x402 Utility
- AlicenseAqualityBmaintenanceBlockchain event sequence anomaly detection MCP server using NASA-derived sequence mining, providing human-readable story labels and anomaly scores for financial event windows.16488 npmMIT
Related Servers
- MIT
- AlicenseBqualityBmaintenancePay-per-call MCP and x402 v2 server on Base USDC providing 19 keyless tools for AI agents: web extraction, social and academic search, B2B lead and domain intelligence, npm/PyPI package and smart-contract security audits, OFAC compliance screening, and DeFi swap quotes23272 npmMIT

oom-x402-mcpofficial
FlicenseNot gradedqualityBmaintenanceMCP server exposing 1,000+ pay-per-call API endpoints across agent infrastructure (memory, coordination, secrets, verification), data, compute, finance, weather, geography, and reference categories — payments via x402 protocol in USDC on Base.-- AlicenseAqualityBmaintenanceMCP server exposing 43 pay-per-call x402 tools (USDC on Base) for AI agents: validation, data lookup and utility APIs. No API key needed.59MIT

opendexterofficial
AlicenseNot gradedqualityCmaintenanceAn MCP server that enables AI agents to search, pay for, and call paid APIs using the x402 protocol, with automatic USDC settlement.2MIT- AlicenseCqualityDmaintenanceMCP server bringing 100+ x402-paid APIs to AI agents (Claude, Cursor, MCP-aware clients). Auto-discovers tools from CDP Bazaar; handles USDC micropayments on Base.10083 npm1MIT
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose: list_capabilities for browsing the catalog, search_capabilities for keyword search, get_endpoint_spec for detailed specifications, call_endpoint for executing routes, daily_402 for a curated daily pick, and agent_service_directory for service-level metadata. There is no ambiguity between them, and the descriptions reinforce their unique roles.
The first four tools follow a consistent verb_noun pattern (list_capabilities, search_capabilities, get_endpoint_spec, call_endpoint), but daily_402 and agent_service_directory abandon the verb prefix, creating a minor inconsistency. All names use snake_case and are otherwise readable, so the deviation is not jarring.
With 6 tools, the server is well-scoped for its purpose as a gateway to a large endpoint catalog. The count is within the ideal range and each tool covers a necessary step in the discovery-to-execution workflow, with no redundancy or obvious bloat.
The tool set fully covers the core lifecycle: browse (list_capabilities), find (search_capabilities), inspect (get_endpoint_spec), and execute (call_endpoint). Additional tools for daily highlights and service directory add value without leaving any critical gaps for the intended use case.