intelligence-mcp
Related Servers
Alternatives to intelligence-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables agents to discover, sample, and pay per call in USDC for live threat intelligence, ZK proof generation, and arbitrage signals via the x402 protocol.MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to access 25 pay-per-request intelligence APIs using USDC micropayments via the x402 protocol, without API keys or accounts.-
- FlicenseNot gradedqualityBmaintenanceEnables agents to query real-time labelled pump.fun intelligence—launch risk cards, creator reputation, rug/graduation flags, wallet profiles, and market regime—with paid endpoints settled per request via x402 USDC on Solana and free sample/regime tools.-

@hpp-io/x402-mcp-bridgeofficial
AlicenseNot gradedqualityAmaintenanceEnables AI agents to autonomously pay for and discover services using HPP USDC.e over the x402 protocol, without API keys or manual signing.93 npmApache 2.0- FlicenseNot gradedqualityBmaintenanceProvides coding agents with 19 pay-per-call developer utilities, npm supply-chain security checks, and Base blockchain lookups, paid via USDC on Base using x402. No API key needed—payment acts as authentication.46 npm-
- AlicenseAqualityAmaintenanceI built this local stdio MCP adapter to discover, preview, and purchase live agent data APIs, including vendor risk, company intelligence, transaction preflight, and EVM reads. Free discovery and previews require no wallet. Optional paid calls settle in Base USDC through x402 v2; auto-pay is disabled by default.271 npmMIT
TDQS
Scored across 3 tools
Each tool serves a clearly distinct purpose: comparative analysis (compare_protocols), detailed retrieval (get_protocol_info), and ecosystem discovery (scan_opportunities). No functional overlap exists between them.
All three tools follow a consistent verb_noun snake_case pattern (compare_protocols, get_protocol_info, scan_opportunities) with predictable action words appropriate to their functions.
Three tools is borderline thin for the domain; while it covers basic read/compare/scan operations, the minimal surface leaves little room for additional analytical or filtering capabilities that intelligence workflows typically require.
Notable gap exists in protocol discovery: get_protocol_info and compare_protocols appear to require specific protocol identifiers, but no list_protocols or search_protocols tool is provided to discover available identifiers before using the other tools.