DexPaprika MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| getNetworksA | REQUIRED FIRST STEP: Get all supported blockchain networks. Always call this first to see available networks before using any network-specific functions. Returns network IDs like "ethereum", "solana", etc. |
| getNetworkDexesA | Get available DEXes on a specific network. First call getNetworks to see valid network IDs. |
| getNetworkPoolsA | PRIMARY POOL FUNCTION: Get top liquidity pools on a specific network. This is the MAIN way to get pool data - there is NO global pools function. Use this instead of any "getTopPools" or "getAllPools" concepts. |
| getDexPoolsA | Get pools from a specific DEX on a network. First use getNetworks, then getNetworkDexes to find valid DEX IDs. |
| getPoolDetailsA | Get detailed information about a specific pool. Requires network ID from getNetworks and a pool address. |
| getTokenDetailsA | Get detailed information about a specific token on a network. First use getNetworks to get valid network IDs. |
| getTokenPoolsB | Get liquidity pools containing a specific token on a network. Great for finding where a token is traded. |
| getPoolOHLCVA | Get historical price data (OHLCV) for a pool - essential for price analysis, backtesting, and visualization. Requires network and pool address. |
| getPoolTransactionsB | Get recent transactions for a specific pool. Shows swaps, adds, removes. Requires network and pool address. |
| searchA | Search across ALL networks for tokens, pools, and DEXes by name, symbol, or address. Good starting point when you don't know the specific network. |
| getStatsB | Get high-level statistics about the DexPaprika ecosystem: total networks, DEXes, pools, and tokens available. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
Each tool has a clearly distinct purpose with no overlap. For example, getNetworkPools retrieves top pools on a network, while getDexPools targets pools from a specific DEX, and getPoolDetails provides detailed information for a single pool. The descriptions explicitly guide usage, preventing confusion.
All tool names follow a consistent verb_noun pattern with 'get' as the prefix (e.g., getNetworks, getPoolDetails, getTokenPools). The naming is uniform and predictable, making it easy for agents to understand the action and target resource.
With 11 tools, the server is well-scoped for its domain of blockchain DEX data analysis. Each tool serves a specific function, from network discovery to pool and token details, without redundancy. The count supports comprehensive coverage without being overwhelming.
The tool set provides complete coverage for exploring DEX data, including network discovery, DEX and pool listings, detailed views, historical data, transactions, and search. There are no obvious gaps; agents can navigate from high-level stats to granular details seamlessly.