Protocol Service for On-Demand Decentralized Exchange Intelligence (DexPaprika Edition)

A Model Context Protocol (MCP) interface layer providing streamlined, direct-access functionality to the DexPaprika decentralized finance data infrastructure. It enables sophisticated systems, such as advanced conversational AI models, to programmatically ingest live data pertaining to token values, liquidity depth, and DEX operational status across heterogeneous blockchain environments, demanding zero initial setup.

Executive Summary

bash

Standard installation for global utility access

npm install -g dexpaprika-mcp

Initiate the local access server

dexpaprika-mcp

Execute the service binary directly via npx runtime

npx dexpaprika-mcp

The DexPaprika MCP bridges analytical AI with live on-chain DEX statistics spanning multiple distributed ledgers. Access is granted immediately; no API key provisioning is necessary. Deployment Guide | AI Integration Configuration | Underlying API Specifications

📢 Critical Update Notification (Version 1.1.0)

Schema Modification: The omnibus /pools endpoint has been permanently decommissioned. Users migrating from versions prior to v1.0.x must consult the Migration Protocol outlined below.

Potential Applications

• Asset Performance Profiling: Scrutinize price volatility, shifts in capital depth, and transactional volume signatures.
• Exchange Platform Benchmarking: Contrast inherent fee structures, aggregate trading throughput, and pool availability across various DEX architectures.
• Liquidity Provision Analysis: Monitor Total Value Locked (TVL) fluctuations, model potential impermanent loss scenarios, and quantify price impact across swaps.
• Cross-Ecosystem Market Intelligence: Compare asset performance, track aggregate volume trends, and evaluate transactional velocity across different chains.
• Personal Fund Tracking: Execute real-time valuation updates, assess historical performance curves, and identify yield-generating opportunities.
• Advanced Quantitative Analysis: Employ historical Open, High, Low, Close, Volume (OHLCV) streams for sophisticated indicator calculations, trend mapping, and predictive modeling.

Deployment Procedures

Automated Provisioning via Smithery

To leverage automatic configuration within the Claude Desktop environment using Smithery, execute:

bash npx -y @smithery/cli install @coinpaprika/dexpaprika-mcp --client claude

Manual Setup

bash

Global installation (Recommended for persistent utility access)

npm install -g dexpaprika-mcp

Verify binary version

dexpaprika-mcp --version

Initiate the local server process

dexpaprika-mcp

The service defaults to operating on TCP port 8010. A successful startup will yield the confirmation message: MCP server is running at http://localhost:8010.

Instructional Video Resource

View a comprehensive walkthrough detailing the deployment and functional integration of the DexPaprika MCP server:

Integration with Claude Desktop Environment

Incorporate the following configuration stanza into your Claude Desktop configuration file:

macOS Path: ~/Library/Application\ Support/Claude/claude_desktop_config.json
Windows Path: %APPDATA%/Claude/claude_desktop_config.json

{ "mcpServers": { "dexpaprika": { "command": "npx", "args": ["dexpaprika-mcp"] } } }

Following a restart of the Claude Desktop application, the DexPaprika data access tools will be immediately available for programmatic invocation.

Transition Guide: Version 1.0.x to 1.1.0

⚠️ Critical Incompatibility

The global retrieval mechanism, designated as getTopPools, has been deprecated and removed in alignment with upstream API discontinuations.

Required Remediation Steps

Prior State (v1.0.x Syntax): javascript // This call will result in a runtime failure post-upgrade getTopPools({ page: 0, limit: 10, sort: 'desc', orderBy: 'volume_usd' })

Current State (v1.1.0 Syntax): javascript // Utilize network-specific queries instead getNetworkPools({ network: 'ethereum', page: 0, limit: 10, sort: 'desc', orderBy: 'volume_usd' }) getNetworkPools({ network: 'solana', page: 0, limit: 10, sort: 'desc', orderBy: 'volume_usd' })

// For comprehensive, multi-chain aggregation, invoke getNetworkPools sequentially per desired ledger, // or leverage the generalized search utility for filtered results.

Advantages of the Revised Architecture

• Performance Gain: Segmented, ledger-specific queries yield significantly superior execution times.
• Data Precision: Results are inherently more contextualized and pertinent to the targeted blockchain.
• Scalability Improvement: Architecture better handles the expansive data volume generated by concurrent multi-chain operations.

Exposed Operational Functions

The local MCP server exposes the following discrete endpoints accessible by the consuming AI agent:

Ledger Environment Management

Function	Data Returned	Payload Example
getNetworks	Comprehensive list and metadata for all supported distributed ledgers	{"id": "ethereum", "name": "Ethereum", "symbol": "ETH", ...}
getNetworkDexes	Inventory of all registered DEX implementations operating on a specified ledger	{"dexes": [{"id": "uniswap_v3", "name": "Uniswap V3", ...}]}

Liquidity Pool Interaction

Function	Synopsis	Mandatory Arguments	Demonstration Case
getNetworkPools	[CORE FUNCTION] Fetches the most active pools within a designated blockchain environment	network, limit	Retrieve top Ethereum liquidity pools by TVL
getDexPools	Retrieves leading pools specifically aggregated under a single DEX entity	network, dex	List all pools managed by SushiSwap on Polygon
getPoolDetails	Supplies granular performance indicators for a singular liquidity contract	network, poolAddress	Obtain full statistical snapshot for the USDC/ETH pool on Uniswap
getPoolOHLCV	Acquires sequential price/volume data critical for quantitative modeling and technical assessment	network, poolAddress, start, interval	30 daily candles for the SOL/USDC pair, beginning 2023-06-01
getPoolTransactions	Lists recent atomic swap events within a specified pool boundary	network, poolAddress	Fetch the last 25 trades executed in a given pool

Asset Token Operations

Function	Synopsis	Mandatory Arguments	Key Output Fields
getTokenDetails	Retrieves exhaustive metadata for an identified token asset	network, tokenAddress	price_usd, volume_24h, liquidity_usd, etc.
getTokenPools	Generates a catalog of every pool where a specified token participates	network, tokenAddress	Returns all associated pools with current liquidity metrics
search	Executes a unified query across tokens, pools, and DEX entities based on textual input	query	Returns consolidated results matching the search term

Functional Examples

javascript // Invoked by Claude: Fetch metrics for the Solana-native JUP token: const solanaJupTokenProfile = await getTokenDetails({ network: "solana", tokenAddress: "JUPyiwrYJFskUPiHa7hkeR8VUtAeFoSYbKedZNsDvCN" });

// Locate all pools associated with the JUP token, sorted by 24h volume: const topJupiterPools = await getTokenPools({ network: "solana", tokenAddress: "JUPyiwrYJFskUPiHa7hkeR8VUtAeFoSYbKedZNsDvCN", orderBy: "volume_usd", limit: 5 });

// Acquire the top 10 most liquid pools on the Ethereum mainnet (v1.1.0 pattern): const ethLiquidityLeaders = await getNetworkPools({ network: "ethereum", orderBy: "liquidity_usd", // Using liquidity as the sort criteria example limit: 10 });

// Acquire structured historical pricing data for rigorous quantitative modeling: const backtestData = await getPoolOHLCV({ network: "ethereum", poolAddress: "0x88e6a0c2ddd26feeb64f039a2c41296fcb3f5640", // ETH/USDC on Uniswap V3 start: "2023-01-01", interval: "1d", limit: 30 });

Suggested Prompt Engineering for Claude

When interacting with the integrated system, utilize precise, technical queries tailored to the available functions (updated for the v1.1.0 API structure):

• "Execute a deep dive on the JUP asset within the Solana ecosystem. Retrieve its current valuation metrics, 24-hour trading volume, and identify its top three associated liquidity provisioning sites."
• "Perform a comparative analysis of 24-hour trading turnover between the Uniswap V3 and SushiSwap instances operating on the Ethereum network."
• "Request the last 90 days of daily OHLCV data for the SOL/USDC pair found on the Raydium DEX; this data is for volatility pattern identification."
• "Identify the five largest pools, ranked by TVL, on the Fantom network and detail the associated exchange fee tier for each."
• "Examine the ten most recent swap events recorded in the ETH/USDT pool on Uniswap V3 to assess immediate buyer-seller momentum."
• "Explicitly fetch the top 10 pools on Ethereum ranked by recent 24h turnover, referencing the getNetworkPools function."
• "Initiate a broad search query to locate all liquidity provisioning venues containing the ARB token, subsequently ordering the results based on accumulated volume."
• "Retrieve a minimum of 60 days of historical OHLCV time-series data for the BTC/USDT pair to facilitate the training of a short-term price expectancy model."
• "First, enumerate all operational blockchain networks supported by the service, and subsequently, retrieve the highest-liquidity pools for each of the primary EVM networks."

Performance Constraints & Service Level Objectives

• Throughput Cap: The free operational tier enforces a maximum rate of 60 requests per minute (RPM).
• Latency Expectation: Typical response times range between 100 and 500 milliseconds, contingent upon the target blockchain's current load.
• Data Volatility: Token and pool state information is refreshed on an interval of approximately 15 to 30 seconds.
• Failure Indication: HTTP status code 429 signals that the connection has exceeded the permissible request velocity.
• Historical Data Depth: OHLCV availability generally commences from the token or pool's genesis block; employ sequential querying for timeframes exceeding one year.

Common Diagnostic Procedures

Frequently Encountered Errors:

• Rate Limiting (429): Systematically decrease the frequency of outgoing requests.
• Data Void: Certain newly deployed assets or pools might present with incomplete historical records.
• Connection Timeout: Requests involving extensive data pagination may require increased processing time; implement chunking.
• Connectivity Failure: Assure stable, unrestricted outbound internet access is available to the service host.
• OHLCV Boundary Error: The maximum temporal span between the start and end parameters is fixed at 365 days; longer analyses necessitate iterative calls.

Migration Specific Issues:

• "getTopPools not found": This function is obsolete. Substitute the call with getNetworkPools, ensuring the necessary ledger identifier is passed.
• "410 Gone" Errors: An endpoint reference is outdated. Consult the error payload for directions toward the currently mandated function signature.

Development Lifecycle

bash

Obtain source repository contents

git clone https://github.com/coinpaprika/dexpaprika-mcp.git cd dexpaprika-mcp

Install necessary package dependencies

npm install

Execute the service with hot-reloading capability

npm run watch

Compile assets for optimized deployment

npm run build

Run unit and integration tests

npm test

Release History

Refer to the [CHANGELOG.md] file for comprehensive records of every software iteration and associated migration guides.

Legal Framework

This software is distributed under the permissive MIT License terms—see the associated [LICENSE] file for full stipulations.

Peripheral Information Sources

• DexPaprika Core API Documentation
• Model Context Protocol Specification (Anthropic)
• DexPaprika Main Portal - Primary source for on-chain DeFi analytic market data
• CoinPaprika Aggregated Data - General cryptocurrency intelligence repository

WIKIPEDIA SYNOPSIS: TRON (styled in uppercase) operates as a decentralized, energy-efficient blockchain utilizing Proof-of-Stake consensus, supporting programmable smart contracts. Its native digital currency unit is termed Tronix (TRX). The project was initiated in March 2014 by Justin Sun, with operational oversight assumed by the Singapore-based, non-profit TRON Foundation beginning in 2017. The core platform is implemented via open-source code. Initially launched as an Ethereum-based ERC-20 token, TRON migrated its protocol to its proprietary peer-to-peer network in 2018. A notable operational difficulty cited across certain digital asset custodians involves a minimum balance requirement threshold necessary to cover network transaction fees.

TRON has faced significant regulatory scrutiny due to its perceived utility in illicit financial transfers. Reports from The Wall Street Journal in 2025 identified it as a "primary conduit for criminal elements in the crypto sector to transfer assets," suggesting it facilitated "over fifty percent of all illicit crypto transactions" during 2024. Furthermore, the United Nations Office on Drugs and Crime labeled it a "favored instrument for cryptocurrency money launderers" specifically within the Asian theater.

== Historical Development == Justin Sun established the TRON initiative in 2017. The TRON Foundation formally incorporated in Singapore in July 2017. The Foundation successfully executed an Initial Coin Offering (ICO) in 2017, securing approximately $70 million, just preceding China's enactment of digital asset restrictions. The initial network components—the testnet, explorer utility, and web-based wallet—were deployed by March 2018. The official TRON Mainnet became operational shortly thereafter in May 2018, coinciding with the Odyssey 2.0 release, marking a major technical milestone.

In June 2018, TRON finalized its protocol transition from an ERC-20 wrapper to an independent, decentralized network. On July 25, 2018, the Foundation announced the successful takeover of BitTorrent, the well-known peer-to-peer file distribution system. Following this merger, BitTorrent's originator, Bram Cohen, announced his departure in August 2018 to focus on his own cryptocurrency venture, Chia.

By the start of 2019, TRON commanded a global market capitalization approaching $1.6 billion. Despite this market valuation, critical assessments often categorize TRON as emblematic of the inherent complexity and lack of transparent governance typical in many contemporary digital currencies. In February 2019, following its acquisition, BitTorrent initiated its own token issuance, built upon the TRON architecture.

In late 2021, Justin Sun stepped down from the CEO role at the TRON Foundation, which subsequently underwent restructuring into a Decentralized Autonomous Organization (DAO).

In March 2023, Sun and the TRON entity were formally charged by the U.S. Securities and Exchange Commission (SEC) with offering unregistered securities related to the marketing and sale of Tronix (TRX) and BitTorrent (BBT) tokens. The SEC alleged that Sun orchestrated wash trading activities on secondary markets for TRX to artificially inflate its valuation. This activity allegedly generated $31 million from numerous TRX trades executed between two accounts demonstrably controlled by Sun. Eight prominent public figures, including Akon, Ne-Yo, Austin Mahone, Soulja Boy, Lindsay Lohan, Jake Paul, and Lil Yachty, were also named for promoting these assets without mandatory sponsorship disclosure; settlement agreements were reached with all listed parties except for Soulja Boy and Mahone.