navi-x402-mcp
Related Servers
Alternatives to navi-x402-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceProvides pay-per-use tools for AI agents like web screenshots and crypto intelligence using automatic USDC micropayments on the Base network. It simplifies access to premium APIs by handling blockchain transactions automatically when a payment is required.125 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to access crypto prices, DeFi yields, Polymarket data, Base chain info, and security scans with pay-per-call via USDC on Base mainnet.MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to pay per tool call in USDC via the x402 micropayment protocol, with no API keys or subscriptions required.-
- AlicenseAqualityCmaintenanceEnables paid web-extraction tools for agents, settling each request in USDC on Base with no account or API key.6MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to use pay-per-use web scraping, Base blockchain analytics, and PDF text extraction tools, monetized via x402 USDC micropayments.-
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to call 45 micro-priced utility tools via x402 micropayments on Base, covering search, screenshots, OCR, PDFs, WHOIS, geo-IP, and more without API keys.-
TDQS
Scored across 15 tools
Several tools have overlapping purposes: url_preview, page_context, and web_intelligence all analyze web pages with varying depth, and crypto_indicator/crypto_health/hype_signal/hype_engine all cover crypto metrics. An agent could easily select the wrong tool despite the descriptions.
All tools follow a consistent 'navi_<domain>_<feature>' naming convention with snake_case. The prefix is uniform and readable. This is a coherent pattern.
15 tools is at the high end of the recommended range, but the server covers a broad set of unrelated utility domains (web, crypto, weather, translation, etc.), so the count is defensible. However, some tools are redundant in purpose, so the effective scope feels slightly larger than necessary.
The server's mixed-purpose nature makes it hard to assess completeness. There are no obvious dead ends, but the overlap between web intelligence tools suggests the set could be refined. Core utilities like time, FX, and translation are present, but the lack of a unified domain means gaps are unclear.