claude mcp add dexpaprika-mcp -- npx -y dexpaprika-mcp
A pasteable skeleton generated from the repository name. Check the project README for the exact package and arguments.
Star count
56 โ ยท coinpaprika/dexpaprika-mcp ยท read from the repository page ยท (checked 2026-10-16 20:00:20)
Source
collected from the punkpeye/awesome-mcp-servers list ยท type: MCP server
Harvest history
first seen 2026-10-09 ยท last seen 2026-10-16 ยท seen 32ร ยท listed by 10 sources
Score
score 1,003 ยท 56 โ ยท 10 sources ยท mcp
FAQ (answers come from our records)
How do I install it?
We did not find an install command for this repository (our install coverage is only about 4%). Check its README or releases page.
Who is it for?
We filed it under these tags: MCP ๆๅก. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository coinpaprika/dexpaprika-mcp๏ผfirst catalogued 2026-10-09๏ผlast seen 2026-10-16ใThere is no official certification or quality rating here โ we record sources and dates only.
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. TL;DR 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. Latest release See CHANGELOG.md for release notes and migration guides. What Can You Build? - **Token Analysis Tools**: Track price movements, liquidity depth changes, and volume patterns - **DEX Comparisons**: Analyze fee structures, volume, and available pools across different DEXes - **Liquidity Pool Analytics**: Monitor TVL changes, impermanent loss calculations, and price impact assessments - **Market Analysis**: Cross-chain token comparisons, volume trends, and trading activity metrics - **Portfolio Trackers**: Current value tracking, historical performance analysis, yield opportunities - **Technical Analysis**: Perform advanced technical analysis using historical OHLCV data, including trend identification, pattern recognition, and indicator calculations Installation Installing via Smithery To install DexPaprika for Claude Desktop automatically via Smithery: Manual Installation This is a stdio server: it speaks MCP over stdin and stdout and binds no port. On start it writes DexPaprika MCP server v (tool contract v ) 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. Video Tutorial Watch our step-by-step tutorial on setting up and using the DexPaprika MCP server: Claude Desktop Integration 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. Optional: using an API key **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, as the entire Authorization value.** Paste it exactly as issued, with nothing in front of it. Almost every other API wants something in front of the key, so this is the single most common reason a working key looks broken. Two things worth knowing: - **A key we cannot read does not produce an error.** The data endpoints ignore an unreadable key and serve you as an anonymous caller, with a normal 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. - **Dev and Pro customers** additionally set DEXPAPRIKA_API_BASE_URL to https://api-pro.dexpaprika.com, which is also what getTokenOHLCV needs. The host does not change automatically, because sending a free key to that host returns 403. Hosted server (no installation) 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: