CoinPaprika MCP Server
OfficialRelated Servers
Alternatives to CoinPaprika MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables access to Coinpaprika cryptocurrency data, including coin listings, prices, historical OHLC, market overview, and search through MCP tools.444 npm1MIT
- AlicenseAqualityDmaintenanceProvides real-time access to cryptocurrency and DEX data across multiple blockchains, enabling users to analyze tokens, pools, trading volumes, and perform technical analysis through DexPaprika's API. No API keys required for seamless integration with AI assistants.11171 npmMIT
- AlicenseNot gradedqualityDmaintenanceConnects AI agents to real-time cryptocurrency market data from CoinGecko API, enabling price lookups, coin details, market rankings, search, and trending crypto queries through natural language.20 npmApache 2.0
- AlicenseAqualityBmaintenanceEnables AI agents to fetch live crypto prices and market data, convert between crypto and fiat, track EVM gas fees, value portfolios, calculate profit/loss, and view historical charts and trending metrics with zero configuration required.1074 npmMIT
- AlicenseAqualityDmaintenanceLive market data for AI agents. 8 tools: real-time crypto prices, OHLCV candles, order books, market cap rankings, trending coins, technical analysis (RSI/SMA/z-score), asset comparison, and Fear & Greed index. Zero API keys, zero dependencies.281MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to access Coinmarketcap data through real API endpoints with no authentication required, supporting crypto and DeFi queries.-
TDQS
Scored across 30 tools
Descriptions are unusually explicit about boundaries, repeatedly naming the sibling tool to use instead (e.g. getCoinExchanges vs getCoinMarkets, getCoinOHLCVLatest/Today/Historical, getTickers vs getTickersById). The only residual confusion comes from the dense family of near-identical ticker/OHLCV tools and search vs resolveId, but each has a stated 'use X for Y' rule that an agent can follow.
The dominant pattern is getXById, but it breaks in several places: getExchangeByID capitalizes ID while others use Id, getHistoricalTickerByContract reverses the word order used by getTickersHistoricalById, and keyInfo/status/search/resolveId/priceConverter abandon the verb_noun convention entirely. Still readable, but not a predictable pattern an agent can extrapolate.
30 tools is at the heavy end for a market-data API, though most map to genuine distinct endpoints across coins, exchanges, contracts, tags, people and global stats. Several could be consolidated (OHLCVLatest vs OHLCVToday, getCoinExchanges vs getCoinMarkets, getTickers vs getTickersById) to trim the surface.
Coverage is broad and lifecycle-complete for read-only market data: discovery (getCoins/search/resolveId), pricing (spot, historical, OHLCV, by-contract), exchanges, markets, contracts, tags, people, conversion, cross-mapping and changelog. Minor gaps: ICOs are referenced by getTags/search/getTagById but no ICO detail tool exists, and there is no batch/multi-coin price fetch.