Skip to main content
Glama
DexPaprika (CoinPaprika)

DexPaprika (CoinPaprika)

Official

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

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.

getDexPools kept its name and its dex argument, but the endpoint underneath changed on 2026-08-05: /networks/{network}/dexes/{dex}/pools was removed and the tool now proxies /networks/{network}/pools/search with a dex_name filter. Rows arrive under results with has_next_page + next_cursor, not under pools with page_info, and the 24h volume field is volume_usd_24h, not volume_usd. page is superseded by cursor: page 2 and above return a structured error rather than silently repeating page 1.

Pagination is 1-indexed; the server accepts page=0 as a backward-compat alias for page=1.

Technical indicators

getPoolIndicator returns RSI, EMA, MACD, Bollinger Bands or VWAP for a pool, computed server-side from its OHLCV candles, so there is no need to fetch candles and compute them. Pick one with indicator and always pass interval. Send only the parameters of that indicator (period; fast_period/slow_period/signal_period for macd; std_dev for bbands): any other is refused with 400. History depth and interval follow the same plan limits as getPoolOHLCV. getTokenIndicator computes the same on a token's USD candles across all its pools and needs a Dev, Pro or Enterprise key.

Time formats

  • getPoolOHLCV.start / .end: a relative offset from now is simplest (-24h = last 24 hours, -7d, -90m; units s, m, h, d) and needs no knowledge of today's date. Also accepts RFC3339 (2024-01-01T00:00:00Z), Unix epoch seconds and YYYY-MM-DD (treated as 00:00:00 UTC).

  • getPoolOHLCV without a key serves the last 24 hours at 1h and longer; a free key (DEXPAPRIKA_API_KEY) opens 7 days at 10m and longer. Limits by plan: https://docs.dexpaprika.com/knowledge-base/rate-limits#ohlcv-limits-by-plan

  • getTokenOHLCV, getPoolIndicator and getTokenIndicator take start / end in the same formats as getPoolOHLCV. There is no keyless or free window: the endpoint needs a Dev or Pro plan, and Dev history stops 30 days back. On a 403, fall back to getPoolOHLCV on the token's main pool (found with getTokenPools).

  • getPoolTransactions.from / .to, and created_after / created_before on getNetworkPoolsFilter and filterNetworkTokens: the same shapes as start, so a relative offset (-1h, -24h, -7d), Unix epoch seconds, RFC3339 or YYYY-MM-DD. Transactions: window capped to last 7 days.

  • getPoolTransactions and getTokenOHLCV need a Dev, Pro or Enterprise key with DEXPAPRIKA_API_BASE_URL=https://api-pro.dexpaprika.com. Keyless and free keys get DP403_PLAN_REQUIRED; tell the user rather than retrying.

  • getTokenIndicator needs the same Dev, Pro or Enterprise key and base URL. Without it, use getPoolIndicator on the token's main pool (found with getTokenPools).

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 gives { networks: [...] }, getPoolOHLCV and getTokenOHLCV give { ohlcv: [...] }, getTokenMultiPrices gives { prices: [...] }.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
getKeyStatusA

Report whether this server is sending an API key and which plan the API sees. Use when calls are being rate limited or refused, or when the user asks whether their DexPaprika key is working. Takes no arguments and reads no market data.

getNetworksA

List every blockchain network DexPaprika indexes, each row carrying its network id (slug), 24h volume, transaction count, and pool count. Read-only and keyless. Start here (or getCapabilities) to get the exact network slug that nearly every other tool requires as its 'network' argument. Use for 'which chains do you support?', 'is Base/Solana/Arbitrum covered?', or 'what is the slug for Polygon?'. Returns the full array with no pagination or sorting; takes no parameters beyond a short rationale. For platform-wide totals rather than a per-network list use getStats.

getCapabilitiesA

Get the static agent onboarding guide for this server: supported workflows, network name synonyms (mapping words like 'eth' to the canonical slug 'ethereum'), recommended call sequences, and common pitfalls. Read-only and keyless. Read it once at the start of a session before your first query, or when asked 'how do I use this API?', 'what order should I call things in?', or 'which slug maps to eth?'. This returns onboarding docs, not live market data; for the actual list of network slugs use getNetworks, and for coverage totals use getStats. Takes no parameters beyond a short rationale.

getNetworkDexesA

List the DEXes (exchanges) operating on one network, such as Uniswap on ethereum or Raydium on solana, returned under 'dexes' with page_info (page, total_pages). Read-only and keyless. Use for 'which DEXes are on Base?', 'does Solana have Orca?', or to get a dex id to feed into getDexPools. Scope is a single network; call getNetworks first for the slug. Params: network (required slug); limit (default 10, max 100); page (default 1, 1-indexed); sort_by (only 'pool'; legacy alias order_by); sort_dir 'asc' or 'desc' (default 'desc'; legacy alias sort).

getNetworkPoolsA

Get the top liquidity pools across a whole network, ranked by 24h volume by default, returned under 'results' with has_next_page and next_cursor. Read-only. The first page works without an API key; paging with cursor needs a key (a free key pages without limit). This is the primary chain-wide pool discovery tool. Use for 'biggest pools on ethereum', 'top trading pairs on Base', or 'most active pools on Solana'. Narrow to one exchange with getDexPools, or apply numeric/time filters with getNetworkPoolsFilter. Params: network (required slug); limit (default 10, max 100); cursor (pass previous next_cursor to page); sort_by (default 'volume_usd_24h', canonical *_24h fields, alias order_by); sort_dir 'asc' or 'desc' (default 'desc', alias sort).

getDexPoolsA

Get the pools belonging to one specific DEX on one network, e.g. all Uniswap v3 pools on ethereum. Proxies /networks/{network}/pools/search with a dex_name filter (the old /networks/{network}/dexes/{dex}/pools endpoint was removed): rows come back under 'results' with cursor pagination (has_next_page + next_cursor), and the 24h volume field is volume_usd_24h. Read-only. The first page works without an API key; paging with cursor needs a key (a free key pages without limit). Narrower than getNetworkPools (a single exchange, not the whole chain). Use for 'show me Raydium pools', 'top pairs on PancakeSwap', or 'liquidity on Orca'. Get the dex id from getNetworkDexes or search first, and pass that response's dex_id field ('uniswap_v3'), matched case-insensitively. Do not pass its dex_name field ('Uniswap V3'): a human display name returns HTTP 200 with an empty results[] rather than an error, so an empty answer here usually means the wrong form of the name was sent. Params: network (required slug); dex (required id, e.g. 'uniswap_v3'; the REST API calls this query parameter dex_name); limit (default 10, max 100); cursor (pass previous next_cursor to page); sort_by (default 'volume_usd_24h', canonical *_24h fields, short legacy names still accepted, alias order_by); sort_dir 'asc'/'desc' (default 'desc', alias sort). The old page number is gone: page 2 and above return an error pointing at cursor.

getNetworkPoolsFilterA

Get pools on one network filtered by numeric thresholds, returned under 'results' with has_next_page and next_cursor. Read-only. The first page works without an API key; paging with cursor needs a key (a free key pages without limit). Choose this over getNetworkPools when the user gives numeric constraints or a time window. Use for 'pools over $1M liquidity on Base', 'pools created in the last 24h', or 'high-volume low-liquidity pairs'. Without a Dev plan or higher (a Dev, Pro or Enterprise key on api-pro.dexpaprika.com), pools created in the last hour are left out, so a created_after window shorter than an hour comes back empty. Optional filters (AND-combined): volume_24h_min/max, volume_7d_min/max, liquidity_usd_min/max, txns_24h_min, created_after/created_before (a relative offset such as '-24h', Unix seconds, RFC3339 or YYYY-MM-DD). Also network (required); limit (default 50, max 100); cursor to page; sort_by (default 'volume_usd_24h', alias order_by); sort_dir asc/desc (default 'desc', alias sort).

getPoolDetailsA

Get the full current snapshot for one pool by address: its two tokens, current price, liquidity/TVL, 24h volume, and transaction counts, returned as a single pool object (not a list). Read-only and keyless. Use after search or getNetworkPools surfaces a pool, or for 'price/TVL of this pool?' or 'details for pool 0x...'. Returns live values only; for historical candles use getPoolOHLCV, and for the raw swap feed use getPoolTransactions. Params: network (required slug); pool_address (required, e.g. '0x88e6a0c2ddd26feeb64f039a2c41296fcb3f5640'); inversed (optional bool, default false, flips the token price ratio to token1/token0).

getPoolOHLCVA

Get historical OHLCV candles (open, high, low, close, volume) for one pool over a time range, returned as a time-series array. Read-only and keyless. Use for 'price history of this pair', 'hourly chart for the last day', or backtesting; for the single current price use getPoolDetails instead. Params: network (required); pool_address (required); start (required; easiest as a relative offset from now such as '-24h', so you need not know today's date; also Unix seconds, RFC3339 or yyyy-mm-dd); end (optional); interval one of '1m','5m','10m','15m','30m','1h','6h','12h','24h' (default '24h'); limit (default 100, max 1000 candles); inversed (optional bool, default false). History depth and interval depend on the plan: without a key, the last 24 hours at '1h' and longer; a free key (DEXPAPRIKA_API_KEY) opens 7 days at '10m' and longer. Asking for more returns 403 with a message naming the plan that allows it.

getPoolIndicatorA

Get a technical indicator (RSI, EMA, MACD, Bollinger Bands or VWAP) for one pool, computed server-side from the pool's completed OHLCV candles and returned as a time series. Read-only. Use for 'is this pool overbought?', 'RSI of this pair', 'MACD cross on the last candle', or as a ready-made signal input for a trading or screening agent, instead of fetching getPoolOHLCV and computing the indicator yourself. The indicator follows the pool's price as getPoolOHLCV reports it, with no inversed parameter. History depth and interval follow the same plan limits as getPoolOHLCV; asking for more returns 403 with a message naming the plan that allows it. Values come oldest first, one per completed candle: rsi, ema and vwap return value; macd returns macd, signal and histogram; bbands returns upper, middle and lower. RSI over 70 is commonly read as overbought and under 30 as oversold; a MACD histogram that changes sign means MACD crossed its signal line. RSI, EMA and MACD are smoothed, so start at least ten periods before the first value you rely on. Params: network (required); pool_address (required); indicator (required): 'rsi', 'ema', 'macd', 'bbands' or 'vwap'; interval (pass it every time: '1m','5m','10m','15m','30m','1h','6h','12h','24h' or '1d'); start (optional; a relative offset such as '-24h' or '-7d', Unix seconds, RFC3339 or yyyy-mm-dd; without it you get the last limit values); end (optional, exclusive); limit (default 100, max 1000); cursor (next_cursor of the previous page, not with start); period for rsi (default 14), ema (20), bbands (20) and vwap (14); fast_period (12), slow_period (26) and signal_period (9) for macd only; std_dev (2) for bbands only. A parameter that belongs to another indicator is refused.

getPoolTransactionsA

Get one pool's recent individual swap transactions, newest first, returned under 'transactions' (paginate with page, or a cursor). Read-only. Requires a Dev, Pro or Enterprise key since 30 September 2026: set DEXPAPRIKA_API_KEY to it and DEXPAPRIKA_API_BASE_URL to https://api-pro.dexpaprika.com. Keyless and free keys get 403 (DP403_PLAN_REQUIRED); getPoolDetails still gives the pool's 24h transaction counts and volume. These are per-trade records, not aggregated candles (use getPoolOHLCV) or a summary snapshot (use getPoolDetails). Use for 'recent trades on this pool', 'who swapped in the last hour', or 'raw transaction feed'. Params: network (required); pool_address (required); limit (default 10, max 100); page (default 1, up to 100 pages) or cursor (a transaction id); from (optional, inclusive: a relative offset such as '-1h', Unix seconds, RFC3339 or YYYY-MM-DD; capped to the last 7 days); to (optional, exclusive, same formats, must be after from).

getTokenDetailsA

Get one token's data and metadata by contract address on one network: multi-timeframe price and volume metrics, plus name, website, Twitter, and Telegram links, returned as a single token object. Read-only and keyless. Use for 'price and volume for 0x... on Base' or 'tell me about this token'. If you only have a symbol like WETH, call search first to resolve the address and network. For many tokens' prices at once use getTokenMultiPrices; for the pools holding this token use getTokenPools. Params: network (required slug); token_address (required contract address, e.g. 'JUPyiwrYJFskUPiHa7hkeR8VUtAeFoSYbKedZNsDvCN' on solana).

getTokenPoolsA

Get the liquidity pools that contain a specific token on one network, returned under 'results' with has_next_page and next_cursor. Read-only. The first page works without an API key; paging with cursor needs a key (a free key pages without limit). Use for 'which pools hold WETH on ethereum?' or 'liquidity venues for 0x...'. Network-scoped, so run search first if unsure of the network; unknown addresses return empty results, not an error. Without a Dev plan or higher (a Dev, Pro or Enterprise key on api-pro.dexpaprika.com), pools created in the last hour are left out, so a token launched in the last hour shows no pools yet. For the token's own price use getTokenDetails. Params: network (required); token_address (required); limit (default 10, max 100); cursor to page; sort_by (default 'volume_usd_24h', alias order_by); sort_dir asc/desc (default 'desc', alias sort). Extra params such as inversed or paired_token_address are unsupported and error.

getTokenOHLCVA

Get historical USD OHLCV candles for one token over a time range, returned as a time-series array. The price and volume are computed across every pool the token trades in on the network (a volume-weighted price, and volume summed across those pools), not a single pair. Requires a Dev or Pro plan: set DEXPAPRIKA_API_KEY to that key and DEXPAPRIKA_API_BASE_URL to https://api-pro.dexpaprika.com. On a keyless or free key this returns 403 (DP403_PLAN_REQUIRED), since there is no keyless or free window at all. On that 403, fall back to getPoolOHLCV on the token's main pool, found with getTokenPools sorted by volume. Use for 'price history of this token' or 'USD chart for this token'; for a single pair's candles use getPoolOHLCV, and for the current price use getTokenDetails. Params: network (required); token_address (required); start (required; easiest as a relative offset from now such as '-24h', so you need not know today's date; also Unix seconds, RFC3339 or yyyy-mm-dd); end (optional, same formats); interval one of '1m','5m','10m','15m','30m','1h','6h','12h','24h' (default '24h'); limit (default 10, max 1000 candles). Dev plan history is limited to the last 30 days. There is no inversed parameter on this endpoint.

getTokenIndicatorA

Get a technical indicator (RSI, EMA, MACD, Bollinger Bands or VWAP) for one token, computed server-side from its USD candles across every pool it trades in on the network (the series getTokenOHLCV returns), as a time series. Requires a Dev, Pro or Enterprise plan: set DEXPAPRIKA_API_KEY to that key and DEXPAPRIKA_API_BASE_URL to https://api-pro.dexpaprika.com. On a keyless or free key this returns 403 (DP403_PLAN_REQUIRED); then use getPoolIndicator on the token's main pool, found with getTokenPools sorted by volume. Use for 'RSI of this token' or a token-level signal for an agent; for one pair use getPoolIndicator. Values come oldest first, one per completed candle: rsi, ema and vwap return value; macd returns macd, signal and histogram; bbands returns upper, middle and lower. RSI over 70 is commonly read as overbought and under 30 as oversold; a MACD histogram that changes sign means MACD crossed its signal line. RSI, EMA and MACD are smoothed, so start at least ten periods before the first value you rely on. Params: network (required); token_address (required); indicator (required): 'rsi', 'ema', 'macd', 'bbands' or 'vwap'; interval (pass it every time: '1m','5m','10m','15m','30m','1h','6h','12h','24h' or '1d'); start (optional; a relative offset such as '-24h' or '-7d', Unix seconds, RFC3339 or yyyy-mm-dd; without it you get the last limit values); end (optional, exclusive); limit (default 100, max 1000); cursor (next_cursor of the previous page, not with start); period for rsi (default 14), ema (20), bbands (20) and vwap (14); fast_period (12), slow_period (26) and signal_period (9) for macd only; std_dev (2) for bbands only. A parameter that belongs to another indicator is refused.

getTokenMultiPricesA

Get current USD prices for up to 10 tokens on the same network in one batched call, returned as a prices array plus a missing_tokens list. Read-only and keyless. Tokens that cannot be priced come back in missing_tokens rather than being dropped, so check that list for partial failures. Use for 'prices for these tokens', 'compare the price of X, Y and Z', or building a portfolio/dashboard snapshot. For one token with full metadata and multi-timeframe stats use getTokenDetails. Params: network (required slug, all tokens must share it); tokens (required array of 1 to 10 contract addresses).

filterNetworkTokensA

Get tokens on one network matching numeric thresholds, returned under 'results' with has_next_page and next_cursor. Read-only. The first page works without an API key; paging with cursor needs a key (a free key pages without limit). Choose this over getTopTokens when the user gives numeric constraints or a time window. Use for 'tokens with FDV over $10M on Base', 'newly created tokens today', or 'low-liquidity high-volume tokens'. Without a Dev plan or higher (a Dev, Pro or Enterprise key on api-pro.dexpaprika.com), tokens created in the last hour are left out, so a created_after window shorter than an hour comes back empty. Optional filters (AND-combined): volume_24h_min/max, liquidity_usd_min/max, fdv_min/max, txns_24h_min, price_change_percentage_24h_min/max, created_after/created_before (a relative offset such as '-24h', Unix seconds, RFC3339 or YYYY-MM-DD). Also network (required); limit (default 50, max 100); cursor to page; sort_by (default 'volume_usd_24h', alias order_by); sort_dir asc/desc (default 'desc', alias sort).

getTopTokensA

Get the top tokens on one network ranked by volume, liquidity, transactions, FDV, or 24h price change, returned under 'results' with has_next_page and next_cursor. Read-only. The first page works without an API key; paging with cursor needs a key (a free key pages without limit). Use for 'top gainers on Solana', 'highest-volume tokens on Base', or 'biggest tokens by FDV on ethereum'. For arbitrary numeric filters or a time window use filterNetworkTokens instead. Params: network (required slug); limit (default 50, max 100); cursor (pass previous next_cursor to page); sort_by (default 'volume_usd_24h', alias order_by), noting that ranking by raw price is unsupported and silently falls back to volume; sort_dir asc/desc (default 'desc', alias sort).

searchA

Search across ALL networks at once for tokens, pools, and DEXes by name, symbol, or address, returning three arrays: 'tokens', 'pools', and 'dexes'. Read-only and keyless. This is the cross-chain entry point when you do not yet know which network something lives on; once you have a network slug from the results, switch to the network-scoped tools. Use for 'find PEPE', 'what is the address for USDC', or 'which chain is this token on?'. No matches returns empty arrays, not an error. Params: query (required; a name, symbol, or contract address, e.g. 'uniswap', 'bitcoin', or '0x...'); limit (optional, caps results per category, applied client-side).

getStatsA

Get platform-wide totals for DexPaprika: the number of networks, DEXes, pools, and tokens indexed, returned as a single summary object. Read-only and keyless. Use for 'how much data do you cover?', 'how many chains or pools total?', or a one-line coverage summary. These are ecosystem-wide counts, not per-network figures; use getNetworks for the per-chain breakdown, or getCapabilities for onboarding docs. Takes no parameters beyond a short rationale.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.4/5.0

Scored across 20 tools

Disambiguation4/5

Most tools have crisply distinct resource+action targets, and the descriptions explicitly cross-reference siblings ('choose this over getNetworkPools when...', 'for one token use getTokenDetails'). The one soft spot is the cluster of chain-wide listing tools (getNetworkPools, getNetworkPoolsFilter, getTopTokens, filterNetworkTokens, getDexPools), which an agent could plausibly confuse despite the guidance text. Overall the boundaries are well drawn, just requiring careful reading.

Naming Consistency4/5

Nearly all tools follow a consistent camelCase get_<resource><aspect> pattern (getTokenDetails, getPoolOHLCV, getNetworkPoolsFilter), with resource prefixes (token/pool/network/dex) aiding scanability. Minor deviations are the bare 'search' and the verb-first 'filterNetworkTokens', which break the 'get' convention slightly. Still highly predictable and readable.

Tool Count4/5

20 tools is at the upper edge, but each occupies a distinct cell in the token × pool × network × meta matrix (details, OHLCV, indicator, transactions, listings, meta). The token/pool OHLCV+indicator pairs are symmetric rather than redundant. It stays justifiable, though a few listing variants could arguably be folded into parameterized tools.

Completeness4/5

The surface covers discovery (search, getNetworks, getNetworkDexes), market data (details, multi-prices, OHLCV, indicators), transactions, and meta/onboarding (capabilities, stats, key status), with documented plan-gating and fallbacks. Gaps are minor: no single-DEX detail object, no pool/token liquidity or TVL history, and no aggregate DEX-level volume stats. Core agent workflows have no dead ends.

Maintenance

ActivityActive
ResponsivenessLimited data