DexScreener 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 |
|---|---|
| get_latest_token_profilesC | Get the latest token profiles |
| get_latest_boosted_tokensC | Get the latest boosted tokens |
| get_top_boosted_tokensB | Get tokens with most active boosts |
| get_token_ordersC | Check orders paid for a specific token |
| get_pairs_by_chain_and_addressC | Get one or multiple pairs by chain and pair address |
| get_pairs_by_token_addressesC | Get one or multiple pairs by token address (max 30) |
| search_pairsC | Search for pairs matching query |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| DexScreener API Documentation | Documentation for the DexScreener API endpoints and usage |
| Memecoin Trading Best Practices | Guidelines and best practices for memecoin trading and analysis |
TDQS
Scored across 7 tools
Most tools have distinct purposes, with clear separation between boosted tokens, token profiles, pairs retrieval, token orders, and pair search. However, get_latest_boosted_tokens and get_top_boosted_tokens could potentially cause some confusion regarding whether they serve overlapping or complementary functions, as both relate to boosted tokens with slightly different focuses.
All tool names follow a consistent verb_noun pattern with underscores, using descriptive and predictable naming conventions. The structure is uniform across all seven tools, making it easy for agents to understand and predict tool purposes based on their names.
With 7 tools, the server is well-scoped for its purpose of providing DexScreener data access. Each tool appears to serve a specific and necessary function without redundancy, covering key operations like retrieving tokens, pairs, orders, and searches in a focused manner.
The tool set covers essential operations for accessing DexScreener data, including token and pair retrieval, orders, and search. A minor gap exists in the lack of update or management tools, but this is reasonable for a read-only data access server, and agents can work effectively with the provided query-focused tools.