Dexpaprika MCP logo

Dexpaprika MCP

by coinpaprika

Read-only MCP access to DexPaprika’s cross-chain token, DEX, liquidity pool, pricing, and historical market data.

Install Dexpaprika MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "coinpaprika-dexpaprika-mcp": {
      "command": "npx",
      "args": [
        "dexpaprika-mcp@latest"
      ],
      "env": {
        "DEXPAPRIKA_API_KEY": "YOUR_VALUE_HERE",
        "DEXPAPRIKA_API_BASE_URL": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Install not yet sandbox-tested— the server itself is confirmed live (we called its tools/list endpoint). The stdio install command is a separate, ongoing check.

Overview

coinpaprika/dexpaprika-mcp connects MCP-compatible AI clients to DexPaprika’s cryptocurrency and decentralized exchange data API. It covers indexed blockchain networks with tools for discovery, token and pool snapshots, DEX listings, batched prices, OHLCV history, transactions, and threshold-based filtering. The server runs locally over stdio with no API key required, while an optional key can increase monthly allowance and unlock broader streaming access. Reach for it when an agent needs structured, network-aware DEX market data rather than a general blockchain RPC interface.

Use cases

  • Find tokens, pools, or DEXes across indexed networks
  • Compare liquidity pools and DEX activity on a chain
  • Track current token prices and pool TVL
  • Analyze historical pool OHLCV candles
  • Filter markets by volume, liquidity, or creation time

Key features

  • Cross-network token, pool, and DEX search
  • Network and platform coverage discovery
  • Current token and pool market snapshots
  • Cursor-paginated pool and token queries
  • Historical pool OHLCV and swap data
  • Batched pricing for up to 10 tokens

Tools17

What Dexpaprika MCP lets your agent do. Expand a tool for its parameters.

Verified live~9.7k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

21/21 checks healthy over the last 79d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 11d ago via OSV.dev · dexpaprika-mcp@latest (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars116Stargazers on the source repository.
npm downloads834Package downloads in the last 30 days.
Last commit5d agoMost recent push to the default branch.
Tools exposed17Callable tools this server registers over MCP.
Directory activity2 viewsConfig copies, upvotes, and views on AllMCPs.

How Dexpaprika MCP works

What coinpaprika/dexpaprika-mcp does

coinpaprika/dexpaprika-mcp exposes DexPaprika market data through the Model Context Protocol. It gives AI clients read-only access to indexed blockchain networks, decentralized exchanges, liquidity pools, tokens, prices, historical candles, and recent pool swaps.

The data is organized around network and contract identifiers. Discovery tools help resolve a chain slug, token address, pool address, or DEX identifier before a more specific query. Cross-network search can find tokens, pools, and DEXes by name, symbol, or address. Platform statistics provide aggregate counts across the indexed ecosystem.

Use this server for market research, token and pool monitoring, DEX comparisons, portfolio snapshots, historical price analysis, and queries that combine liquidity, volume, transaction, or creation-time conditions.

How it works

The local server communicates with an MCP client through stdin and stdout and does not bind a network port. Install the npm package globally or launch it on demand with npx. Once connected, the client can call the registered tools and receive structured responses from DexPaprika.

A typical workflow begins with getCapabilities for usage guidance or getNetworks for canonical network slugs. Use search when the network or contract address is unknown. Network-scoped tools then expose DEXes, pools, tokens, and rankings. Pool and token endpoints return either a single object or paginated arrays, depending on the operation.

Pagination uses page numbers for some transaction responses and cursors for pool and token collections. OHLCV requests accept Unix timestamps, RFC3339 values, or dates, with selectable candle intervals.

Setup and configuration

Install the package globally:

Terminal
npm install -g dexpaprika-mcp
dexpaprika-mcp

Alternatively, run npx dexpaprika-mcp@latest from an MCP client configuration. A Claude Desktop entry can use npx as the command with dexpaprika-mcp@latest as its argument. The server is also available as a hosted MCP endpoint with Streamable HTTP, SSE, and JSON-RPC transports at mcp.dexpaprika.com.

The free tier works without configuration or an API key. Set DEXPAPRIKA_API_KEY when using a key, placing the complete issued value in the environment. getKeyStatus reports whether the API is receiving the key and which plan it recognizes. Dev and Pro customers also set DEXPAPRIKA_API_BASE_URL to the Pro API host.

Tools and capabilities

  • Discover supported networks, platform totals, network aliases, DEXes, pools, tokens, and search matches.
  • Rank network pools or tokens by volume, liquidity, transactions, FDV, or 24-hour price change.
  • Filter pools and tokens with numeric thresholds, transaction counts, liquidity ranges, volume ranges, and creation timestamps.
  • Retrieve current pool snapshots containing token, price, liquidity or TVL, volume, and transaction data.
  • Retrieve token metadata, multi-timeframe metrics, social links, and network-specific pool associations.
  • Request current USD prices for up to 10 tokens on the same network in one call.
  • Fetch pool OHLCV candles and recent individual swap transactions.

Limitations and notes

All listed operations are read-only; the server does not submit trades or mutate blockchain state. Most queries require the canonical network slug, and token, pool, and DEX lookups are network-scoped after discovery. A DEX pool query requires the DEX identifier rather than its display name.

The free, keyless service is subject to DexPaprika’s request and plan limits. Some paginated pool and token results require a key beyond the first page. OHLCV ranges are bounded: pool candles allow an end date no more than one year after the start, and pool transaction time filters cover at most the last seven days. Batched token pricing is limited to 10 addresses per request, and unknown search or token matches can return empty arrays rather than errors.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Dexpaprika MCP

coinpaprika/dexpaprika-mcp is an MCP server that connects AI clients to DexPaprika’s cryptocurrency and DEX data API. Its main tools discover networks, tokens, pools, and exchanges, then retrieve prices, liquidity, volume, OHLCV history, token metadata, and recent pool transactions across supported chains.

Install it with `npm install -g dexpaprika-mcp` and start it with `dexpaprika-mcp`, or run `npx dexpaprika-mcp@latest` from your MCP client configuration. The local server uses stdio and does not provide a browser URL.

No, the free tier runs without an API key. Set `DEXPAPRIKA_API_KEY` for a higher monthly allowance and broader streaming access, then use `getKeyStatus` to check whether DexPaprika recognizes the key and plan.

Yes, it works with Cursor through its standard stdio MCP configuration. Start the local command from Cursor, or configure the hosted Streamable HTTP endpoint at `https://mcp.dexpaprika.com/streamable-http`.

Use `search` to find tokens, pools, and DEXes across all networks, or use `getNetworks` to list canonical network slugs. After discovery, pass the returned network and contract identifiers to network-scoped tools such as `getTokenDetails`, `getTokenPools`, or `getPoolDetails`.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewDexpaprika MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/coinpaprika-dexpaprika-mcp?style=directory)](https://allmcps.com/mcp/coinpaprika-dexpaprika-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/coinpaprika-dexpaprika-mcp"><img src="https://allmcps.com/api/badge/coinpaprika-dexpaprika-mcp?style=directory" alt="Dexpaprika MCP on AllMCPs" /></a>