Snap Router
Related Servers
Alternatives to Snap Router
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to access 11 paid x402 endpoints as standard MCP tools, paying per call in USDC on Base without API keys, covering chat, code, vision, embeddings, crypto prices, weather, geolocation, forex, and WHOIS data.-

AgentBIT MCP Serverofficial
AlicenseNot gradedqualityDmaintenanceEnables AI agents to call 50+ pay-per-request tools covering onchain and crypto data, web research, security, compliance screening, business intelligence, and infrastructure checks. Payments settle per call in USDC on Base through the x402 protocol with no accounts, API keys, or subscriptions, and the first call is free for new wallets.MIT- FlicenseNot gradedqualityBmaintenanceEnables AI agents to pay per tool call in USDC via the x402 micropayment protocol, with no API keys or subscriptions required.-
- AlicenseAqualityAmaintenancePay-per-call data and tools for AI agents over x402, by UnyKorn. 360 endpoints: DeFi and market data, multi-chain wallet reads, wallet and token risk signals, SEC filings, web and domain intel, and AI text tools. Settled per call in USDC on Base ($0.001-$0.25). No API keys or subscriptions; unpaid calls return the exact quote first.221MIT
- AlicenseNot gradedqualityCmaintenanceExposes a live catalogue of specialist tools as MCP endpoints and returns x402 payment challenges for each call, letting agents pay per use in USDC from their own wallet without subscriptions or API keys.MIT
- AlicenseNot gradedqualityBmaintenancePay-per-call access to SEO and SERP data, keyword research, backlink and site audits, local business search, SMS verification, social marketing, EU-hosted LLM inference, and read-only on-chain calls. No signup and no API key: agents pay per request in USDC on Base via x402.50 npmMIT
TDQS
Scored across 1 tool
With only one tool, there is no possibility of misselection or overlap; its stated purpose (catalog discovery before loading tools) is unambiguous. An agent cannot confuse it with anything else in this server.
The single tool follows a clean snake_case verb/resource-style name (snap_router) that matches the server name. There is no second convention to conflict with.
A one-tool surface is inherently thin, even though a discovery router is arguably a single-purpose operation. The rubric treats 1-2 tools as borderline, and this sits right at that edge.
For a pure discovery role, the tool covers the core 'find candidates' operation, but the surface is a dead end: no way to fetch full details for a given service/tool ID, filter by price/category, or paginate the 16k-entry catalog. Agents can work around this by rerunning searches, but it is a notable gap.