crypto-intelligence-mcp
Related Servers
Alternatives to crypto-intelligence-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables crypto research and market intelligence through 66 read-only tools covering sentiment, whale tracking, on-chain flows, influencer accuracy, and screening across 2,300+ coins, allowing AI agents and traders to verify hype, accumulation, and momentum without an API key.MIT
- AlicenseBqualityDmaintenanceProvides AI agents with research tools for AI agent ecosystem analysis, DeFi protocol analysis, and general market research.329 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to query cryptocurrency network and market data through tools for time-series metrics, OHLCV candles, bid/ask quotes, index levels, and asset or market metadata.MIT
- AlicenseAqualityCmaintenanceRead-only Hyperliquid and cross-exchange market research for AI agents, providing structured tools for live market data without requiring authentication.917 npmMIT
- AlicenseNot gradedqualityBmaintenanceProvides crypto market intelligence tools, reference resources, and prompt templates for sentiment analysis, mindshare tracking, social intelligence, and more.9 npm6MIT

PredMCPofficial
AlicenseNot gradedqualityDmaintenanceSafe, read-only market data for AI trading agents, offering 44 tools to query prediction markets, perpetuals, and cross-venue signals without the ability to execute trades.1MIT
TDQS
Scored across 2 tools
The two tools are mostly distinct: ci_discover retrieves product discovery metadata, while ci_request_claim checks readiness for one existing claim. They both read CI-related information, so there is minor potential for confusion, but the descriptions clarify the boundary.
Both tools use the ci_ prefix and snake_case, making the naming predictable and readable. The slight pattern difference between ci_discover and ci_request_claim is a minor deviation rather than an inconsistency.
Two tools is borderline thin for a crypto-intelligence server, even one explicitly scoped to read-only discovery and claim readiness. The surface feels minimal and may leave agents without adjacent operations they would reasonably expect.
The surface covers discovery and claim-readiness checks but lacks broader lifecycle support such as listing/searching claims, creating or updating claims, or retrieving more detailed product/claim information. The explicit read-only limitations reduce danger, but the overall crypto-intelligence domain coverage remains significantly incomplete.