# DexPaprika (remote · mcp.dexpaprika.com)

Real-time DEX and on-chain data: liquidity pools, token prices, swaps, and trading volume.

- Trust score: 64/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `mcp.dexpaprika.com`: 64/100 (this document), [markdown](https://verifymcp.io/servers/com-dexpaprika-dexpaprika/mcp.md), [page](https://verifymcp.io/servers/com-dexpaprika-dexpaprika/mcp)
- remote · `mcp.dexpaprika.com`: 70/100, [markdown](https://verifymcp.io/servers/com-dexpaprika-dexpaprika/streamable-http.md), [page](https://verifymcp.io/servers/com-dexpaprika-dexpaprika/streamable-http)

## Channel facts

- Endpoint: `https://mcp.dexpaprika.com/sse`
- Transports: `sse`
- Auth: `none`
- Version: `2.3.2`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 40/100
  - Verified sse transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 55/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 7599 tokens (~447/item across 17 items; 17 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http com-dexpaprika-dexpaprika https://mcp.dexpaprika.com/sse
```

### Codex

```toml
[mcp_servers.com-dexpaprika-dexpaprika]
url = "https://mcp.dexpaprika.com/sse"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-dexpaprika-dexpaprika": {
      "type": "remote",
      "url": "https://mcp.dexpaprika.com/sse",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-dexpaprika-dexpaprika --url https://mcp.dexpaprika.com/sse --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-dexpaprika-dexpaprika:
    url: "https://mcp.dexpaprika.com/sse"
```

### Other

```json
{
  "mcpServers": {
    "com-dexpaprika-dexpaprika": {
      "type": "http",
      "url": "https://mcp.dexpaprika.com/sse"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 63, +3)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-31 (score 60, −1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 61, −1)

- [security] Tool “getNetworkPoolsFilter” rewrote its description, which is the text the model reads
- [security] Tool “getNetworks” rewrote its description, which is the text the model reads
- [security] Tool “getPoolDetails” rewrote its description, which is the text the model reads
- [security] Tool “getPoolOHLCV” rewrote its description, which is the text the model reads
- [security] Tool “getStats” rewrote its description, which is the text the model reads
- [security] Tool “getTokenDetails” rewrote its description, which is the text the model reads
- [security] Tool “getTokenMultiPrices” rewrote its description, which is the text the model reads
- [security] Tool “getTokenPools” rewrote its description, which is the text the model reads
- [security] Tool “getTopTokens” rewrote its description, which is the text the model reads
- [security] Tool “search” rewrote its description, which is the text the model reads
- [security] Tool “filterNetworkTokens” rewrote its description, which is the text the model reads
- [security] Tool “getCapabilities” rewrote its description, which is the text the model reads
- [security] Tool “getDexPools” rewrote its description, which is the text the model reads
- [security] Tool “getNetworkDexes” rewrote its description, which is the text the model reads
- [security] Tool “getPoolTransactions” rewrote its description, which is the text the model reads
- [security] Tool “getNetworkPools” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 361 → 447
- [functional] Server version: 2.0.0 → 2.3.2
- [cosmetic] “getNetworkPools” reworded the description of “sort_dir”
- [cosmetic] “getNetworkPoolsFilter” reworded the description of “order_by”
- [cosmetic] “getNetworkPoolsFilter” reworded the description of “sort”
- [cosmetic] “getNetworkPoolsFilter” reworded the description of “sort_by”
- [cosmetic] “getNetworkPoolsFilter” reworded the description of “sort_dir”
- [cosmetic] “getTokenPools” reworded the description of “sort”
- [cosmetic] “getTokenPools” reworded the description of “sort_by”
- [cosmetic] “getTokenPools” reworded the description of “sort_dir”
- [cosmetic] “getTopTokens” reworded the description of “order_by”
- [cosmetic] “getTopTokens” reworded the description of “sort”
- [cosmetic] “getTopTokens” reworded the description of “sort_by”
- [cosmetic] “getTopTokens” reworded the description of “sort_dir”
- [cosmetic] “filterNetworkTokens” reworded the description of “order_by”
- [cosmetic] “filterNetworkTokens” reworded the description of “sort”
- [cosmetic] “filterNetworkTokens” reworded the description of “sort_by”
- [cosmetic] “filterNetworkTokens” reworded the description of “sort_dir”
- [cosmetic] “getDexPools” reworded the description of “order_by”
- [cosmetic] “getDexPools” reworded the description of “sort”
- [cosmetic] “getDexPools” reworded the description of “sort_by”
- [cosmetic] “getDexPools” reworded the description of “sort_dir”
- [cosmetic] “getNetworkDexes” reworded the description of “order_by”
- [cosmetic] “getTokenPools” reworded the description of “order_by”
- [cosmetic] “getNetworkDexes” reworded the description of “sort”
- [cosmetic] “getNetworkDexes” reworded the description of “sort_by”
- [cosmetic] “getNetworkDexes” reworded the description of “sort_dir”
- [cosmetic] “getNetworkPools” reworded the description of “order_by”
- [cosmetic] “getNetworkPools” reworded the description of “sort”
- [cosmetic] “getNetworkPools” reworded the description of “sort_by”

### 2026-07-29 (score 62, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-28 (score 61, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 60, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 60)

First indexed and scored.

## MCP tools (17)

### `getNetworks` (~197 tokens)

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.

Input parameters:

- `rationale` (string, required): REQUIRED. 1-2 sentence rationale for this call (e.g. "User asked for X; calling Y to fetch Z"). Logged for MCP improvement, never shown to end users. No PII or secrets. See the server `instructions`…

### `getNetworkDexes` (~475 tokens)

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).

Input parameters:

- `limit` (number): OPTIONAL: Number of items per page (default: 10, max: 100)
- `network` (string, required): REQUIRED: Network ID from getNetworks (e.g., 'ethereum', 'solana')
- `order_by` (string): OPTIONAL: alias of sort_by; both are accepted. Not deprecated at the REST layer: api.dexpaprika.com itself takes order_by, so use this name when calling the REST API directly.
- `page` (number): OPTIONAL: Page number, 1-indexed. Server accepts page=0 (treated as page=1) for backward compatibility.
- `rationale` (string, required): REQUIRED. 1-2 sentence rationale for this call (e.g. "User asked for X; calling Y to fetch Z"). Logged for MCP improvement, never shown to end users. No PII or secrets. See the server `instructions`…
- `sort` (string): OPTIONAL: alias of sort_dir; both are accepted. Not deprecated at the REST layer: api.dexpaprika.com itself takes sort, so use this name when calling the REST API directly.
- `sort_by` (string): OPTIONAL: Sort field. Canonical parameter name; older tools used order_by. The REST API calls this parameter order_by.
- `sort_dir` (string): OPTIONAL: Sort direction (asc/desc). Canonical parameter name. Defaults to 'desc' if neither sort_dir nor sort is provided. The REST API calls this parameter sort.

### `getNetworkPools` (~527 tokens)

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 and keyless. 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).

Input parameters:

- `cursor` (string): OPTIONAL: Pagination cursor. Pass `next_cursor` from a previous response to fetch the next page (read `has_next_page` to know if more remain). Replaces the old page number.
- `limit` (number): OPTIONAL: Number of items per page (default: 10, max: 100)
- `network` (string, required): REQUIRED: Network ID from getNetworks (e.g., 'ethereum', 'solana')
- `order_by` (string): OPTIONAL: alias of sort_by; both are accepted. Not deprecated at the REST layer: api.dexpaprika.com itself takes order_by, so use this name when calling the REST API directly.
- `rationale` (string, required): REQUIRED. 1-2 sentence rationale for this call (e.g. "User asked for X; calling Y to fetch Z"). Logged for MCP improvement, never shown to end users. No PII or secrets. See the server `instructions`…
- `sort` (string): OPTIONAL: alias of sort_dir; both are accepted. Not deprecated at the REST layer: api.dexpaprika.com itself takes sort, so use this name when calling the REST API directly.
- `sort_by` (string): OPTIONAL: Sort field. Canonical parameter name. Defaults to 'volume_usd_24h'. Prefer the canonical *_24h names; short legacy names (volume_usd, transactions, last_price_change_usd_24h) are still acce…
- `sort_dir` (string): OPTIONAL: Sort direction (asc/desc). Canonical parameter name. Defaults to 'desc' if neither sort_dir nor sort is provided. The REST API calls this parameter sort.

### `getDexPools` (~546 tokens)

Get the pools belonging to one specific DEX on one network, e.g. all Uniswap v3 pools on ethereum, returned under 'pools' with page_info. Read-only and keyless. 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. Params: network (required slug); dex (required id, e.g. 'uniswap_v3'); limit (default 10, max 100); page (default 1); sort_by one of 'volume_usd','price_usd','transactions','last_price_change_usd_24h','created_at' (default 'volume_usd', alias order_by); sort_dir 'asc'/'desc' (default 'desc', alias sort).

Input parameters:

- `dex` (string, required): REQUIRED: DEX identifier from getNetworkDexes (e.g., 'uniswap_v3')
- `limit` (number): OPTIONAL: Number of items per page (default: 10, max: 100)
- `network` (string, required): REQUIRED: Network ID from getNetworks (e.g., 'ethereum', 'solana')
- `order_by` (string): OPTIONAL: alias of sort_by; both are accepted. Not deprecated at the REST layer: api.dexpaprika.com itself takes order_by, so use this name when calling the REST API directly.
- `page` (number): OPTIONAL: Page number, 1-indexed. Server accepts page=0 (treated as page=1) for backward compatibility.
- `rationale` (string, required): REQUIRED. 1-2 sentence rationale for this call (e.g. "User asked for X; calling Y to fetch Z"). Logged for MCP improvement, never shown to end users. No PII or secrets. See the server `instructions`…
- `sort` (string): OPTIONAL: alias of sort_dir; both are accepted. Not deprecated at the REST layer: api.dexpaprika.com itself takes sort, so use this name when calling the REST API directly.
- `sort_by` (string): OPTIONAL: Sort field. Canonical parameter name. Defaults to 'volume_usd' if neither sort_by nor order_by is provided. The REST API calls this parameter order_by.
- `sort_dir` (string): OPTIONAL: Sort direction (asc/desc). Canonical parameter name. Defaults to 'desc' if neither sort_dir nor sort is provided. The REST API calls this parameter sort.

### `getNetworkPoolsFilter` (~692 tokens)

Get pools on one network filtered by numeric thresholds, returned under 'results' with has_next_page and next_cursor. Read-only and keyless. 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'. Optional filters (AND-combined): volume_24h_min/max, volume_7d_min/max, liquidity_usd_min/max, txns_24h_min, created_after/created_before (Unix timestamps). 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).

Input parameters:

- `created_after` (number): OPTIONAL: Only pools created after this UNIX timestamp
- `created_before` (number): OPTIONAL: Only pools created before this UNIX timestamp
- `cursor` (string): OPTIONAL: Pagination cursor. Pass `next_cursor` from a previous response to fetch the next page. Replaces the old page number.
- `limit` (number): OPTIONAL: Items per page (default: 50, max: 100)
- `liquidity_usd_max` (number): OPTIONAL: Maximum pool liquidity in USD
- `liquidity_usd_min` (number): OPTIONAL: Minimum pool liquidity in USD
- `network` (string, required): REQUIRED: Network ID from getNetworks (e.g., 'ethereum', 'solana')
- `order_by` (string): OPTIONAL: alias of sort_by; both are accepted. Not deprecated at the REST layer: api.dexpaprika.com itself takes order_by, so use this name when calling the REST API directly.
- `rationale` (string, required): REQUIRED. 1-2 sentence rationale for this call (e.g. "User asked for X; calling Y to fetch Z"). Logged for MCP improvement, never shown to end users. No PII or secrets. See the server `instructions`…
- `sort` (string): OPTIONAL: alias of sort_dir; both are accepted. Not deprecated at the REST layer: api.dexpaprika.com itself takes sort, so use this name when calling the REST API directly.
- `sort_by` (string): OPTIONAL: Sort field. Canonical parameter name. Defaults to 'volume_usd_24h'. Prefer the canonical *_24h names; short legacy names (volume_24h, volume_7d, liquidity) are still accepted. The REST API…
- `sort_dir` (string): OPTIONAL: Sort direction (asc/desc). Canonical parameter name. Defaults to 'desc' if neither sort_dir nor sort is provided. The REST API calls this parameter sort.
- `txns_24h_min` (number): OPTIONAL: Minimum transactions in 24h
- `volume_24h_max` (number): OPTIONAL: Maximum 24h volume in USD
- `volume_24h_min` (number): OPTIONAL: Minimum 24h volume in USD
- `volume_7d_max` (number): OPTIONAL: Maximum 7d volume in USD
- `volume_7d_min` (number): OPTIONAL: Minimum 7d volume in USD

### `getPoolDetails` (~335 tokens)

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).

Input parameters:

- `inversed` (boolean): OPTIONAL: Whether to invert the price ratio (default: false)
- `network` (string, required): REQUIRED: Network ID from getNetworks (e.g., 'ethereum', 'solana')
- `pool_address` (string, required): REQUIRED: Pool address or identifier (e.g., '0x88e6a0c2ddd26feeb64f039a2c41296fcb3f5640')
- `rationale` (string, required): REQUIRED. 1-2 sentence rationale for this call (e.g. "User asked for X; calling Y to fetch Z"). Logged for MCP improvement, never shown to end users. No PII or secrets. See the server `instructions`…

### `getPoolOHLCV` (~440 tokens)

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 week', 'candles since Jan 1', or backtesting; for the single current price use getPoolDetails instead. Params: network (required); pool_address (required); start (required; Unix timestamp, RFC3339, or yyyy-mm-dd); end (optional, capped to 1 year after start); interval one of '1m','5m','10m','15m','30m','1h','6h','12h','24h' (default '24h'); limit (default 100, max 366 candles); inversed (optional bool, default false).

Input parameters:

- `end` (string): OPTIONAL: End time for historical data (max 1 year from start)
- `interval` (string): OPTIONAL: Interval granularity (default: '24h')
- `inversed` (boolean): OPTIONAL: Whether to invert the price ratio for alternative pair perspective (default: false)
- `limit` (number): OPTIONAL: Number of OHLCV data points to retrieve (default: 100, max: 366). One row per `interval`.
- `network` (string, required): REQUIRED: Network ID from getNetworks (e.g., 'ethereum', 'solana')
- `pool_address` (string, required): REQUIRED: Pool address or identifier
- `rationale` (string, required): REQUIRED. 1-2 sentence rationale for this call (e.g. "User asked for X; calling Y to fetch Z"). Logged for MCP improvement, never shown to end users. No PII or secrets. See the server `instructions`…
- `start` (string, required): REQUIRED: Start time. RFC3339 recommended (e.g. '2024-01-01T00:00:00Z'). Also accepts Unix epoch seconds and YYYY-MM-DD (treated as 00:00:00 UTC).

### `getPoolTransactions` (~425 tokens)

Get one pool's recent individual swap transactions, newest first, returned under 'transactions' (paginate with page, or a cursor). Read-only and keyless. 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 Unix seconds, inclusive, capped to the last 7 days); to (optional Unix seconds, exclusive, must be after from).

Input parameters:

- `cursor` (string): OPTIONAL: Transaction ID used for cursor-based pagination
- `from` (number): OPTIONAL: Start of time-range filter, Unix epoch SECONDS (inclusive). Window is capped to last 7 days. Note: getPoolOHLCV uses `start` (string) for the same concept — getPoolTransactions uses numeric…
- `limit` (number): OPTIONAL: Number of items per page (default: 10, max: 100)
- `network` (string, required): REQUIRED: Network ID from getNetworks (e.g., 'ethereum', 'solana')
- `page` (number): OPTIONAL: Page number, 1-indexed. Up to 100 pages. Server accepts page=0 (treated as page=1) for backward compatibility.
- `pool_address` (string, required): REQUIRED: Pool address or identifier
- `rationale` (string, required): REQUIRED. 1-2 sentence rationale for this call (e.g. "User asked for X; calling Y to fetch Z"). Logged for MCP improvement, never shown to end users. No PII or secrets. See the server `instructions`…
- `to` (number): OPTIONAL: Filter transactions up to this UNIX timestamp (exclusive). Must be after 'from'.

### `getTokenDetails` (~311 tokens)

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).

Input parameters:

- `network` (string, required): REQUIRED: Network ID from getNetworks (e.g., 'ethereum', 'solana')
- `rationale` (string, required): REQUIRED. 1-2 sentence rationale for this call (e.g. "User asked for X; calling Y to fetch Z"). Logged for MCP improvement, never shown to end users. No PII or secrets. See the server `instructions`…
- `token_address` (string, required): REQUIRED: Token contract address (e.g., 'JUPyiwrYJFskUPiHa7hkeR8VUtAeFoSYbKedZNsDvCN' for Jupiter on Solana)

### `getTokenPools` (~694 tokens)

Get the liquidity pools that contain a specific token on one network, returned under 'results' with has_next_page and next_cursor. Read-only and keyless. 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. 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.

Input parameters:

- `address` (string): REMOVED alias for paired_token_address. No longer supported by the API; supplying it returns an error.
- `cursor` (string): OPTIONAL: Pagination cursor. Pass `next_cursor` from a previous response to fetch the next page (read `has_next_page` to know if more remain). Replaces the old page number.
- `inversed` (boolean): REMOVED: the pair-perspective flip is no longer supported by the API; the pools/search replacement returns pool-perspective metrics only. Supplying true returns an error. For a single pool, getPoolDe…
- `limit` (number): OPTIONAL: Number of items per page (default: 10, max: 100)
- `network` (string, required): REQUIRED: Network ID from getNetworks (e.g., 'ethereum', 'solana')
- `order_by` (string): OPTIONAL: alias of sort_by; both are accepted. Not deprecated at the REST layer: api.dexpaprika.com itself takes order_by, so use this name when calling the REST API directly.
- `paired_token_address` (string): REMOVED: the second-token pair filter is no longer supported by the API. Supplying it returns an error. Filter client-side on each result's tokens[] instead.
- `rationale` (string, required): REQUIRED. 1-2 sentence rationale for this call (e.g. "User asked for X; calling Y to fetch Z"). Logged for MCP improvement, never shown to end users. No PII or secrets. See the server `instructions`…
- `reorder` (boolean): REMOVED alias for inversed. No longer supported by the API; supplying true returns an error.
- `sort` (string): OPTIONAL: alias of sort_dir; both are accepted. Not deprecated at the REST layer: api.dexpaprika.com itself takes sort, so use this name when calling the REST API directly.
- `sort_by` (string): OPTIONAL: Sort field. Canonical parameter name. Defaults to 'volume_usd_24h'. Prefer the canonical *_24h names; short legacy names (volume_usd, transactions, last_price_change_usd_24h) are still acce…
- `sort_dir` (string): OPTIONAL: Sort direction (asc/desc). Canonical parameter name. Defaults to 'desc' if neither sort_dir nor sort is provided. The REST API calls this parameter sort.
- `token_address` (string, required): REQUIRED: Token contract address

### `getTopTokens` (~520 tokens)

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 and keyless. 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).

Input parameters:

- `cursor` (string): OPTIONAL: Pagination cursor. Pass `next_cursor` from a previous response to fetch the next page. Replaces the old page number.
- `limit` (number): OPTIONAL: Items per page (default: 50, max: 100)
- `network` (string, required): REQUIRED: Network ID from getNetworks
- `order_by` (string): OPTIONAL: alias of sort_by; both are accepted. Not deprecated at the REST layer: api.dexpaprika.com itself takes order_by, so use this name when calling the REST API directly.
- `rationale` (string, required): REQUIRED. 1-2 sentence rationale for this call (e.g. "User asked for X; calling Y to fetch Z"). Logged for MCP improvement, never shown to end users. No PII or secrets. See the server `instructions`…
- `sort` (string): OPTIONAL: alias of sort_dir; both are accepted. Not deprecated at the REST layer: api.dexpaprika.com itself takes sort, so use this name when calling the REST API directly.
- `sort_by` (string): OPTIONAL: Ranking field. Defaults to 'volume_usd_24h'. Prefer the canonical names (volume_usd_24h, liquidity_usd, txns_24h, fdv_usd, price_change_percentage_24h); short legacy names are still accepte…
- `sort_dir` (string): OPTIONAL: Sort direction (asc/desc). Canonical parameter name. Defaults to 'desc' if neither sort_dir nor sort is provided. The REST API calls this parameter sort.

### `filterNetworkTokens` (~646 tokens)

Get tokens on one network matching numeric thresholds, returned under 'results' with has_next_page and next_cursor. Read-only and keyless. 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'. Optional filters (AND-combined): volume_24h_min/max, liquidity_usd_min/max, fdv_min/max, txns_24h_min, created_after/created_before (Unix timestamps). 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).

Input parameters:

- `created_after` (number): OPTIONAL: Only tokens created after this UNIX timestamp
- `created_before` (number): OPTIONAL: Only tokens created before this UNIX timestamp
- `cursor` (string): OPTIONAL: Pagination cursor. Pass `next_cursor` from a previous response to fetch the next page. Replaces the old page number.
- `fdv_max` (number): OPTIONAL: Maximum FDV in USD
- `fdv_min` (number): OPTIONAL: Minimum FDV in USD
- `limit` (number): OPTIONAL: Items per page (default: 50, max: 100)
- `liquidity_usd_max` (number): OPTIONAL: Maximum token liquidity in USD
- `liquidity_usd_min` (number): OPTIONAL: Minimum token liquidity in USD
- `network` (string, required): REQUIRED: Network ID from getNetworks
- `order_by` (string): OPTIONAL: alias of sort_by; both are accepted. Not deprecated at the REST layer: api.dexpaprika.com itself takes order_by, so use this name when calling the REST API directly.
- `rationale` (string, required): REQUIRED. 1-2 sentence rationale for this call (e.g. "User asked for X; calling Y to fetch Z"). Logged for MCP improvement, never shown to end users. No PII or secrets. See the server `instructions`…
- `sort` (string): OPTIONAL: alias of sort_dir; both are accepted. Not deprecated at the REST layer: api.dexpaprika.com itself takes sort, so use this name when calling the REST API directly.
- `sort_by` (string): OPTIONAL: Sort field. Defaults to 'volume_usd_24h'. Prefer the canonical names; short legacy names are still accepted. The REST API calls this parameter order_by.
- `sort_dir` (string): OPTIONAL: Sort direction (asc/desc). Canonical parameter name. Defaults to 'desc' if neither sort_dir nor sort is provided. The REST API calls this parameter sort.
- `txns_24h_min` (number): OPTIONAL: Minimum transactions in 24h
- `volume_24h_max` (number): OPTIONAL: Maximum 24h volume in USD
- `volume_24h_min` (number): OPTIONAL: Minimum 24h volume in USD

### `getTokenMultiPrices` (~237 tokens)

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).

Input parameters:

- `network` (string, required): REQUIRED: Network ID from getNetworks
- `rationale` (string, required): REQUIRED. 1-2 sentence rationale for this call (e.g. "User asked for X; calling Y to fetch Z"). Logged for MCP improvement, never shown to end users. No PII or secrets. See the server `instructions`…
- `tokens` (array, required): REQUIRED: Up to 10 token contract addresses on the same network.

### `search` (~309 tokens)

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).

Input parameters:

- `limit` (number): OPTIONAL: Cap items returned per category (tokens, pools, dexes). Upstream returns all matches by default; this client-side slice keeps payloads small for agents. Applies independently to each catego…
- `query` (string, required): REQUIRED: Search term (e.g., 'uniswap', 'bitcoin', 'ethereum', or a token address).
- `rationale` (string, required): REQUIRED. 1-2 sentence rationale for this call (e.g. "User asked for X; calling Y to fetch Z"). Logged for MCP improvement, never shown to end users. No PII or secrets. See the server `instructions`…

### `getStats` (~170 tokens)

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.

Input parameters:

- `rationale` (string, required): REQUIRED. 1-2 sentence rationale for this call (e.g. "User asked for X; calling Y to fetch Z"). Logged for MCP improvement, never shown to end users. No PII or secrets. See the server `instructions`…

### `getCapabilities` (~198 tokens)

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.

Input parameters:

- `rationale` (string, required): REQUIRED. 1-2 sentence rationale for this call (e.g. "User asked for X; calling Y to fetch Z"). Logged for MCP improvement, never shown to end users. No PII or secrets. See the server `instructions`…

### `submitFeedback` (~249 tokens)

Report a problem back to the DexPaprika team when a tool got you stuck, returned something unexpected, lacked data you needed, or behaved differently than documented. Use whenever you hit a dead end, a response shape surprised you, or coverage was missing; even partial feedback helps and every submission is read. Low friction: provide goal, expected, and observed instead of a rationale field.

Input parameters:

- `attempted_tools` (array): OPTIONAL: List of tool names you called, in order, before submitting this feedback.
- `blocked_at` (string): OPTIONAL: Tool name or step where you got stuck.
- `expected` (string): OPTIONAL: What you expected to happen. Capped at 500 characters; trim or summarize longer narratives.
- `goal` (string, required): REQUIRED: What you (or the user behind you) were trying to accomplish. 10-500 characters; longer goals are validation-rejected at the MCP layer.
- `observed` (string): OPTIONAL: What actually happened. Capped at 500 characters; trim or summarize longer narratives. Longer text triggers an MCP -32602 input validation error.
- `severity` (string): OPTIONAL: How badly this affected your task. Default 'minor'.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-dexpaprika-dexpaprika/mcp#diagnostics

## Score history

- 2026-08-03: 64
- 2026-08-02: 63
- 2026-08-01: 63
- 2026-07-31: 60
- 2026-07-30: 61
- 2026-07-29: 62
- 2026-07-28: 61
- 2026-07-27: 60
- 2026-07-26: 60

## Links

- Remote endpoint: https://mcp.dexpaprika.com/sse
- Repository: https://github.com/coinpaprika/dexpaprika-mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-dexpaprika-dexpaprika/mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-dexpaprika-dexpaprika/mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/com-dexpaprika-dexpaprika/mcp