Cambrian API MCP
OfficialRelated Servers
Alternatives to Cambrian API MCP
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceProvides AI agents with research tools for AI agent ecosystem analysis, DeFi protocol analysis, and general market research.329 npmMIT

Stelar Signals MCPofficial
AlicenseAqualityBmaintenanceEnables AI agents to access crypto market signals including regime, sentiment, price, risk, and text tools like summarization and fact-checking, backed by a live production-grade classifier.636 npmMIT- FlicenseNot gradedqualityDmaintenanceEnables AI agents to access real-time crypto risk intelligence with two tools: Flare for precursor detection and Core for overall risk environment assessment.4-
- 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 access 48 real-time crypto data tools including prices, DeFi, meme tokens, gas, sentiment, Solana, and agent commerce, with post-paid billing via Solana USDC.-
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to perform complex crypto operations like cross-chain routing, contract decoding, portfolio management, and anti-rug security checks, returning unsigned transactions for safe signing by the agent.MIT
TDQS
Scored across 145 tools
Most tools are clearly distinguished by chain and protocol in the name (e.g., cambrian_ethereum_uniswap_v3_pool vs cambrian_base_uniswap_v3_pool). However, a few pairs like cambrian_solana_tokens_holder_distribution_over_time and cambrian_solana_tokens_holders_over_time have overlapping semantics, and the absence of descriptions for nearly all tools increases ambiguity.
All tools follow the same pattern: cambrian_<chain>_<domain>_<specific>. Plural/singular variations and modifiers like _time_bounded are used consistently. The naming is highly predictable and systematic.
With 145 tools, this is an extreme mismatch for an MCP server. Even if the API covers many chains and protocols, the sheer number overwhelms an agent's selection process and makes the surface unwieldy.
The tool surface appears comprehensive, covering price, pools, tokens, lending, social data, and risk across multiple chains. Minor gaps exist (e.g., no cross-chain comparison tools or some metadata endpoints), but core analytics workflows are well supported.