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.21 npmMIT

Stelar Signals MCPofficial
AlicenseAqualityDmaintenanceEnables 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.656 npmMIT- AlicenseNot gradedqualityFmaintenanceEnables 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 gradedqualityBmaintenanceEnables 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 242 tools
The chain/protocol/metric prefix structure gives some signal, but with 242 tools and virtually no descriptions, an agent must guess between near-identical siblings: price_current vs price_unix vs price_hour, orca_pools vs orca_pools_fee_metrics vs orca_pools_liquidity_map, and every `_windows` variant (e.g. morpho_v2_vaults_windows vs morpho_v2_vaults) has no explanation of how it differs. Singular/plural pairs (pool/pools) and versioned families (morpho_v1/v2, euler vs euler_v2) compound the overlap. Only the mechanically encoded chain/protocol token distinguishes many tools, and that is a naming artifact rather than a described purpose.
Names follow a strong, predictable pattern of cambrian_<chain>_<domain>_<entity>[_windows] in consistent snake_case, which makes the surface largely scannable. Minor deviations exist (chain-agnostic tools like cambrian_deep42_*, cambrian_risk_perp_risk_engine, cambrian_docs, cambrian_solana_token_snapshot, and irregular ordering in cambrian_solana_ohlcv_base_quote), but nothing approaching mixed conventions.
242 tools is an extreme mismatch: the vast majority are the same handful of endpoints replicated across (chain × protocol × metric × window) combinations. A chain/protocol parameter on a few dozen generic tools would express the same surface. At this size tool selection becomes a combinatorial guessing game, and the lack of descriptions makes it worse.
Coverage of the DeFi analytics domain is broad (prices, OHLCV, DEX pools, lending markets/vaults, tokens, TVL) but uneven: Solana has deep entity-level tooling (holders, security, leaderboards, wallet balance history) that has no EVM counterpart, and protocol coverage is chain-asymmetric (aero/alien only on Base, sparklend/sky only on Ethereum). There are also no cross-chain comparison, search, or entity-lookup tools beyond the docs helper, so agents will hit dead ends when moving off Solana.