Skip to main content
Glama
coinpaprika

DexPaprika (CoinPaprika)

Official
by coinpaprika
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to DexPaprika (CoinPaprika)

No user-submitted related servers found.

    Related Servers

    • DEX Pools MCP

      kukapay
      A
      license
      A
      quality
      D
      maintenance
      An MCP server that provides AI agents with real-time access to DEX liquidity pool data, enabling smarter trading, analytics, and automated strategies.
      10
      1
      MIT

    • DexPaprika MCP Server

      infinity-smithpl
      A
      license
      A
      quality
      D
      maintenance
      Provides real-time access to cryptocurrency and DEX data across multiple blockchains, enabling users to analyze tokens, pools, trading volumes, and perform technical analysis through DexPaprika's API. No API keys required for seamless integration with AI assistants.
      11
      261 npm
      MIT

    • The Graph Token API MCP

      pinax-network
      A
      license
      Not graded
      quality
      F
      maintenance
      Official MCP server that turns The Graph’s Token API into a plug-and-play web3 data tool. Exposes ERC-20 & NFT metadata, balances, transfers, top-holder stats, prices, and more, allowing LLMs to run SQL queries on structured and indexed blockchain data.
      2
      Apache 2.0

    • coin-mcp

      sweetcornna
      A
      license
      A
      quality
      D
      maintenance
      A comprehensive cryptocurrency market-data MCP server with 49 tools across six data sources, enabling LLMs to answer market questions via natural language.
      49
      MIT

    • x402 MCP Server

      fernsugi
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that provides DeFi data tools (crypto prices, whale concentration, funding rates) for AI agents via the x402 protocol.
      2 npm
      1
      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

    A4.3/5.0

    Scored across 20 tools

    Disambiguation3/5

    Multiple tools return overlapping resource types: getNetworkPools, getDexPools, getNetworkPoolsFilter, and getTokenPools all list pools; getTopTokens and filterNetworkTokens both rank/filter tokens; and getPoolOHLCV/getTokenOHLCV plus getPoolIndicator/getTokenIndicator are close mirror pairs. The descriptions provide explicit cross-references and decision rules, so an attentive agent can choose correctly, but the set requires careful reading.

    Naming Consistency4/5

    Most tools use a consistent get_<Resource> pattern (getPoolDetails, getNetworkPools, getTokenIndicator, getNetworkDexes, etc.). The exceptions are search and filterNetworkTokens, with filterNetworkTokens notably breaking the parallel convention set by getNetworkPoolsFilter.

    Tool Count3/5

    20 tools fall in the 16-25 range that feels heavy for a single MCP server, especially with parallel pool/token variants and separate top-list versus filter tools. Each tool has a distinct role, but consolidation is plausible for several pairs.

    Completeness4/5

    The surface covers the domain well: networks, DEXes, pools, tokens, detail views, OHLCV history, indicators, transactions, batch prices, global search, platform stats, and diagnostics. Minor gaps exist (e.g., no single-DEX detail endpoint and no token-level transaction feed), but agents can work around them via pool-level tools.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources