DexPaprika (CoinPaprika)
OfficialRelated Servers
Alternatives to DexPaprika (CoinPaprika)
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceAn MCP server that provides AI agents with real-time access to DEX liquidity pool data, enabling smarter trading, analytics, and automated strategies.101MIT
- 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.11MIT
- AlicenseNot gradedqualityFmaintenanceOfficial MCP server that turns The Graph’s Token API into a plug-and-play web3 data tool. Exposes ERC-20 & NFT metadata, balances, transfers, top-holder stats, prices, and more, allowing LLMs to run SQL queries on structured and indexed blockchain data.2Apache 2.0
- AlicenseAqualityDmaintenanceAn MCP server that tracks and analyzes DEX liquidity pools to power intelligent DeFi agents and automated strategies.12MIT
- AlicenseAqualityDmaintenanceA comprehensive cryptocurrency market-data MCP server with 49 tools across six data sources, enabling LLMs to answer market questions via natural language.49MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that provides DeFi data tools (crypto prices, whale concentration, funding rates) for AI agents via the x402 protocol.21 npm1MIT
TDQS
Scored across 20 tools
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.
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.
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.
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.