DexPaprika MCP Server

Official

Real-time multi-chain DEX and on-chain data via MCP

How to install ↓ Compare GitHub source repository ↗

Category: Other #10 of 230
Stars: ★ 97 Popular
Transport: stdio (local process) · Streamable HTTP · SSE
Runtime: Node.js · Hosted (no local runtime)
Credentials: Optional API key
License: MIT
Last commit: 6 days ago
Tools: 17

70FMRS · B

A well-maintained multi-chain DEX data MCP server with 16 read-only tools (hosted adds submitFeedback), keyless free tier, and thorough docs and examples. Great for DeFi analytics; not suitable for on-chain writes or strict real-time needs.

Strongest · Documentation 17/20 Weakest · Reliability 9/20

Reliability

9/20

Security and permissions

16/20

Maintenance

14/20

Documentation

17/20

Setup experience

14/20

Why each score

Reliability 9/20: The README is internally detailed — it claims 16 read-only tools on the self-hosted build vs 17 on the hosted server (extra `submitFeedback`), and even documents the exact stderr startup banner (version + 'tool contract' version), which suggests some engineering discipline. However, server.json only declares two hosted `remotes` (streamable-http, sse) and has no `packages` entry for the npm/npx self-host path that the README repeatedly emphasizes as the primary install method — a manifest/README mismatch. No CI workflow or test files were supplied as evidence; the README references `npm test`/`npm run watch` scripts but no verifiable test coverage or CI logs were seen. Per the static calibration rule, reliability is capped at 12 without such evidence, and further deducted for the manifest gap and unverifiable claims.
Security and permissions 16/20: All 16–17 tools are read-only queries against on-chain/market data (prices, pools, volume, OHLCV, etc.) with no evidence of file writes, shell execution, credential forwarding, or irreversible actions — consistent with least privilege. The free tier requires no API key, and paid keys only raise rate limits; no plaintext secrets appear in install examples. Points withheld because the hosted server's extra `submitFeedback` tool and the data flow to mcp.dexpaprika.com (logging/retention of queries) are not clearly disclosed, and the README does not explicitly bound what data crosses the network boundary.
Maintenance 14/20: The repo shows an MIT license, an explicit version (2.4.0), a referenced CHANGELOG.md, and modest but real community signal (42 stars, 2 open issues, not archived) — indicating some ongoing upkeep. However, the provided metadata cannot verify actual commit cadence, issue response times, or a security-response channel, and no clear maintainer identity/ownership statement is given, so a high score is not warranted.
Documentation 17/20: The README is well structured: install options (global npm, npx, Smithery, hosted server), Claude Desktop config examples, a categorized table of all 16 tools with parameters, rate-limit/credit economics, error codes and a troubleshooting section, sample prompts, and a changelog link — a good layered evidence trail with real examples. Deductions for not disclosing the hosted service's data retention/privacy policy and for leaving the tool-version-to-'tool contract' manifest relationship only partially explained, which is a hidden assumption.
Setup experience 14/20: Multiple straightforward paths are offered: global npm install, npx one-liner, Smithery one-command install, and a zero-config hosted streamable-http/SSE endpoint, plus JSON config examples for Claude Desktop on both macOS and Windows — genuinely low friction. Per the static calibration rule, setup is capped at 15 absent verifiable CI+test execution evidence; an additional point is withheld because server.json's manifest does not declare a local package entry matching the npm-based install path the README treats as primary, casting some doubt on the manifest's completeness.

Static review · not runListed 2026-09-07

Read the FMRS scoring method →

Fit and risk

What it can accessUses the network

Best for

AI assistant users needing multi-chain DEX and on-chain data
DeFi analysts and market researchers
Developers building token and pool analysis tools

Not for

Scenarios needing on-chain writes, trade execution, or private-key management
CEX market data needs (this server focuses on DEX/on-chain data)
Users requiring truly real-time data on a free budget (free tier delays up to 15 seconds)

Required permissions

Requires internet access to call the DexPaprika API
Node.js/npm for local stdio installation
No API key needed for the free tier (a free key raises quota)

Risks and side effects

Free-tier rate limits (200,000 credits/month per IP, 30 requests/minute) can trigger DP429_RATE_LIMIT errors
Free tier data delayed up to 15 seconds; not for truly real-time use
Some newer tokens/pools may have incomplete historical data
Price and on-chain data are informational only, not investment advice

Setup

Before you start

Runtime：Node.js · Hosted (no local runtime)

Install with npm install -g dexpaprika-mcp, then run dexpaprika-mcp; or run directly with npx dexpaprika-mcp@latest. Alternatively install via Smithery: npx -y smithery mcp add coinpaprika/dexpaprika. Zero-setup option: point an MCP client at https://mcp.dexpaprika.com/streamable-http (hosted endpoint). Add a dexpaprika entry to your Claude Desktop config file and restart.

claude_desktop_config.json

{"mcpServers":{"dexpaprika":{"command":"npx","args":["dexpaprika-mcp@latest"]}}}

Shown for Claude Desktop. Other clients may use a different file or key (VS Code uses "servers") — the configurator below converts it.

.vscode/mcp.json

{
  "servers": {
    "dexpaprika": {
      "command": "npx",
      "args": [
        "dexpaprika-mcp@latest"
      ]
    }
  }
}

Goes in your project's .vscode/mcp.json (VS Code uses a "servers" key).

Terminal

claude mcp add dexpaprika -- npx dexpaprika-mcp@latest

Run it in a terminal; replace any <…> placeholders with your own values first.

Generate and validate client config

Check that it works

After adding the config and restarting Claude Desktop, the tool list should include getCapabilities and getNetworkPools; calling getNetworks should return the 36 supported blockchain networks.

Troubleshooting

On DP429_RATE_LIMIT errors, implement exponential backoff
OHLCV max range between start and end dates is 1 year; paginate for longer timeframes
Empty OHLCV may mean the pool is too new; use getPoolTransactions instead
Large data requests may time out; use pagination
The server is a stdio process launched by an MCP client (Claude Desktop, Cursor, Claude Code), not a browser URL

Things to try

Once connected, you can ask your AI assistant things like:

Analyze the JUP token on Solana: fetch its price, volume, and top liquidity pools.
Compare trading volume between Uniswap V3 and SushiSwap on Ethereum.
Get 7-day OHLCV data for the SOL/USDC pool on Raydium.
Show me the top 10 pools on Ethereum by 24h volume.

Tools 17

getCapabilities read-only

Returns server capabilities, workflow patterns, network synonyms, and best practices. Start here.

getNetworks read-only

Lists all 36 supported blockchain networks.

getStats read-only

Returns high-level ecosystem stats (networks, DEXes, pools, tokens).

search read-only

Search tokens, pools, and DEXes across all networks by name, symbol, or address.

getNetworkDexes read-only

Lists DEXes on a specific network.

getNetworkPools read-only

PRIMARY tool. Gets top liquidity pools on a network.

getDexPools read-only

Gets pools from a specific DEX.

getNetworkPoolsFilter read-only

Filters pools by volume, transactions, and creation time.

Show 9 more tools

getPoolDetails read-only

Detailed pool info (price, volume, TVL, tokens).

getPoolOHLCV read-only

Historical OHLCV candle data.

getPoolTransactions read-only

Recent transactions/trades for a pool.

getTokenDetails read-only

Detailed token information.

getTokenPools read-only

Liquidity pools containing a token (network-scoped filter, results + cursor pagination).

getTokenMultiPrices read-only

Batched prices for up to 10 tokens.

getTopTokens read-only

Top tokens on a network ranked by volume, liquidity, FDV, or 24h price change.

filterNetworkTokens read-only

Filters tokens by volume, liquidity, FDV, transactions, and creation time.

submitFeedback writes

Hosted server only: submit feedback.

Use cases

Track token price movements, liquidity depth changes, and volume patterns

Compare fee structures, volume, and pools across DEXes

Monitor TVL changes and assess price impact

Perform technical analysis with historical OHLCV data

Build portfolio trackers and yield analysis tools

Supported clients

Claude Desktop

CursorPartial support

Claude CodePartial support

Listed from the project's documentation, not tested by this site.

Overview

DexPaprika MCP Server, maintained by CoinPaprika, provides on-demand access to DexPaprika's crypto and DEX data API covering token prices, liquidity pools, trading volume, OHLCV history, and transactions across 36 blockchain networks. It runs locally over stdio via npm, or use the official hosted endpoint (streamable-http / sse / -rpc). The free tier requires no API key to start.

Similar servers

Hevy MCP 77 · B

Manage your Hevy workout data from AI assistants via MCP.

★ 517 · Tools 26 Compare with this →

Firecrawl MCP Server 75 · B

Firecrawl's official MCP server for web search, scraping, and structured extraction for AI agents

★ 7.6k · Tools 11 Compare with this →

BioMCP 75 · B

One binary. One grammar. Evidence from the biomedical sources you already trust.

★ 659 · Tools 11 Compare with this →

Compartment 75 · B

Encrypted, fully offline long-term memory for AI agents

★ 583 · Tools 14 Compare with this →

Compare with other MCP servers

Source revision ed6d71152708 Data synced 2026-10-19 Read the FMRS scoring method