memecoin-radar-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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_trending_tokens_by_sourceA | Retrieve top traded tokens on specified source platform in the last 12 hours. |
| get_pumpfun_graduates_by_marketcapA | Retrieve Pump.fun token launches sorted by highest market capitalization in the last 24 hours. |
| get_pumpfun_graduates_by_trading_volumeA | Retrieve Pump.fun token launches sorted by highest trading volume in the last 24 hours. |
| get_recent_pumpfun_graduatesA | Retrieve the most recently graduated tokens from Pump.fun in the last 24 hours. |
| get_recent_kol_buysA | Retrieve recent token purchases by memecoin Key Opinion Leaders (KOLs). |
| get_trending_tokens_by_kol_trading_volumeA | Retrieve tokens with the highest trading volume by memecoin KOLs. |
| get_trending_tokens_on_raydiumA | Retrieve tokens with the highest trading volume on Raydium within a specified time span. |
| get_trending_tokens_on_pumpswapA | Retrieve tokens with the highest trading volume on PumpSwap within a specified time span. |
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 8 tools
The tools have clear distinctions in their primary focus (Pump.fun graduates, KOL activity, trending tokens by source/platform), but there is some overlap in purpose. For example, get_pumpfun_graduates_by_marketcap and get_pumpfun_graduates_by_trading_volume both retrieve Pump.fun graduates with different sorting criteria, which could cause confusion if an agent needs general graduate data without a specific sorting preference. The descriptions help clarify, but the boundaries between tools like get_trending_tokens_by_kol_trading_volume and get_recent_kol_buys are somewhat fuzzy, as both relate to KOL activity.
All tool names follow a consistent verb_noun pattern with 'get_' prefix, using snake_case throughout. The naming is predictable and clear, such as get_pumpfun_graduates_by_marketcap and get_trending_tokens_on_raydium, making it easy for agents to understand the action and target resource without confusion.
With 8 tools, the count is reasonable for a memecoin tracking server, covering multiple aspects like graduates, KOL activity, and trending tokens across platforms. It's slightly on the higher side but well-scoped, as each tool serves a distinct query type. However, it might feel a bit heavy for a narrow domain, but not excessively so.
The tool set provides good coverage for retrieving data on memecoin trends, graduates, and KOL activity, but there are notable gaps. It lacks tools for creating, updating, or deleting data (e.g., no way to add custom alerts or track specific tokens), which limits it to read-only operations. While this might be intentional for a radar server, the surface feels incomplete for full lifecycle management or interactive features beyond basic queries.