Sato Hub
MCP

DexPaprika MCP Server

Zero-config MCP access to DexPaprika's DEX data — tokens, liquidity pools, and OHLCV across 33 chains.

  • Sato Score86
  • ChainsMultichain
ActiveSelf-ReportedActive · 2d ago

DexPaprika MCP Server is an open-source MCP server by CoinPaprika, with last code activity on 2026-10-13 (Active). Latest release on 2026-10-13. Sato Score 86/100 (how open, active and verifiable it is, not a safety grade), as of 2026-10-15. How the score works →

See how to install DexPaprika MCP Server →

Last commit Oct 13, 2026 · Last release Oct 13, 2026 (v2.8.0) · ★ 53

Listed from dexpaprika.com on 2026-07-12. Install: not attempted. Evidence →

Next step

Watch DexPaprika MCP Server

One email if what we observe changes — its repo goes quiet or disappears, or the listing is retired. Nothing else.

Check it from your agent

Add Sato Hub’s MCP server (no key), then ask:

https://satohub.ai/api/mcp
Run Sato Hub Preflight on coinpaprika/dexpaprika-mcp before I use it.
Full setup: Claude Code, Cursor, others →

Your project?

Prove you control the domain and correct this page — description, links, tags, chains. A claim proves control, not verification: it never changes the Sato Score.

Claim this listing →

Overview

DexPaprika (CoinPaprika's DEX data arm) publishes this MCP server so agents can query real-time token, liquidity-pool, and DEX data plus OHLCV history and cross-DEX comparisons across 33 blockchains, via 14 tools. It runs via npm/npx with no API key on a free 10,000-requests/day tier, or through a hosted endpoint at mcp.dexpaprika.com supporting Streamable HTTP, SSE, and JSON-RPC. Builders plug it in as a market-data layer for on-chain trading or research agents.

Sato Score

86/100· High

How open, active & verifiable — not a safety or returns grade.

Maintenance & liveness
35/35
Code transparency
18/20
Interface verifiability
10/10
Docs & demo
6/10
Listing transparency & provenance
12/15
Independent verification
5/10

Live endpoint probed — we called the hosted MCP endpoint and it answered with its real tool inventory (proves the interface works, not runtime safety).

Sato Check

v2.8.0 · as of 2026-10-14
Does it take your key?
No key read found
Does your key leave?
Not yet run · earlier run 2026-10-05: not observed
Can it move funds on its own?
None found
Full profile, evidence and limits →

A profile describes what we read and ran, with dates. It is not a safety rating, an audit or an endorsement, and "not found" is not "not there".

Evidence — listed vs checked · what the words mean

Listed from dexpaprika.com on 2026-07-12. Install: not attempted.

ClaimValueEvidenceSourceChecked
Chains supportedMultichainself-reporteddocs.dexpaprika.comas of 2026-10-15
Verification statusSelf-Reported — not independently reviewedself-reporteddexpaprika.comas of 2026-10-15
Recent activitylast release 2026-10-13 · last commit 2026-10-13observedgithub.com/coinpaprika/dexpaprika-mcp2026-10-15
Install worksdocumented by the project, not run by Sato Hubnot attempted by Sato Hubself-reportedgithub.com/coinpaprika/dexpaprika-mcpas of 2026-07-14
MCP endpoint answersanswered — 20 tools listedobservedmcp.dexpaprika.com2026-10-15
Daily check record90 of 90 daily checks since 2026-07-17 succeededa success rate of our checks, not uptime; the source is this listing's own historyobserved—2026-10-14
Takes your keyno private-key read found in what we readtracedsatohub.ai2026-10-14
Key leaves the machinenot yet run with planted test keysthe sandbox lane has not run on this versionobservedsatohub.ainot dated
Moves funds on its ownno action that signs or sends funds foundtracedsatohub.ai2026-10-14
Deploys asnpm install -g / npx, or one-line Smithery installconfidence 0.85self-reportedgithub.com/coinpaprika/dexpaprika-mcpas of 2026-07-14
Works withClaude Desktopconfidence 0.75self-reportedgithub.com/coinpaprika/dexpaprika-mcpas of 2026-07-14
Sato Score86/100 (High)how open, active and verifiable — not a safety or quality gradecomputedsatohub.ai2026-10-15

Self-reported rows are the project’s own words, dated when we recorded them — not a check. Only reproduced and reviewed rows carry a mark. None of these rows is a safety or quality rating.

Install — as documented by the project, not run by us

Runtime: node

npm install -g dexpaprika-mcp
dexpaprika-mcp

MCP invocation: {"mcpServers":{"dexpaprika":{"command":"npx","args":["dexpaprika-mcp@latest"]}}}

Read from the project’s own docs as of 2026-07-14. What a deploy spec is →

Tool inventory — 20 tools, probed live 2026-10-15

  • getNetworks — 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
  • getNetworkDexes — 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
  • getNetworkPools — 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
  • getDexPools — Get the pools belonging to one specific DEX on one network, e.g. all Uniswap v3 pools on ethereum, returned under 'results' with has_next_page and next_cursor. Read-only and keyless. Proxies /networks
  • getNetworkPoolsFilter — 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 numeri
  • getPoolDetails — 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 ke
  • getPoolOHLCV — 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 char
  • getPoolIndicator — 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 and keyless. Use
  • getPoolTransactions — Get one pool's recent individual swap transactions, newest first, returned under 'transactions' (paginate with page, or a cursor). Read-only. Runs on the caller's own Dev, Pro or Enterprise API key, s
  • getTokenDetails — 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
  • getTokenPools — 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?' o
  • getTopTokens — 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
  • filterNetworkTokens — 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 con
  • getTokenMultiPrices — 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
  • getTokenOHLCV — 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-weig
  • getTokenIndicator — Get a technical indicator (RSI, EMA, MACD, Bollinger Bands or VWAP) for one token, computed server-side from the token's USD candles across every pool it trades in on the network (the same series as g
  • search — 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 entr
  • getStats — 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?', 'h
  • getCapabilities — 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 pi
  • submitFeedback — 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,
Answers a handshake
yes · 2026-10-15
Answers a call
not asked — no tool is named as a read (list_/get_/search_)

Live probe verifies the interface responds — not what the tools do, their safety, or their output quality. The call is one read-only tool named by this server's own list (list_/get_/search_, no mutating verb anywhere in the name, no required arguments and none that look like a key, an address or an amount), asked once a day with no arguments. Not asked is not a failure.

Observed record — 91 daily checks since 2026-07-17

100%of 91 checks since 2026-07-17 succeeded
Currently responding for 91 days
Succeeded
91
Failed
0
Their error
0
Unattributed
0

This is the share of our daily checks that succeeded — not an availability guarantee. A check can fail because the host was down, because our runner timed out, or because the network in between dropped it, and only the first of those is a fact about this project. Failures are split by what we can attribute; anything we cannot attribute is counted, not hidden. 46 of these checks predate 2026-09-01, when the probe counted a bot-block (HTTP 403) as a failure and recorded no reason for any failure. Every one of them passed, so the rate covers them too.

Last 30 days — to 2026-10-15, one point per UTC day

Share of OUR checks that succeeded
100%
7-day rolling; unattributable days are gaps · 30/30 days
Tools listed
20
from the server's own tools/list · 29/30 days
Sato Score
86
as snapshotted that day · 29/30 days

A gap is a day we have no attributable observation — never a zero. Thirty points is the whole shape the free layer carries; the daily rows behind it stay in the snapshot series.

Tool inventory history — 20 now, peak 20, since 2026-07-19

  • 2026-10-14 18 → 20 +2 (getPoolIndicator, getTokenIndicator)
  • 2026-09-29 17 → 18 +1 (getTokenOHLCV)
  • 2026-09-23 0 → 17 +17 (filterNetworkTokens, getCapabilities, getDexPools, getNetworkDexes…)

Recorded from our own daily tools/list handshake. A shrinking toolset is a real signal for an agent choosing a server; a gap in the series means the probe did not succeed that day, not that the tools disappeared.

Details

Chains
Multichain
Agent types
MCP Server, Data Provider
Open source
Yes
Pricing
Free tier, 10,000 requests/day, no API key required
Deploys as
npm install -g / npx, or one-line Smithery install
Works with
Claude Desktop
Last checked
2026-10-15

Marketplace Signals

No marketplace signals recorded for this resource yet.

Verification status reflects evidence reviewed by Sato Hub. Self-reported claims are never presented as verified.

#mcp#dex-data#market-data#multi-chain#free-tier
See something inaccurate or outdated?Submit a correction →

Recent Activity

All news →

Releases and posts from DexPaprika MCP Server, pulled from its GitHub and X.

Releasecoinpaprika/dexpaprika-mcp2d ago

dexpaprika-mcp v2.8.0

Added getPoolIndicator . RSI, EMA, MACD, Bollinger Bands or VWAP for one pool, computed by the API from the pool's completed candles and returned as a time series, so an agent no longer has to fetch getPoolOHLCV and do the maths itself. Pick one with indicator , pass interval , and optionally start , end , limit and cursor . History depth and interval follow the same plan limits as getPoolOHLCV .

Multichain
GitHub ↗
Releasecoinpaprika/dexpaprika-mcp3d ago

dexpaprika-mcp v2.7.3

Added Pool tools sort by the 48h price change. getNetworkPools , getDexPools , getNetworkPoolsFilter and search pool results now accept sort_by=price_change_percentage_48h , which the REST API added to /pools/search and /networks/{network}/pools/search . Before this, the value failed the tool schema. Token tools stay on the 24h window, as tokens/search does. getNetworkPoolsFilter filters on the 48

Multichain
GitHub ↗
Releasecoinpaprika/dexpaprika-mcp13d ago

dexpaprika-mcp v2.7.2

Fixed getPoolTransactions no longer says it is keyless. Since 2026-09-30 pool transactions answer only Dev, Pro and Enterprise keys, on api-pro.dexpaprika.com . The tool description, the server instructions and the getCapabilities workflows and pitfalls now say so, and name the two settings that make it work: DEXPAPRIKA_API_KEY set to the paid key and DEXPAPRIKA_API_BASE_URL=https://api-pro.dexpap

Multichain
GitHub ↗
Releasecoinpaprika/dexpaprika-mcp16d ago

dexpaprika-mcp v2.7.1

Changed README and the getKeyStatus 401 hint now just say to send the key on its own. Both used to describe what a prefix in front of the key does on the wire. They now say only what to send: the key alone, as the entire Authorization value, with nothing in front of it.

Multichain
GitHub ↗
Releasecoinpaprika/dexpaprika-mcp16d ago

dexpaprika-mcp v2.7.0

Added getTokenOHLCV . Historical USD OHLCV candles for a token, computed as a volume-weighted price across every pool the token trades in on the network (volume is summed across those pools too), so it answers "price history of this token" rather than one pair. Same parameter shapes as getPoolOHLCV ( network , token_address , start , end , interval , limit ), but there is no inversed parameter: th

Multichain
GitHub ↗
Releasecoinpaprika/dexpaprika-mcp17d ago

dexpaprika-mcp v2.6.0

Changed Time filters take relative offsets. Since 2026-09-28 the API accepts the same shapes as OHLCV start on getPoolTransactions from / to and on created_after / created_before in getNetworkPoolsFilter and filterNetworkTokens : a relative offset from now ( -1h , -24h , -7d ), Unix seconds, RFC3339 or YYYY-MM-DD . These parameters were typed as numbers, so -24h was rejected before it reached the

Multichain
GitHub ↗

Listing History

Recorded changes to DexPaprika MCP Server's listing — status, verification, Sato Score, and recent releases. Full history is kept in the listing record.

  1. Oct 13, 2026
    New release published
  2. Oct 12, 2026
    New release published
  3. Jul 29, 2026
    10 releases tracked
    Showing the 2 most recent. Full release history is retained in the listing record.
  4. Jul 20, 2026
    Edited: mcp endpoint url
  5. Jul 19, 2026
    Edited: mcp endpoint url
  6. Jul 18, 2026
    Sato Hub began tracking this listing
  7. Jul 14, 2026
    Enriched: supported integrations
  8. Jul 14, 2026
    Auto-enriched: deployment options
  9. Jul 13, 2026
    Listed on Sato Hub

Compared with

Appears in

Related Resources

Reference

QuestionsShowHide

Questions people ask about DexPaprika MCP Server

Is DexPaprika MCP Server open source?
Yes. DexPaprika MCP Server is open source under the MIT license; the repository is https://github.com/coinpaprika/dexpaprika-mcp. Checked as of 2026-10-15.
Which chains does DexPaprika MCP Server support?
DexPaprika MCP Server lists support for Multichain as of 2026-10-15.
Is DexPaprika MCP Server still maintained?
The most recent code activity Sato Hub observed was on 2026-10-13 (last commit 2026-10-13, last release 2026-10-13), which Sato Hub labels "Active". Posts on X are not counted as maintenance. Activity is a recency signal, not a quality judgment.
How do I install or run DexPaprika MCP Server?
node. Install: npm install -g dexpaprika-mcp. Entry: dexpaprika-mcp. This is taken from the project's own documentation and has not been reproduced by Sato Hub. It runs as an MCP server ({"mcpServers":{"dexpaprika":{"command":"npx","args":["dexpaprika-mcp@latest"]}}}).
Is DexPaprika MCP Server verified on Sato Hub?
Sato Hub holds one earned check for DexPaprika MCP Server: Live endpoint probed — we called the hosted MCP endpoint and it answered with its real tool inventory (proves the interface works, not runtime safety). Its Sato Score is 86 of 100, a measure of how open, active and verifiable the project is, not a safety, quality or returns grade.
Cite this pageShowHide

Cite this page

Sato Hub. "DexPaprika MCP Server — Sato Hub." Sato Hub, updated 2026-10-15, accessed 2026-10-15. https://satohub.ai/resources/dexpaprika-mcp

Data last refreshed 2026-10-15; this page is rebuilt daily. Citations carry the date so a reader can tell which snapshot a claim came from. Catalog data is licensed CC-BY-4.0.

Join the Sato Hub Briefing

Sign up for the Briefing: the agents, tools, and infrastructure that actually shipped, and why they matter.