Skip to main content
Glama
QuantGeekDev

coincap-mcp

by QuantGeekDev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to coincap-mcp

No user-submitted related servers found.

    Related Servers

    • Crypto Price & Market Analysis

      roman0211
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides comprehensive cryptocurrency analysis using the CoinCap API, offering real-time price data, market analysis across exchanges, and historical price trends for any cryptocurrency.
      314
      MIT

    • 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
      -

    • crypto-portfolio

      gorlomi-enzo
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables real-time cryptocurrency prices, search, and market data via the CoinGecko API without requiring an API key.
      -

    • 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
      40
      7
      -

    • mcp-crypto

      dhruvil05
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides real-time cryptocurrency data from CoinGecko, including prices, market data, historical data, and coin search.
      11
      MIT
    Deploy Server
    RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

    TDQS

    C2.7/5.0

    Scored across 3 tools

    Disambiguation2/5

    Two tools (bitcoin_price and get_crypto_price) have overlapping purposes, both focused on fetching crypto prices, which creates ambiguity. The descriptions do not clearly differentiate them, making it likely an agent could misselect between them. The third tool (list_assets) is distinct, but the overlap between the first two significantly reduces clarity.

    Naming Consistency3/5

    The naming is mixed, with two tools using a verb_noun pattern (get_crypto_price, list_assets) and one using a noun_verb pattern (bitcoin_price). While readable, this inconsistency in verb placement and specificity (bitcoin vs. crypto) deviates from a predictable convention. The patterns are not chaotic but lack uniformity.

    Tool Count3/5

    With 3 tools, the count is borderline thin for a crypto data server, as it may lack comprehensive coverage for common operations like historical data or multiple asset queries. However, it is reasonable for a minimal or focused scope, though it feels slightly under-scoped for typical crypto API use cases.

    Completeness2/5

    The tool set has significant gaps for a crypto data domain, such as missing operations for historical price data, market cap info, volume, or specific asset details beyond listing. The overlap in price tools does not add functionality, and agents may struggle with incomplete workflows like tracking trends or comparing assets over time.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources