{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"awesome-dexpaprika","slug":"dexpaprika","name":"DexPaprika","type":"mcp","url":"https://github.com/coinpaprika/dexpaprika-mcp","page_url":"https://unfragile.ai/dexpaprika","categories":["mcp-servers"],"tags":[],"pricing":{"model":"open_source","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"awesome-dexpaprika__cap_0","uri":"capability://tool.use.integration.multi.blockchain.dex.pool.data.retrieval.with.real.time.indexing","name":"multi-blockchain dex pool data retrieval with real-time indexing","description":"Fetches and aggregates decentralized exchange pool data across 20+ blockchains (Ethereum, Polygon, Arbitrum, Optimism, Base, Solana, etc.) via the DexPaprika API, providing real-time pool metadata including liquidity, token pair composition, fee tiers, and protocol identifiers. The MCP server acts as a standardized interface layer that normalizes heterogeneous blockchain DEX schemas into a unified query model, enabling clients to request pools by blockchain, protocol, or token pair without managing chain-specific RPC endpoints or DEX contract ABIs.","intents":["Query available liquidity pools across multiple chains to find optimal trading pairs","Monitor real-time pool reserves and fee structures for arbitrage opportunities","Aggregate DEX data from multiple blockchains in a single unified API call","Build cross-chain liquidity dashboards without managing individual blockchain connections"],"best_for":["DeFi developers building cross-chain trading bots or aggregators","Quantitative traders analyzing liquidity fragmentation across blockchains","Teams building multi-chain portfolio management tools"],"limitations":["Data freshness depends on DexPaprika API update frequency (typically 1-5 minute latency)","Limited to pools indexed by DexPaprika — newly deployed or low-liquidity pools may not be available","No historical pool state snapshots — only current pool data accessible","Rate limiting on DexPaprika API may throttle high-frequency queries"],"requires":["DexPaprika API key (free tier available with rate limits)","MCP client implementation (Claude, custom agent, or MCP-compatible tool)","Network connectivity to DexPaprika API endpoints"],"input_types":["blockchain identifier (string: 'ethereum', 'polygon', 'solana', etc.)","protocol name (string: 'uniswap', 'curve', 'raydium', etc.)","token addresses or symbols (string)","optional filters (fee tier, liquidity range)"],"output_types":["structured JSON with pool metadata (address, reserves, fee, TVL)","array of pool objects with standardized schema across chains"],"categories":["tool-use-integration","data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-dexpaprika__cap_1","uri":"capability://data.processing.analysis.token.pair.volume.and.trading.activity.analysis","name":"token pair volume and trading activity analysis","description":"Retrieves historical and real-time trading volume, price movements, and transaction counts for token pairs across DEX protocols. The capability aggregates volume metrics across multiple DEX venues on the same blockchain, providing traders with comprehensive liquidity and activity signals. Data is normalized into time-series format (hourly, daily aggregations) enabling trend analysis and volatility calculations without requiring manual data transformation or external analytics libraries.","intents":["Identify high-volume token pairs for optimal trade execution","Detect unusual trading activity or volume spikes indicating market moves","Compare trading activity across different DEX protocols for the same pair","Build volume-weighted price feeds for more accurate pricing signals"],"best_for":["Algorithmic traders building volume-based entry/exit signals","Market makers optimizing liquidity provision across DEX venues","Analytics platforms tracking DeFi market microstructure"],"limitations":["Volume data aggregation may have 5-15 minute delays depending on blockchain finality","Historical volume data retention limited to 90-180 days (varies by DexPaprika plan)","Does not include off-chain order book data or CEX volume for comparison","Volume metrics are DEX-only and exclude bridge/wrapped token trading on other chains"],"requires":["DexPaprika API key with analytics tier access","Blockchain and token pair identifiers","Time range specification for historical queries"],"input_types":["blockchain identifier (string)","token pair addresses (string tuple)","time range (ISO 8601 timestamps or relative: '24h', '7d')","aggregation interval (string: 'hourly', 'daily', '4h')"],"output_types":["time-series JSON with volume, price, transaction count per interval","aggregated statistics (min/max volume, average price, volatility)"],"categories":["data-processing-analysis","search-retrieval"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-dexpaprika__cap_2","uri":"capability://data.processing.analysis.cross.chain.token.metadata.and.symbol.resolution","name":"cross-chain token metadata and symbol resolution","description":"Resolves token identities across multiple blockchains, mapping token addresses to canonical symbols, decimals, logos, and chain-specific contract addresses. The capability handles wrapped/bridged token variants (e.g., USDC on Ethereum vs Polygon vs Arbitrum) and provides canonical token information to prevent address collisions and enable unified token tracking. Uses DexPaprika's centralized token registry which maintains mappings across 5M+ tokens, reducing need for manual address lookups or maintaining separate token lists per chain.","intents":["Resolve token contract addresses to human-readable symbols across chains","Identify canonical vs wrapped token variants to avoid trading the wrong asset","Build unified token search across multiple blockchains","Fetch token metadata (decimals, logos) for UI rendering without external image CDNs"],"best_for":["Multi-chain wallet and portfolio tracking applications","DEX aggregators normalizing token identities across venues","Trading bots that need canonical token identification for order routing"],"limitations":["Token metadata updates may lag behind new token deployments by 24-48 hours","Wrapped token mappings depend on bridge protocol indexing — not all bridges supported","Logo/image URLs may become stale if hosted on external CDNs","No real-time token creation detection — only indexed tokens available"],"requires":["DexPaprika API key","Token address (contract address) or symbol string","Blockchain identifier for address resolution"],"input_types":["token address (string: '0x...' format)","token symbol (string: 'USDC', 'WETH', etc.)","blockchain identifier (string)","optional: search query for fuzzy matching"],"output_types":["structured JSON with token metadata (symbol, decimals, logo URL, chain addresses)","array of token matches for ambiguous queries"],"categories":["data-processing-analysis","memory-knowledge"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-dexpaprika__cap_3","uri":"capability://search.retrieval.dex.protocol.and.venue.enumeration.with.chain.filtering","name":"dex protocol and venue enumeration with chain filtering","description":"Lists all supported DEX protocols and their availability across blockchains, enabling clients to discover which protocols operate on which chains and their relative market share. The capability returns protocol metadata including protocol type (AMM, order book, hybrid), supported token pairs, and total value locked (TVL) per protocol per chain. This enables dynamic protocol selection for routing and helps identify protocol-specific opportunities or constraints.","intents":["Discover which DEX protocols are available on a specific blockchain","Compare protocol TVL and market share across chains","Identify protocol-specific trading pairs or features","Route trades to optimal protocols based on liquidity distribution"],"best_for":["DEX aggregators building dynamic routing logic","Researchers analyzing DEX market structure and competition","Developers building protocol-agnostic trading interfaces"],"limitations":["Protocol list is static snapshot from DexPaprika — new protocols may not appear immediately","TVL figures are point-in-time and may be 5-30 minutes stale","Does not include protocol-specific parameters (swap fees, slippage, minimum liquidity)","No protocol performance metrics (uptime, transaction success rate)"],"requires":["DexPaprika API key","Optional: blockchain identifier to filter protocols"],"input_types":["blockchain identifier (string, optional)","protocol type filter (string: 'amm', 'orderbook', optional)"],"output_types":["array of protocol objects with metadata (name, type, TVL, supported chains)","protocol availability matrix (protocol x blockchain)"],"categories":["search-retrieval","data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-dexpaprika__cap_4","uri":"capability://tool.use.integration.mcp.tool.schema.standardization.and.function.calling","name":"mcp tool schema standardization and function calling","description":"Exposes DexPaprika DEX analytics capabilities through the Model Context Protocol (MCP) standard, enabling AI agents and LLM-based tools to invoke DEX queries via standardized function-calling schemas. The MCP server translates natural language requests from Claude or other MCP clients into structured API calls, handles authentication with DexPaprika API keys, manages rate limiting, and returns results in agent-friendly JSON format. This abstraction allows non-technical prompts like 'find high-volume USDC pairs on Ethereum' to be automatically converted to correct API parameters.","intents":["Enable AI agents to query DEX data without manual API integration","Allow Claude and other LLMs to analyze DeFi market conditions via natural language","Build autonomous trading bots that can discover and evaluate trading opportunities","Create conversational DeFi analytics interfaces powered by LLMs"],"best_for":["AI agent developers building autonomous DeFi tools","Teams integrating Claude with DeFi workflows","Non-technical users building LLM-powered trading assistants"],"limitations":["MCP client must support DexPaprika server — requires explicit configuration","LLM interpretation of natural language queries may be ambiguous (e.g., 'high volume' threshold)","No built-in transaction execution — only data retrieval and analysis","Rate limiting applies per API key, not per MCP client session"],"requires":["MCP-compatible client (Claude, custom agent framework)","DexPaprika API key configured in MCP server environment","Network connectivity between MCP client and server"],"input_types":["natural language prompts (string)","structured function parameters (JSON)","MCP tool invocation requests"],"output_types":["structured JSON responses with DEX data","formatted text summaries for LLM consumption","error messages with remediation guidance"],"categories":["tool-use-integration","planning-reasoning"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-dexpaprika__cap_5","uri":"capability://search.retrieval.blockchain.network.enumeration.and.chain.metadata","name":"blockchain network enumeration and chain metadata","description":"Provides metadata for all supported blockchains including chain IDs, RPC endpoints, block explorers, and native token information. The capability enables clients to dynamically discover supported chains and their properties without hardcoding chain lists. Returns standardized chain metadata (name, symbol, decimals, logo) enabling UI rendering and chain selection interfaces.","intents":["Discover all blockchains supported by DexPaprika for dynamic chain selection","Retrieve chain metadata for UI rendering (logos, names, symbols)","Map between chain IDs and human-readable names","Build chain-agnostic applications that adapt to available blockchains"],"best_for":["Multi-chain application developers building dynamic chain selectors","DEX aggregators supporting variable blockchain sets","Teams building chain-agnostic portfolio tools"],"limitations":["Chain list is static from DexPaprika — new chains may not appear immediately","Does not include real-time chain status or network health metrics","RPC endpoints provided are informational only — not guaranteed to be operational","No chain-specific parameters (gas prices, finality time, consensus mechanism)"],"requires":["DexPaprika API key"],"input_types":["optional: chain identifier filter (string)"],"output_types":["array of chain objects with metadata (name, ID, symbol, logo, explorer)","chain lookup by ID or name"],"categories":["search-retrieval","data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-dexpaprika__cap_6","uri":"capability://data.processing.analysis.liquidity.pool.composition.and.reserve.tracking","name":"liquidity pool composition and reserve tracking","description":"Retrieves detailed composition of liquidity pools including token reserves, reserve ratios, and impermanent loss indicators. The capability tracks how much of each token is locked in pools and enables calculation of slippage for hypothetical trades. Provides real-time reserve data enabling traders to assess pool depth and identify thin liquidity conditions that may result in high slippage.","intents":["Calculate expected slippage for a trade given current pool reserves","Identify pools with imbalanced reserves indicating potential arbitrage","Monitor reserve changes to detect large trades or liquidity withdrawals","Assess pool depth before executing large trades"],"best_for":["Traders optimizing trade execution and slippage minimization","Arbitrage bots detecting reserve imbalances","Market makers analyzing pool composition for liquidity provision"],"limitations":["Reserve data updates with blockchain block time — 12-15 second latency on Ethereum","Does not include historical reserve snapshots for trend analysis","Slippage calculations are estimates — actual slippage depends on transaction ordering","No fee tier information for some protocols"],"requires":["DexPaprika API key","Pool identifier (address or protocol-specific ID)","Blockchain identifier"],"input_types":["pool address (string)","blockchain identifier (string)","optional: trade amount for slippage calculation"],"output_types":["structured JSON with reserve amounts, token addresses, reserve ratios","calculated slippage percentage for hypothetical trade amounts"],"categories":["data-processing-analysis","planning-reasoning"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-dexpaprika__cap_7","uri":"capability://data.processing.analysis.historical.price.and.ohlcv.data.retrieval","name":"historical price and ohlcv data retrieval","description":"Provides historical price data (OHLCV: Open, High, Low, Close, Volume) for token pairs across DEX protocols at multiple time granularities (1m, 5m, 15m, 1h, 4h, 1d). Data is aggregated from on-chain transactions and normalized into candlestick format enabling technical analysis without requiring manual price calculation from transaction logs. Supports time range queries enabling backtesting and historical analysis.","intents":["Backtest trading strategies using historical DEX price data","Build technical analysis indicators (moving averages, RSI, MACD) from OHLCV data","Analyze price discovery across DEX protocols and blockchains","Detect price divergences between chains for arbitrage opportunities"],"best_for":["Quantitative traders backtesting DEX trading strategies","Technical analysts studying DeFi market microstructure","Researchers analyzing cross-chain price discovery"],"limitations":["Historical data retention limited to 90-180 days depending on DexPaprika plan","OHLCV data is DEX-only and does not include CEX prices for comparison","Granularity below 1-minute not available due to blockchain block time constraints","Price data may have gaps during low-liquidity periods or protocol downtimes"],"requires":["DexPaprika API key with historical data access","Token pair identifiers","Blockchain identifier","Time range (start/end timestamps)"],"input_types":["token pair (tuple of addresses or symbols)","blockchain identifier (string)","time range (ISO 8601 timestamps)","candle interval (string: '1m', '5m', '1h', '1d', etc.)"],"output_types":["array of OHLCV candles with timestamp, open, high, low, close, volume","formatted for technical analysis libraries (pandas, numpy)"],"categories":["data-processing-analysis","search-retrieval"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":29,"verified":false,"data_access_risk":"moderate","permissions":["DexPaprika API key (free tier available with rate limits)","MCP client implementation (Claude, custom agent, or MCP-compatible tool)","Network connectivity to DexPaprika API endpoints","DexPaprika API key with analytics tier access","Blockchain and token pair identifiers","Time range specification for historical queries","DexPaprika API key","Token address (contract address) or symbol string","Blockchain identifier for address resolution","Optional: blockchain identifier to filter protocols"],"failure_modes":["Data freshness depends on DexPaprika API update frequency (typically 1-5 minute latency)","Limited to pools indexed by DexPaprika — newly deployed or low-liquidity pools may not be available","No historical pool state snapshots — only current pool data accessible","Rate limiting on DexPaprika API may throttle high-frequency queries","Volume data aggregation may have 5-15 minute delays depending on blockchain finality","Historical volume data retention limited to 90-180 days (varies by DexPaprika plan)","Does not include off-chain order book data or CEX volume for comparison","Volume metrics are DEX-only and exclude bridge/wrapped token trading on other chains","Token metadata updates may lag behind new token deployments by 24-48 hours","Wrapped token mappings depend on bridge protocol indexing — not all bridges supported","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.05,"quality":0.41,"ecosystem":0.39999999999999997,"match_graph":0.25,"freshness":0.52,"weights":{"adoption":0.25,"quality":0.25,"ecosystem":0.15,"match_graph":0.23,"freshness":0.12}},"observed_outcomes":{"matches":0,"success_rate":0,"avg_confidence":0,"top_intents":[],"last_matched_at":null},"maintenance":{"status":"active","updated_at":"2026-06-17T09:51:03.038Z","last_scraped_at":"2026-05-03T14:00:15.503Z","last_commit":null},"community":{"stars":null,"forks":null,"weekly_downloads":null,"model_downloads":null,"model_likes":null}},"distribution":{"claim_url":"https://unfragile.ai/submit?claim=dexpaprika","compare_url":"https://unfragile.ai/compare?artifact=dexpaprika"}},"signature":"keBwwSGjj+XhWm2chLdq7DEOPnoIDjC/+GmW1k/6mopDnN0yD8qU8xG9KxI53y0nolLzIxSakpWcN1SwepRlBw==","signedAt":"2026-06-23T03:40:44.837Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/dexpaprika","artifact":"https://unfragile.ai/dexpaprika","verify":"https://unfragile.ai/api/v1/verify?slug=dexpaprika","publicKey":"https://unfragile.ai/api/v1/trust-passport-public-key","spec":"https://unfragile.ai/trust","schema":"https://unfragile.ai/schema.json","docs":"https://unfragile.ai/docs"}}