Skip to main content
Glama
pumpfun-claims-bot

pumpfun-claims-bot

by nirholas

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_token_infoB

Fetch PumpFun token metadata, market cap, bonding curve progress, and flags

get_token_holdersB

Fetch top holders for a PumpFun token including concentration metrics

get_token_tradesB

Fetch recent trade activity for a PumpFun token (volume, buy/sell counts)

get_pool_liquidityB

Fetch PumpSwap AMM pool liquidity for a graduated token

get_bundle_infoC

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

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.5/5.0

Scored across 9 tools

Disambiguation4/5

Most tools target distinct resources or actions: token metadata, holders, trades, liquidity, bundle detection, creator profile, GitHub profile, claim history, and SOL price. There is minor conceptual overlap between get_token_info flags and get_bundle_info, and between creator/GitHub profile lookups, but the boundaries are clear enough for selection.

Naming Consistency5/5

All tools use the same get_ + snake_case noun phrase convention. Names are predictable and consistently structured across the entire set.

Tool Count5/5

Nine tools is well-scoped for a PumpFun claims/analytics server, with each tool covering a distinct data retrieval need. No obvious redundancy or excessive surface area.

Completeness3/5

The surface covers token analytics, creator/GitHub identity, claim history, and SOL pricing, but despite the server being a claims bot there is no tool to actually submit or manage a claim. This is a notable lifecycle gap if claim execution is in scope.

Maintenance

ActivityActive
ResponsivenessNo recent community issues