Server facts
dexpaprika-mcp
Project
- Author
- coinpaprika
- Repository
- github.com/coinpaprika/dexpaprika-mcp
- Website
- dexpaprika.com
- License
- MIT
- Category
- Blockchain & Web3
Tech
- Runtime / language
- node
- Transports
- stdio
- Remote available
- No
- Authentication
- Not specified
Activity
- GitHub stars
- 95
- Last commit
- Data as of
Tags
- claude integration
- crypto analysis tool
- crypto api
- cryptocurrency
- defi
- dex
- dexpaprika
- mcp
- model context protocol
Overview
DEX research with DexPaprika starts by locating an asset, exchange, or pool across supported chains. The search tool accepts names, symbols, and addresses; its results identify the network needed for more focused queries. getNetworks supplies chain identifiers and activity figures, while getCapabilities explains workflow sequences and network aliases rather than returning market data. Developers can explore exchanges on a chain, rank pools by trading volume, or screen pools against liquidity, transaction, volume, and creation-time criteria. Token discovery also includes rankings and threshold filters for measures such as fully diluted valuation and price changes.
Once a pool is selected, getPoolDetails provides its current price, liquidity, and trading metrics. getPoolOHLCV retrieves historical candles, while getPoolTransactions supplies recent individual swaps. Token lookups combine metadata with price and volume statistics, and getTokenPools identifies liquidity venues for a chosen asset. getTokenMultiPrices batches USD price requests within a single network and reports tokens it could not price. These read-only market tools work without an API key; getKeyStatus separately reports key use and the API-recognized plan when investigating access or rate-limit issues.
dexpaprika-mcp setup notes
- dexpaprika-mcp records stdio only; confirm a network transport upstream before planning remote access.