Skip to main content
Glama
Bitcompare MCP Server

Bitcompare MCP Server

Official

Related Servers

Alternatives to Bitcompare MCP Server

Related Servers

  • A
    license
    A
    quality
    C
    maintenance
    Cross-chain DeFi intelligence MCP server for AI agents. 7 tools for yield discovery, pool analysis, profit simulation, risk scoring, whale tracking, impermanent loss calculation, and DeFi overview across 86 chains and 6,500+ liquidity pools.
    7
    1
    AGPL 3.0
  • A
    license
    A
    quality
    C
    maintenance
    Official MCP server for interacting with Saudi market data (Sahmk) via natural language queries, enabling stock quotes, company info, and market summaries inside AI agents like Cursor and Claude Desktop.
    15
    15
    MIT
  • A
    license
    A
    quality
    C
    maintenance
    Read-only MCP server for the Hyperliquid / HyperEVM ecosystem - yields, protocol TVL, fees, markets, funding history, order-book depth.
    9
    83 npm
    MIT
  • A
    license
    C
    quality
    B
    maintenance
    The canonical crypto MCP server for AI agents, providing access to 3,500+ editorial articles, 200+ entity dossiers, 43 academy lessons, and live market data as native MCP tools with full attribution.
    98
    160 PyPI
    1
    MIT

TDQS

A3.6/5.0

Scored across 21 tools

Disambiguation4/5

Most tools target distinct resources (prices vs. yields vs. coin metadata vs. stablecoin analytics), and descriptions actively steer usage, e.g. telling agents to pass category="lending" and to prefer get_price over get_price_by_symbol for multiple symbols. The main soft spots are get_rates vs. get_rate_by_symbol and get_price vs. get_price_by_symbol, which overlap substantially and are only separated by prose hints.

Naming Consistency3/5

Mostly snake_case with a predictable verb_noun style for retrieval (get_*, list_*, resolve_*), but the set mixes verbs with bare nouns (top_coins, market_summary, fear_greed_index, stablecoin_index, similar_coins). Analogous operations are named inconsistently, e.g. get_rate_history vs. coin_history.

Tool Count3/5

21 tools is on the heavy side for a data API and covers several domains (coins, prices, yields, providers, stablecoins), so some surface likely goes unused in a single session. Each tool does map to a real endpoint, so it is not padding, but it sits at the borderline of the acceptable range.

Completeness4/5

Market data, rates/yields, provider listings, earn-product terms, rate-change audit logs, and stablecoin analytics are all covered, so core workflows have no dead ends. Gaps are minor: single-product lookup by id and bulk symbol resolution are missing or plan-gated — resolve_symbols_batch is exposed but explicitly returns 403 on the current plan.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues