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
      1,407 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.
      10 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.4/5.0

    Scored across 18 tools

    Disambiguation4/5

    Most tools target clearly distinct resource+action pairs (details vs OHLCV vs transactions for pools; single vs batch vs multi-timeframe for tokens), and each description explicitly states when to prefer a sibling tool. The only mild overlap is the cluster of pool-listing tools (getNetworkPools, getDexPools, getNetworkPoolsFilter) and token-listing tools (getTopTokens, filterNetworkTokens), but numeric-vs-ranked/scope distinctions are spelled out.

    Naming Consistency4/5

    The set overwhelmingly follows a camelCase get_<resource> pattern (getTokenDetails, getPoolOHLCV, getNetworkDexes, getStats). Two outliers break the pattern: 'filterNetworkTokens' (verb differs from its sibling getTopTokens) and the bare 'search', plus a slightly clunky getNetworkPoolsFilter vs filterNetworkTokens asymmetry. Minor deviations, still highly readable.

    Tool Count4/5

    18 tools is on the heavier side but justified by a genuinely broad domain spanning networks, DEXes, pools, tokens, transactions, OHLCV, plus meta tools (getCapabilities, getKeyStatus, getStats). Each tool maps to a real scope (network-wide vs single-DEX vs filtered) rather than being redundant padding.

    Completeness4/5

    The read-only surface covers the full lifecycle well: discovery (search), networks/dexes, pool and token listings with filters, detail snapshots, historical OHLCV for both pools and tokens, raw transaction feeds, and coverage/onboarding metadata. Minor gaps exist (no token-level aggregated transaction feed, no direct symbol lookup without search), but actionable fallbacks and cross-references between tools largely compensate.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources