pumpfun-claims-bot
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 |
|---|---|
| get_token_infoA | Fetch PumpFun token metadata, market cap, bonding curve progress, and flags |
| get_token_holdersA | Fetch top holders for a PumpFun token including concentration metrics |
| get_token_tradesA | Fetch recent trade activity for a PumpFun token (volume, buy/sell counts) |
| get_pool_liquidityA | Fetch PumpSwap AMM pool liquidity for a graduated token |
| get_bundle_infoB | Detect if a token launch was bundled (scam indicator) |
| get_creator_profileA | Fetch PumpFun creator profile — username, launch count, scam estimate, recent coins |
| get_github_userB | Fetch GitHub user profile by username or numeric ID — repos, followers, bio, account age |
| get_claim_historyA | Check claim history for a GitHub user — whether they have claimed, claim count, and which token mints they claimed from |
| get_sol_priceA | Fetch current SOL/USD price |
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 9 tools
Each tool targets a distinct data resource: token info, holders, trades, liquidity, bundle status, creator profile, GitHub user, claim history, and SOL price. There is no meaningful overlap or ambiguity between tool purposes.
All tools follow a consistent get_<noun> pattern with snake_case, making the read-only nature and target resource immediately clear. No mixed conventions or vague verb variations exist.
Nine tools is a well-scoped size for a claims-verification bot. Each tool covers a distinct piece of the investigation workflow without unnecessary redundancy or bloat.
The toolkit covers token intelligence, holder analysis, liquidity, scam signals, creator background, GitHub identity, claim history, and SOL pricing—strong coverage for pre-claim due diligence. However, there is no active claim or eligibility-check action, which leaves a minor gap if the bot is expected to execute claims directly.