coinpaprika/dexpaprika-mcp
🎖️ 📇 ☁️ 🍎 🪟 🐧 - Coinpaprika's DexPaprika MCP server exposes high-performance [DexPaprika API](https://docs.dexpaprika.com) covering 20+ chains and 5M+ tokens with real time pricing, liquidity pool data & historical OHLCV data, providing AI agents standardized access to comprehensive market data through Model Context Protocol.
Category: Other
Install
npx -y dexpaprika-mcpCapabilities
- tools
Server instructions
# DexPaprika MCP — agent usage notes ## `rationale` field (required on every read tool) Every read tool (`getNetworks`, `getPoolDetails`, etc.) requires a `rationale` string of 20-500 chars. Format: 1-2 sentences referencing (a) what triggered the call and (b) downstream use. Do not include user PII or secrets. Rationales are accepted to satisfy the schema and never persisted in the self-host build. Examples: - "User asked for SOL price; calling getTokenDetails to fetch current USD value." - "Building a portfolio dashboard; need top pools for WETH on ethereum to estimate liquidity." - "Backtesting USDC/WETH spread; fetching 24h OHLCV at 1h interval." ## Tool discovery Start with `getNetworks` (discover supported chains) or `getCapabilities` (agent-onboarding doc: network synonyms, workflow patterns, common pitfalls). Both are free and have no parameters beyond rationale. ## Parameter naming Sort parameters accept both legacy and canonical names — pick whichever is clearer; the server normalizes both. Canonical names (preferred going forward): - `sort_dir` (legacy: `sort`) — sort direction, "asc" or "desc". - `sort_by` (legacy: `order_by`) — sort field, tool-specific enum. `getTokenPools` no longer accepts `inversed`/`reorder` or `paired_token_address`/`address`: the endpoint it proxied was removed and its replacement (/networks/{network}/pools/search with token_address) has no equivalent for either. Supplying them returns a structured error with a client-side workaround. The token filter is network-scoped only; the cross-network /pools/search ignores token_address. Pagination is 1-indexed; the server accepts `page=0` as a backward-compat alias for `page=1`. ## Time formats - `getPoolOHLCV.start` / `.end`: RFC3339 recommended (`2024-01-01T00:00:00Z`). Also accepts Unix epoch seconds and `YYYY-MM-DD` (treated as 00:00:00 UTC). - `getPoolTransactions.from` / `.to`: Unix epoch SECONDS only. Window capped to last 7 days. ## Output shape All tools return both `content[0].text` (JSON string, for older clients) and `structuredContent` (validated against the tool's `outputSchema`, 2025-06-18+). Prefer `structuredContent` to avoid the parse round-trip. Array-returning tools wrap the array under a named key in structuredContent — `getNetworks` → `{ networks: [...] }`, `getPoolOHLCV` → `{ ohlcv: [...] }`, `getTokenMultiPrices` → `{ prices: [...] }`.