CoinPaprika MCP
Official CoinPaprika MCP: 30 tools for prices, tickers, OHLCV, and exchange data across 8,000+ coins.
- Sato Score78
- ChainsMultichain
CoinPaprika MCP is an open-source MCP server by CoinPaprika, with last code activity on 2026-08-19 (Recent). Latest release on 2026-08-19. Sato Score 78/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 CoinPaprika MCP →Last commit Aug 19, 2026 · Last release Aug 19, 2026 (v1.4.0) · ★ 10
Listed from coinpaprika.com on 2026-07-13. Install: not attempted. Evidence →
Next step
Watch CoinPaprika MCP
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/mcpRun Sato Hub Preflight on coinpaprika/coinpaprika-mcp before I use it.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
CoinPaprika's official MCP server gives agents on-demand access to CoinPaprika's market-data API through 30 tools spanning coin listings and profiles, real-time tickers and quotes, OHLCV candles, exchange and market data, tags, team info, and contract lookups across 8,000+ coins and 200+ exchanges — no API key required for the free tier. A builder installs it via npm or points an MCP client at CoinPaprika's hosted streamable-HTTP endpoint, with optional paid-tier tools (historical data, ID mapping) unlocked by an API key.
Sato Score
78/100· HighHow open, active & verifiable — not a safety or returns grade.
- Maintenance & liveness
- 35/35
- Code transparency
- 18/20
- Interface verifiability
- 10/10
- Docs & demo
- 0/10
- Listing transparency & provenance
- 12/15
- Independent verification
- 3/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).
Evidence — listed vs checked · what the words mean
Listed from coinpaprika.com on 2026-07-13. Install: not attempted.
| Claim | Value | Evidence | Source | Checked |
|---|---|---|---|---|
| Chains supported | Multichain | self-reported | coinpaprika.com | as of 2026-10-15 |
| Verification status | Self-Reported — not independently reviewed | self-reported | coinpaprika.com | as of 2026-10-15 |
| Recent activity | last release 2026-08-19 · last commit 2026-08-19 | observed | github.com/coinpaprika/coinpaprika-mcp | 2026-10-15 |
| Install works | documented by the project, not run by Sato Hubnot attempted: no falsifiable install+entry probe from deploy_spec | self-reported | github.com/coinpaprika/coinpaprika-mcp | as of 2026-09-14 |
| MCP endpoint answers | answered — 31 tools listed | observed | mcp.coinpaprika.com | 2026-10-15 |
| Daily check record | 90 of 90 daily checks since 2026-07-17 succeededa success rate of our checks, not uptime; the source is this listing's own history | observed | — | 2026-10-14 |
| Deploys as | Hosted API, npmconfidence 0.90 | self-reported | github.com/coinpaprika/coinpaprika-mcp | as of 2026-07-14 |
| Works with | Claude Desktop, Claude Codeconfidence 0.85 | self-reported | github.com/coinpaprika/coinpaprika-mcp | as of 2026-07-14 |
| Sato Score | 78/100 (High)how open, active and verifiable — not a safety or quality grade | computed | satohub.ai | 2026-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 — not run by us — no falsifiable install+entry probe from deploy_spec
Runtime: remote
connect to the hosted endpoint https://mcp.coinpaprika.com/streamable-http (no install)
or self-host: npx @coinpaprika/mcp@latest
{"mcpServers": {"coinpaprika": {"url": "https://mcp.coinpaprika.com/streamable-http"}}}claude mcp add --transport http satohub-coinpaprika-mcp https://mcp.coinpaprika.com/streamable-http
A remote server: your client connects to the project's endpoint. Installing runs third-party software under your own credentials. Sato Hub publishes the documented invocation and, where the harness reproduced it, the date it did — neither is a safety review.
Read from the project’s own docs as of 2026-09-14. What a deploy spec is →
Tool inventory — 31 tools, probed live 2026-10-15
getCoins— List all available coins with id, name, symbol and rank. Use to discover coins or map a name to an id. Does NOT include prices; for prices use getTickers or getTickersById. Read-only; limit caps the ngetCoinById— Get descriptive project information about a coin: description, links, team and tags. Use for 'tell me about Uniswap', 'what is this project'. Does NOT include price; for price and market cap use getTigetCoinEvents— Get the timeline of events for a coin (launches, partnerships, hard forks, conference talks) with dates and descriptions. Use for 'what is happening with X', 'upcoming events for Ethereum', 'X roadmapgetCoinExchanges— List the exchanges that LIST a specific coin (venue names only). Use for 'which exchanges list X', 'is X on Coinbase', 'where is X listed'. For where to BUY with per-market price and volume use getCoigetCoinMarkets— Get the specific markets and trading pairs where a coin trades, with per-market price and 24h volume. Use for 'where can I buy X', 'X price on Binance', 'best market for X'. For just the list of exchagetCoinOHLCVLatest— Get the latest full-day OHLC candle (open, high, low, close and volume) for a coin. Use for 'yesterday's candle for BTC'. For the live spot price use getTickersById. Read-only; coinId must be a canonigetCoinOHLCVToday— Get today's in-progress OHLC candle for a coin. Use for 'today's high and low for ETH'. For the current spot price use getTickersById; for past candles use getCoinOHLCVHistorical. Read-only; coinId isgetCoinOHLCVHistorical— Get OHLC candles (open, high, low, close, volume) for a coin. Use for 'daily chart last month', 'hourly candles since Jan 1'. For one past price use getTickersHistoricalById; for the latest candle usegetTickers— Get current prices, market caps and 24h changes for the top cryptocurrencies ranked by market cap. Use for 'top 5 coins', 'top crypto today', 'biggest cryptocurrencies', or a market snapshot. For onegetTickersById— Get the current price, market cap, 24h change and volume of one cryptocurrency in USD or another quote currency. Use for 'what is the price of X', 'how much is Bitcoin worth', 'BTC to USD', 'ETH pricegetTickersHistoricalById— Get a coin's price, market cap and volume at past times as point-in-time snapshots (not OHLC candles). Use for 'price of BTC last Tuesday', 'ETH market cap on 2024-01-01'. For OHLC chart candles use ggetExchanges— List exchanges tracked by CoinPaprika as a list ranked by rank, each with id, name, trust score, active market count and 24h volume. Use for 'top exchanges by volume', 'biggest crypto exchanges', or tgetExchangeByID— Get details for a specific exchange: 24h volume, market count, trust score, links and fiat support. Use for 'tell me about Binance', 'Coinbase exchange stats', 'is X a trustworthy exchange'. For the pgetExchangeMarkets— List the trading pairs (markets) on one exchange as a list, each with the pair, base and quote coin ids, latest price, 24h volume and category. Use for 'what pairs trade on Binance', 'markets on KrakegetPeopleById— Get the profile of one person in crypto by id: name, description or bio, teams_count, positions held, and linked projects plus social and code accounts. Use for 'who is Vitalik Buterin', 'background ogetTags— List all CoinPaprika tags (categories such as 'defi', 'stablecoin', 'memecoin', 'ai') used to group coins, returned as a list with each tag's id, name, coin_counter and ico_counter. Use for 'what crypgetTagById— Get details for one CoinPaprika tag (a category such as 'defi' or 'stablecoin'): its id, name, description, coin_counter, ico_counter, and optionally the coins and ICOs grouped under it. Use for 'whatgetPlatforms— List the smart-contract platforms (blockchains such as ethereum, bnb, polygon) for which CoinPaprika indexes token contracts. Use for 'which chains are supported for contract lookups', 'list contractgetContracts— List the token contract addresses tracked on one platform as a list, mapping each contract to its CoinPaprika coin id. Use for 'contracts on ethereum', 'what tokens does BSC have', or to map a contracgetTickerByContract— Get the current price and market data of a token by its contract address (for on-chain and DeFi tokens). Use when you have a contract address (0x...) rather than a name. For history use getHistoricalTgetHistoricalTickerByContract— Get a token's price and market history by its contract address, as a time series. Use for 'token price on 2024-01-01 by address', 'hourly history for a contract'. For its current price use getTickerBystatus— Get the CoinPaprika MCP server's status and configuration (uptime, mode, enabled features). Use when asked 'is the server up', 'what mode am I in', 'server status'. This reports the MCP server itself,getGlobal— Get a global crypto market overview: total market cap, total 24h volume, Bitcoin dominance, and market-wide 24h change. Use for 'how is the crypto market doing', 'total market cap', 'BTC dominance'. Fsearch— Broadly search CoinPaprika across coins, exchanges, ICOs, people and tags by name or symbol when the entity type is unknown or you are exploring. Use for 'find anything called X'. If you specificallyresolveId— Resolve a fuzzy coin, exchange, person or tag name or symbol to a ranked list of candidate CoinPaprika ids, best first (take the top one). Call FIRST when you have a bare name or symbol but need an idpriceConverter— Convert an amount from one crypto or fiat to another at the current rate, e.g. 'how much is 0.5 BTC in USD', 'convert 100 USDC to EUR'. For a plain coin price without an amount, use getTickersById. RegetCapabilities— Get the server's capabilities, supported workflow patterns, validation rules and recommended tool sequences. Use FIRST to onboard as an agent, or when asked 'what can this server do', 'how should I chkeyInfo— Get details and usage for the CoinPaprika API key you supplied: plan, quota, requests remaining and expiry. Use for 'what plan am I on', 'how many requests are left', 'is my API key valid'. Read-only;getMappings— Get mappings between CoinPaprika ids and external or legacy identifiers (CoinMarketCap, CoinGecko, CryptoCompare, ISIN, DTI) so you can reconcile ids across systems. Use for 'map CoinPaprika ids to X'getChangelogIDs— Get the ids of recent changes to CoinPaprika's coin and exchange listings (additions, renames, delistings) for syncing a local dataset. Use for 'what changed recently', 'new or delisted coins', 'listisubmitFeedback— Report a problem or gap back to the CoinPaprika MCP maintainers: call it when you got stuck, a response was unexpected, information you needed was missing, or a tool did not behave as documented. Use
- 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
- 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
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 — 31 now, peak 31, since 2026-07-17
- 2026-09-23 0 → 31 +31 (getCapabilities, getChangelogIDs, getCoinById, getCoinEvents…)
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
- Deploys as
- Hosted API, npm
- Works with
- Claude Desktop, Claude Code
- 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.
Where CoinPaprika MCP fits
Related concepts: What Are MCPs? The Standard Way to Give Agents Tools, What Are Onchain Agents?
Recent Activity
All news →Releases and posts from CoinPaprika MCP, pulled from its GitHub and X.
coinpaprika-mcp v1.4.0: Release 1.4.0 (#15)
Release 1.4.0 Closes the Unreleased section. The correction it carries has been sitting on main since #14 and is not on npm: 1.3.3 is still the published version, so every install today gets a server that reports the free tier as 10,000 calls a day and tells the caller its 429 resets at midnight UTC. The real allowance is 20,000 calls a month. Also promotes the meta.rate_limit removal into its own
coinpaprika-mcp v1.3.3
Version bump only; no functional or API changes since 1.3.2. Re-release under a fresh version.
coinpaprika-mcp v1.3.2
Round 2 of the tool-definition-quality work: sharpened the 12 lowest-scoring tool descriptions (enumerate every enum value, state each parameter's default and range, describe the returned shape and no-match behavior, name sibling tools) and fixed a description-vs-schema contradiction in resolveId. No behavior change. Published to npm as @coinpaprika/mcp@1.3.2.
Listing History
Recorded changes to CoinPaprika MCP's listing — status, verification, Sato Score, and recent releases. Full history is kept in the listing record.
- Sep 23, 2026Sato Score tier: Medium → HighScore 66 → 76.
- Aug 19, 2026New release published
- Jul 29, 2026New release published
- Jul 18, 2026Sato Hub began tracking this listing
- Jul 14, 2026Edited: mcp endpoint url
- Jul 14, 2026Auto-enriched: deployment options, supported integrations, has pricing
- Jul 13, 2026Listed on Sato Hub
Compared with
Appears in
Related Resources
Coinbase AgentKit
ActiveCoinbase's toolkit for giving AI agents wallets and the ability to take onchain actions.
Hyperliquid
ActiveOnchain perpetual futures and spot DEX running on its own L1 with an HyperEVM smart-contract layer.
Model Context Protocol (MCP)
ActiveAnthropic's open standard for connecting AI systems to external tools and data sources.
Reference
QuestionsWhat people ask about this pageShowHide
Questions people ask about CoinPaprika MCP
- Is CoinPaprika MCP open source?
- Yes. CoinPaprika MCP is open source under the MIT license; the repository is https://github.com/coinpaprika/coinpaprika-mcp. Checked as of 2026-10-15.
- Which chains does CoinPaprika MCP support?
- CoinPaprika MCP lists support for Multichain as of 2026-10-15.
- Is CoinPaprika MCP still maintained?
- The most recent code activity Sato Hub observed was on 2026-08-19 (last commit 2026-08-19, last release 2026-08-19), which Sato Hub labels "Recent". Posts on X are not counted as maintenance. Activity is a recency signal, not a quality judgment.
- How do I install or run CoinPaprika MCP?
- remote. Install: connect to the hosted endpoint https://mcp.coinpaprika.com/streamable-http (no install) && or self-host: npx @coinpaprika/mcp@latest. Entry: {"mcpServers": {"coinpaprika": {"url": "https://mcp.coinpaprika.com/streamable-http"}}}. This is taken from the project's own documentation and has not been reproduced by Sato Hub. It runs as an MCP server (https://mcp.coinpaprika.com/streamable-http).
- Is CoinPaprika MCP verified on Sato Hub?
- Sato Hub holds one earned check for CoinPaprika MCP: 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 78 of 100, a measure of how open, active and verifiable the project is, not a safety, quality or returns grade.
Cite this pagePlain text, APA or BibTeXShowHide
Cite this page
Sato Hub. "CoinPaprika MCP — Sato Hub." Sato Hub, updated 2026-10-15, accessed 2026-10-15. https://satohub.ai/resources/coinpaprika-mcpData 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.