dexscreener-mcp
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_pairsA | Search DexScreener for trading pairs by token name, symbol, or contract address across all chains. Returns price, 24h change, volume, liquidity, and FDV. |
| get_token_poolsA | Get all liquidity pools (pairs) for a specific token on a given chain. |
| get_tokensA | Get pair/market data for one or more token addresses on a chain (comma-separated, up to 30). |
| get_pairA | Get details for a specific pair by chain id and pair (pool) address. |
| latest_token_profilesA | Get the latest token profiles freshly listed/updated on DexScreener (new tokens to watch). |
| top_boosted_tokensA | Get the currently top-boosted (most promoted / trending) tokens on DexScreener. |
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 6 tools
Most tools target distinct data retrieval patterns: search, address lookups, pair details, and discovery lists. However, search_pairs and get_tokens both return pair data, which could cause confusion when an agent has a contract address.
Predominantly verb_noun (search_pairs, get_token_pools, get_tokens, get_pair), but latest_token_profiles and top_boosted_tokens deviate from the verb pattern, making the set slightly inconsistent.
Six tools cover the core DexScreener functionality without redundancy; the count is appropriate for a focused data provider.
The set covers search, direct address lookups, pair details, and discovery features. Missing historical/OHLC data but that's beyond the typical scope for first-level data access.