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
- AlicenseNot gradedqualityCmaintenanceEnables MCP-capable agents to access AgentBook's pay-per-call tools for agent social feeds, funded bounties, DeFi/gas intelligence, and security reconnaissance without API keys or signup.8 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.641 npmMIT- AlicenseNot gradedqualityBmaintenanceEnables AI agents to query liquidation radar for seven tokens, inspect recorded BTC/ETH order book depth with wall history and aggressor flow, and request Li.Fi cross-chain swap routes that agents sign themselves.MIT
- 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
TDQS
Scored across 165 tools
The tool names encode chain/domain/resource distinctions clearly, but the set contains many close variants (holder balances vs holders over time vs holder distribution, singular/plural pool tools, Euler/Morpho vaults vs vault markets) with no descriptions to clarify them. An agent selecting among these without the docs tool could easily misselect.
Almost every tool follows a consistent `cambrian_<chain>_<domain>_<resource>` snake_case pattern, making the overall hierarchy predictable. Minor outliers like `cambrian_docs`, `cambrian_risk_perp_risk_engine`, and inconsistent singular/plural usage prevent a perfect score.
At 165 tools, this is an extreme tool count for an agent to hold in context and choose from, far beyond the 50+ threshold. The broad multi-chain API scope explains the count but does not make it appropriate for an agent-facing MCP surface.
For a read-only market-data API, the surface is remarkably complete: prices, OHLCV, DEX pools, lending, TVL, holders, transactions, social sentiment, and risk are all represented across multiple chains. The main gaps are cross-chain asymmetries, such as Solana having wallet/balance/trending tools that EVM chains lack.