Skip to main content
Glama
coinpaprika

DexPaprika (CoinPaprika)

Official

Related Servers

Alternatives to DexPaprika (CoinPaprika)

No user-submitted related servers found.

    Related Servers

    • 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
    • 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
      151 npm
      MIT
    • 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
    • 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
    • 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.
      5 npm
      1
      MIT

    TDQS

    A4.5/5.0

    Scored across 17 tools

    Disambiguation4/5

    Most tools are clearly separated by resource type (pools, tokens, networks, DEXes) and action (list, filter, details, OHLCV, transactions). The only mild overlap is between getNetworkPools and getNetworkPoolsFilter, and between getTopTokens and filterNetworkTokens, but their descriptions explicitly distinguish ranking vs. filtering.

    Naming Consistency4/5

    The naming follows a consistent get<Resource><Detail> pattern (getPoolDetails, getTokenPools, getNetworkDexes, getTopTokens). Minor deviations: 'search' and 'filterNetworkTokens' break the get prefix, and getNetworkPoolsFilter is slightly awkward compared to filterNetworkTokens, but overall the pattern is predictable.

    Tool Count5/5

    17 tools is on the higher end but appropriate for a DEX data API covering networks, DEXes, pools, tokens, transactions, OHLCV, and platform stats. Each tool serves a distinct data access pattern, and the count reflects the breadth of the domain without being bloated.

    Completeness4/5

    The surface covers the core read-only DEX data domain well: network discovery, DEX discovery, pool listing/filtering/details/OHLCV/transactions, token details/pools/multi-prices/filtering/top, search, and platform stats. Minor gaps: no direct token price history endpoint (only pool OHLCV) and no per-DEX aggregate stats, but agents can work around these via existing tools.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive