DexPaprika▌
by coinpaprika
Get live crypto exchange data & coin stock prices on DexPaprika. Track bitcoin price live, DEX listings, and more across
Provides real-time cryptocurrency market data across multiple blockchain networks, including DEX listings, liquidity pools, token details, and price analytics without requiring API keys.
Both formats append explainx.ai attribution and the canonical URL for this MCP server listing.
best for
- / DeFi researchers analyzing liquidity and trading patterns
- / Crypto traders tracking token prices across DEXes
- / Developers building crypto portfolio and analytics tools
- / Financial analysts performing cross-chain market research
capabilities
- / Query liquidity pools across blockchain networks
- / Get detailed token information and trading data
- / Retrieve historical price data (OHLCV) for pools
- / Search tokens, pools, and DEXes by name or address
- / Fetch recent pool transactions and trading activity
- / Get available DEXes and supported blockchain networks
what it does
Provides real-time cryptocurrency market data across multiple blockchain networks including DEX listings, liquidity pools, token details, and price analytics. Works across all networks and DEXes without requiring API keys.
about
DexPaprika is an official MCP server published by coinpaprika that provides AI assistants with tools and capabilities via the Model Context Protocol. Get live crypto exchange data & coin stock prices on DexPaprika. Track bitcoin price live, DEX listings, and more across It is categorized under finance, analytics data. This server exposes 12 tools that AI clients can invoke during conversations and coding sessions.
how to install
You can install DexPaprika in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport. This server supports remote connections over HTTP, so no local installation is required.
license
MIT
DexPaprika is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
readme
DexPaprika MCP Server
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 real-time token, pool, and DEX data with zero configuration.
TL;DR
# Install globally
npm install -g dexpaprika-mcp
# Start the server
dexpaprika-mcp
# Or run directly without installation
npx dexpaprika-mcp
DexPaprika MCP connects Claude to live DEX data across multiple blockchains. No API keys required. Installation | Configuration | API Reference
🚨 Version 1.2.0 Update Highlights
New: Batched token prices tool getTokenMultiPrices and enhanced getNetworkDexes parameters. See examples below.
🚨 Version 1.1.0 Update Notice
Breaking Change: The global /pools endpoint has been removed. If you're upgrading from v1.0.x, please see the Migration Guide below.
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: Real-time 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:
npx -y @smithery/cli install @coinpaprika/dexpaprika-mcp --client claude
Manual Installation
# Install globally (recommended for regular use)
npm install -g dexpaprika-mcp
# Verify installation
dexpaprika-mcp --version
# Start the server
dexpaprika-mcp
The server runs on port 8010 by default. You'll see MCP server is running at http://localhost:8010 when successfully started.
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
{
"mcpServers": {
"dexpaprika": {
"command": "npx",
"args": ["dexpaprika-mcp"]
}
}
}
After restarting Claude Desktop, the DexPaprika tools will be available to Claude automatically.
Migration from v1.0.x to v1.1.0
⚠️ Breaking Changes
The global getTopPools function has been removed due to API deprecation.
Migration Steps
Before (v1.0.x):
// This will no longer work
getTopPools({ page: 0, limit: 10, sort: 'desc', orderBy: 'volume_usd' })
After (v1.1.0):
// Use network-specific queries instead
getNetworkPools({ network: 'ethereum', page: 0, limit: 10, sort: 'desc', orderBy: 'volume_usd' })
getNetworkPools({ network: 'solana', page: 0, limit: 10, sort: 'desc', orderBy: 'volume_usd' })
// To query multiple networks, call getNetworkPools for each network
// Or use the search function for cross-network searches
Benefits of the New Approach
- Better Performance: Network-specific queries are faster and more efficient
- More Relevant Results: Get pools that are actually relevant to your use case
- Improved Scalability: Better suited for handling large amounts of data across networks
Technical Capabilities
The MCP server exposes these specific endpoints Claude can access:
Network Operations
| Function | Description | Example |
|---|---|---|
getNetworks | Retrieves all supported blockchain networks and metadata | {"id": "ethereum", "name": "Ethereum", "symbol": "ETH", ...} |
getNetworkDexes | Lists DEXes available on a specific network | {"dexes": [{"id": "uniswap_v3", "name": "Uniswap V3", ...}]} |
Pool Operations
| Function | Description | Required Parameters | Example Usage |
|---|---|---|---|
getNetworkPools | [PRIMARY] Gets top pools on a specific network | network, limit | Get Solana's highest liquidity pools |
getDexPools | Gets top pools for a specific DEX | network, dex | List pools on Uniswap V3 |
getPoolDetails | Gets detailed pool metrics | network, poolAddress | Complete metrics for USDC/ETH pool |
getPoolOHLCV | Retrieves time-series price data for various analytical purposes (technical analysis, ML models, backtesting) | network, poolAddress, start, interval | 7-day hourly candles for SOL/USDC |
getPoolTransactions | Lists recent transactions in a pool | network, poolAddress | Last 20 swaps in a specific pool |
Token Operations
| Function | Description | Required Parameters | Output Fields |
|---|---|---|---|
getTokenDetails | Gets comprehensive token data | network, tokenAddress | price_usd, volume_24h, liquidity_usd, etc. |
getTokenPools | Lists pools containing a token | network, tokenAddress | Returns all pools with liquidity metrics |
getTokenMultiPrices | Batched USD prices for multiple tokens | network, tokens[] | Array of { id, chain, price_usd } |
search | Finds tokens, pools, DEXes by name/id | query | Multi-entity search results |
Example Usage
// With Claude, get details about a specific token:
const solanaJupToken = await getTokenDetails({
network: "solana",
tokenAddress: "JUPyiwrYJFskUPiHa7hkeR8VUtAeFoSYbKedZNsDvCN"
});
// Find all pools for a specific token with volume sorting:
const jupiterPools = await getTokenPools({
network: "solana",
tokenAddress: "JUPyiwrYJFskUPiHa7hkeR8VUtAeFoSYbKedZNsDvCN",
orderBy: "volume_usd",
limit: 5
});
// Get top pools on Ethereum (v1.1.0 approach):
const ethereumPools = await getNetworkPools({
network: "ethereum",
orderBy: "volume_usd",
limit: 10
});
// Get historical price data for various analytical purposes (technical analysis, ML models, backtesting):
const ohlcvData = await getPoolOHLCV({
network: "ethereum",
poolAddress: "0x88e6a0c2ddd26feeb64f039a2c41296fcb3f5640", // ETH/USDC on Uniswap V3
start: "2023-01-01",
interval: "1d",
limit: 30
});
// 1.2.0: Get batched prices for multiple tokens (repeatable tokens query)
const prices = await getTokenMultiPrices({
network: "ethereum",
tokens: [
"0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2", // WETH
"0xdac17f958d2ee523a2206206994597c13d831ec7" // USDT
]
});
Sample Prompts for Claude
When working with Claude, try these specific technical queries (updated for v1.1.0):
- "Analyze the JUP token on Solana. Fetch price, volume, and top liquidity pools."
- "Compare trading volume between Uniswap V3 and SushiSwap on Ethereum."
- "Get the 7-day OHLCV data for SOL/USDC on Raydium and plot a price chart."
- "Find the top 5 pools by liquidity on Fantom network and analyze their fee structures."
- "Get recent transactions for the ETH/USDT pool on Uniswap and analyze buy vs sell pressure."
- "Show me the top 10 pools on Ethereum by 24h volume using getNetworkPools."
- "Search for all pools containing the ARB token and rank them by volume."
- "Retrieve OHLCV data for BTC/USDT to analyze volatility patterns and build a price prediction model."
- "First get all available networks, then show me the top pools on each major network."
Rate Limits & Performance
- Free Tier Limits: 60 requests per minute
- Response Time: 100-500ms for most endpoints (network dependent)
- Data Freshness: Pool and token data updated every 15-30s
- Error Handling: 429 status codes indicate rate limiting
- OHLCV Data Availability: Historical data typically available from token/pool creation date
Troubleshooting
Common Issues:
- Rate limiting: If receiving 429 errors, reduce request frequency
- Missing data: Some newer tokens/pools may have incomplete historical data
- Timeout errors: Large data requests may take longer, consider pagination
- Network errors: Check network connectivity, the service requires internet access
- OHLCV limitations: Maximum range between start and end dates is 1 year; use pagination for longer timeframes
Migration Issues:
- "getTopPools not found": This function has been removed. Use
getNetworkPoolsinstead with a specific network parameter - "410 Gone" errors: You're using a deprecated endpoint. Check the error message for guidance on the correct endpoint to use
Development
# Clone the repository
git clone https://github.com/coinpaprika/dexpaprika-mcp.git
cd dexpaprika-mcp
# Install dependencies
npm install
# Run with auto-restart on code changes
npm run watch
# Build for production
npm run build
# Run tests
npm test
Changelog
See CHANGELOG.md for detailed release notes and migration guides.
License
This project is licensed under the MIT License - see the LICENSE file for details.
Additional Resources
- DexPaprika API Documentation
- Model Context Protocol Specification
- DexPaprika - Comprehensive onchain analytics market data
- CoinPaprika - Compr
FAQ
- What is the DexPaprika MCP server?
- DexPaprika is a Model Context Protocol (MCP) server profile on explainx.ai. MCP lets AI hosts (e.g. Claude Desktop, Cursor) call tools and resources through a standard interface; this page summarizes categories, install hints, and community ratings.
- How do MCP servers relate to agent skills?
- Skills are reusable instruction packages (often SKILL.md); MCP servers expose live capabilities. Teams frequently combine both—skills for workflows, MCP for APIs and data. See explainx.ai/skills and explainx.ai/mcp-servers for parallel directories.
- How are reviews shown for DexPaprika?
- This profile displays 31 aggregated ratings (sample rows for discoverability plus signed-in user reviews). Average score is about 4.7 out of 5—verify behavior in your own environment before production use.
Use Cases▌
Extended AI Capabilities
Add new capabilities to Claude beyond text generation
Example
Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Context Enhancement
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Workflow Automation
Automate multi-step workflows combining AI and external tools
Example
Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Implementation Guide▌
Prerequisites
- ›Claude Desktop 0.7.0+ or Cursor IDE with MCP support
- ›Basic understanding of MCP architecture and capabilities
- ›Access credentials for integrated services (if required)
- ›Willingness to experiment and iterate on configuration
Time Estimate
15-60 minutes depending on server complexity
Installation Steps
- 1.Install MCP server: npm install -g [package-name] or via GitHub
- 2.Add server configuration to ~/.claude/mcp.json
- 3.Provide required credentials and configuration
- 4.Restart Claude Desktop to load new server
- 5.Test basic functionality with simple prompts
- 6.Explore capabilities and experiment with use cases
- 7.Document successful patterns for reuse
Troubleshooting
- ⚠MCP server not loading: Check config syntax, verify installation
- ⚠Connection errors: Check network, firewall, credentials
- ⚠Feature not working: Read server docs, check required parameters
- ⚠Performance issues: Monitor resource usage, check for network latency
- ⚠Conflicts with other servers: Check port assignments, namespace collisions
Best Practices▌
✓ Do
- +Read server documentation thoroughly before setup
- +Start with simple use cases to validate functionality
- +Test in non-production environment first
- +Monitor resource usage and performance
- +Keep servers updated for bug fixes and new features
- +Document configuration for team members
- +Use environment variables for sensitive configuration
✗ Don't
- −Don't grant overly permissive access to MCP servers
- −Don't skip reading security considerations in docs
- −Don't expose sensitive data without proper controls
- −Don't run untrusted MCP servers without code review
- −Don't ignore error messages—investigate root cause
💡 Pro Tips
- ★Combine multiple MCP servers for powerful workflows
- ★Create custom MCP servers for your specific needs
- ★Share successful configurations with team
- ★Use MCP inspector for debugging
- ★Join MCP community for tips and troubleshooting
Technical Details▌
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
- Model Context Protocol (MCP)
- JSON-RPC 2.0
- stdio or HTTP transport
Compatibility
- Claude Desktop
- Cursor IDE
- Custom MCP clients
When to Use This▌
✓ Use When
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid When
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.
Integration▌
- →Tool composition: Chain multiple MCP tools in workflows
- →Context augmentation: Provide AI with relevant external data
- →Action delegation: Let AI execute tasks on external systems
- →Bidirectional sync: Keep AI context and external systems in sync
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
List & Promote Your MCP Server
Share your MCP server with the developer community
Ratings
4.7★★★★★31 reviews- ★★★★★Liam Tandon· Dec 28, 2024
Useful MCP listing: DexPaprika is the kind of server we cite when onboarding engineers to host + tool permissions.
- ★★★★★Lucas Menon· Dec 16, 2024
Strong directory entry: DexPaprika surfaces stars and publisher context so we could sanity-check maintenance before adopting.
- ★★★★★Diego Abbas· Nov 19, 2024
According to our notes, DexPaprika benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
- ★★★★★Lucas Bansal· Nov 7, 2024
I recommend DexPaprika for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
- ★★★★★Isabella Flores· Oct 26, 2024
DexPaprika reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
- ★★★★★Kiara Yang· Oct 10, 2024
We wired DexPaprika into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
- ★★★★★Sakshi Patil· Sep 25, 2024
DexPaprika reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
- ★★★★★Rahul Santra· Sep 21, 2024
We evaluated DexPaprika against two servers with overlapping tools; this profile had the clearer scope statement.
- ★★★★★Mia Bhatia· Sep 17, 2024
Strong directory entry: DexPaprika surfaces stars and publisher context so we could sanity-check maintenance before adopting.
- ★★★★★Neel Torres· Sep 5, 2024
Useful MCP listing: DexPaprika is the kind of server we cite when onboarding engineers to host + tool permissions.
showing 1-10 of 31
