The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Dexpaprika MCP listing page.
A Model Context Protocol (MCP) server that provides on-demand access to DexPaprika's cryptocurrency and DEX data API. Built specifically for AI assistants like Claude to programmatically fetch current token, pool and DEX data with zero configuration.
DexPaprika MCP connects Claude to live DEX data across multiple blockchains. The free tier needs no API key to start. Installation | Configuration | API Reference
Prefer zero setup? Use the hosted MCP server at mcp.dexpaprika.com: no installation, no key to start, the same data tools plus
submitFeedback. See Hosted server for transport endpoints.
See CHANGELOG.md for release notes and migration guides.
To install DexPaprika for Claude Desktop automatically via Smithery:
This is a stdio server: it speaks MCP over stdin and stdout and binds no port. On start it writes DexPaprika MCP server v<version> (tool contract v<contract>) is running... to stderr and then waits for a client. Run it from an MCP client (Claude Desktop, Cursor, Claude Code) rather than expecting a URL in a browser.
Watch our step-by-step tutorial on setting up and using the DexPaprika MCP server:
Add the following to your Claude Desktop configuration file:
macOS: ~/Library/Application\ Support/Claude/claude_desktop_config.json
Windows: %APPDATA%/Claude/claude_desktop_config.json
After restarting Claude Desktop, the DexPaprika tools will be available to Claude automatically.
This works without a key and always will. No signup, no card, nothing to configure. Everything above is the supported way to run it.
A free key raises the monthly allowance and opens streaming on any token rather than the public showcase set. It does not raise the per-minute request limit, which is the same on both tiers. Get one at console.dexpaprika.com; current limits are on the rate limits page.
The key goes in on its own. There is no Bearer prefix, and no other scheme
word either. Paste the key exactly as issued. Almost every other API wants the
opposite, so this is the single most common reason a working key looks broken.
Two things worth knowing:
200 and
real data, so a typo looks exactly like success. Ask the assistant to run
getKeyStatus after setting one: it reports which plan the API actually sees
and names the likely cause when the key is not landing.DEXPAPRIKA_API_BASE_URL to
https://api-pro.dexpaprika.com. The host does not change automatically,
because sending a free key to that host returns 403.If you prefer zero setup, point any MCP-compatible client directly at the hosted server at mcp.dexpaprika.com. The landing page provides setup instructions and documentation. The following transport endpoints are available:
| Transport | Endpoint | Use Case |
|---|---|---|
| Streamable HTTP | https://mcp.dexpaprika.com/streamable-http | Recommended for most clients |
| SSE | https://mcp.dexpaprika.com/sse | Legacy SSE transport |
| JSON-RPC | https://mcp.dexpaprika.com/json-rpc | Direct JSON-RPC |
Note: These are MCP protocol endpoints. They won't display anything in a browser. Visit mcp.dexpaprika.com for the landing page.
This self-host build registers 17 read tools: 16 market-data tools plus getKeyStatus. The hosted server at mcp.dexpaprika.com registers its own set including submitFeedback. Verify either with a live tools/list.
| Tool | Description |
|---|---|
getCapabilities | Server capabilities, workflow patterns, network synonyms, and best practices. Start here. |
getNetworks | List every supported blockchain network (36) |
getStats | High-level ecosystem stats (total networks, DEXes, pools, tokens) |
search | Search tokens, pools, and DEXes across ALL networks by name, symbol, or address |
getKeyStatus | Whether a key is being sent and which plan the API sees. Reads no market data. |
| Tool | Description | Required Parameters |
|---|---|---|
getNetworkDexes | List DEXes on a specific network | network |
| Tool | Description | Required Parameters |
|---|---|---|
getNetworkPools | PRIMARY. Get top liquidity pools on a network | network |
getDexPools | Get pools from a specific DEX (rows under results, cursor pagination) | network, dex |
getNetworkPoolsFilter | Filter pools by volume, transactions, creation time | network |
getPoolDetails | Detailed pool info (price, volume, TVL, tokens) | network, pool_address |
getPoolOHLCV | Historical OHLCV candle data | network, pool_address, start |
getPoolTransactions | Recent transactions/trades for a pool | network, pool_address |
| Tool | Description | Required Parameters |
|---|---|---|
getTokenDetails | Detailed token information | network, token_address |
getTokenPools | Liquidity pools containing a token (network-scoped filter, results + cursor pagination) | network, token_address |
getTokenMultiPrices | Batched prices for up to 10 tokens | network, tokens[] |
getTopTokens | Top tokens on a network ranked by volume, liquidity, FDV, or 24h price change | network |
filterNetworkTokens | Filter tokens by volume, liquidity, FDV, transactions, and creation time | network |
Common Issues:
DP429_RATE_LIMIT errors, implement exponential backoffgetPoolTransactions insteadSee CHANGELOG.md for detailed release notes and migration guides.
This project is licensed under the MIT License - see the LICENSE file for details.