Skip to main content
Glama
CryptoAPIs-io

Crypto APIs Market Data MCP Server

by CryptoAPIs-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Related Servers

Alternatives to Crypto APIs Market Data MCP Server

No user-submitted related servers found.

    Related Servers

    • CoinCap MCP Server

      Sanchello69
      F
      license
      A
      quality
      D
      maintenance
      Provides access to cryptocurrency market data through the CoinCap API v3, enabling users to retrieve real-time prices, exchange rates, market information, and detailed data for various cryptocurrencies.
      5
      -

    • mcp-crypto

      pipeworx-io
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides cryptocurrency market data (top coins by market cap) and fiat currency exchange rates.
      3 npm
      MIT

    • CoinMarketCap MCP Server

      Alexander-Herranz
      A
      license
      B
      quality
      D
      maintenance
      Provides access to cryptocurrency market data, exchange information, and blockchain metrics through the CoinMarketCap API. Supports price quotes, historical data, trending tokens, global metrics, and DEX information across different subscription tiers.
      26
      36 npm
      MIT

    • CoinCap MCP Server

      CC3-0
      F
      license
      C
      quality
      C
      maintenance
      Provides access to CoinCap's cryptocurrency market data and technical analysis tools via MCP, supporting assets, exchanges, markets, and more.
      38
      8 npm
      7
      -

    • polygon-mcp

      atomcp-ai
      A
      license
      C
      quality
      C
      maintenance
      Enables querying real-time and historical financial market data for stocks, options, forex, and crypto, including quotes, trades, technical indicators, and reference data through a set of MCP tools.
      71
      3
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.5/5.0

    Scored across 4 tools

    Disambiguation4/5

    The four tools have distinct purposes: metadata, exchange rates, asset details, and reference docs. Within exchange rates and assets, there are closely related actions (by symbol vs. by ID) that could cause selection confusion, but the tool-level separation is clear.

    Naming Consistency4/5

    Tool names follow a consistent snake_case pattern with the 'market_data_' prefix for data tools, and 'system_info' is a minor deviation. Actions use a consistent kebab-case verb-noun structure (e.g., 'get-exchange-rate-by-asset-symbols'), so overall naming is predictable with only a slight inconsistency.

    Tool Count4/5

    With 4 tools, the server is on the lean side but not unreasonable for a market data scope. Each tool covers a different aspect (metadata, rates, assets, reference), and the count is within the acceptable range, though it feels minimal rather than comprehensive.

    Completeness2/5

    The tool surface is missing common market data operations such as historical price data, market charts, OHLCV, or market cap. It only provides current exchange rates and asset details, which is a significant gap for a market data API and will likely cause agent failures when historical or broader market metrics are needed.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources