PumpFun Claims Bot
NPM · PUMPFUN-CLAIMS-BOT · SCANNED SEP 20
MCP server for PumpFun on-chain intelligence — tokens, claims, holders, and bundles.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security89
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects uuid 8.3.2, reached via @solana/web3.js > jayson > uuid. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 53 of 156 dependencies flagged as unhealthy (2 deprecated). View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 7 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 339 tokens (~37/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the PumpFun Claims Bot MCP server?
PumpFun Claims Bot runs locally as an npm package, launched with npx -y pumpfun-claims-bot. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · pumpfun-claims-bot
claude mcp add nirholas-pumpfun-claims-bot -- npx -y pumpfun-claims-bot
{
"mcpServers": {
"nirholas-pumpfun-claims-bot": {
"command": "npx",
"args": [
"-y",
"pumpfun-claims-bot"
]
}
}
} {
"servers": {
"nirholas-pumpfun-claims-bot": {
"command": "npx",
"args": [
"-y",
"pumpfun-claims-bot"
]
}
}
} codex mcp add nirholas-pumpfun-claims-bot -- npx -y pumpfun-claims-bot
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"nirholas-pumpfun-claims-bot": {
"type": "local",
"command": [
"npx",
"-y",
"pumpfun-claims-bot"
],
"enabled": true
}
}
} openclaw mcp add nirholas-pumpfun-claims-bot --command npx --arg -y --arg pumpfun-claims-bot
mcp_servers:
nirholas-pumpfun-claims-bot:
command: "npx"
args: ["-y", "pumpfun-claims-bot"] {
"McpServers": {
"nirholas-pumpfun-claims-bot": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"pumpfun-claims-bot"
]
}
}
} assistant mcp add nirholas-pumpfun-claims-bot -t stdio -c npx -a -y pumpfun-claims-bot
{
"mcpServers": {
"nirholas-pumpfun-claims-bot": {
"command": "npx",
"args": [
"-y",
"pumpfun-claims-bot"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 −3
- Stability: pass → 0.80 functional
- 19 Sept 26 +1
- Stability: 0.97 → pass security
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 −3
- Stability: pass → 0.77 functional
- 11 Sept 26 +1
- Stability: 0.97 → pass security
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed npm/pumpfun-claims-bot@1.0.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 2 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-528h-pc64-c93x | CVE-2026-71429 | medium | CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-w5hq-g745-h8pq | CVE-2026-41907 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 156 packages
| Packages resolved | 156 |
|---|---|
| Deprecated | 2 |
| Stale | 51 |
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_bundle_info ~31
Detect if a token launch was bundled (scam indicator)
| Name | Type | Req | Description |
|---|---|---|---|
| mint | string | yes | Token mint address |
No output schema declared.
No examples provided.
get_claim_history ~49
Check claim history for a GitHub user — whether they have claimed, claim count, and which token mints they claimed from
| Name | Type | Req | Description |
|---|---|---|---|
| githubUserId | string | yes | GitHub numeric user ID |
No output schema declared.
No examples provided.
get_creator_profile ~36
Fetch PumpFun creator profile — username, launch count, scam estimate, recent coins
| Name | Type | Req | Description |
|---|---|---|---|
| wallet | string | yes | Creator wallet address |
No output schema declared.
No examples provided.
get_github_user ~55
Fetch GitHub user profile by username or numeric ID — repos, followers, bio, account age
| Name | Type | Req | Description |
|---|---|---|---|
| userId | string | – | GitHub numeric user ID |
| username | string | – | GitHub username (login) |
No output schema declared.
No examples provided.
get_pool_liquidity ~49
Fetch PumpSwap AMM pool liquidity for a graduated token
| Name | Type | Req | Description |
|---|---|---|---|
| mint | string | yes | Token mint address |
| usdMarketCap | number | – | Current USD market cap (for context) |
No output schema declared.
No examples provided.
get_sol_price ~15
Fetch current SOL/USD price
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_token_holders ~32
Fetch top holders for a PumpFun token including concentration metrics
| Name | Type | Req | Description |
|---|---|---|---|
| mint | string | yes | Token mint address |
No output schema declared.
No examples provided.
get_token_info ~35
Fetch PumpFun token metadata, market cap, bonding curve progress, and flags
| Name | Type | Req | Description |
|---|---|---|---|
| mint | string | yes | Token mint address |
No output schema declared.
No examples provided.
get_token_trades ~37
Fetch recent trade activity for a PumpFun token (volume, buy/sell counts)
| Name | Type | Req | Description |
|---|---|---|---|
| mint | string | yes | Token mint address |
No output schema declared.
No examples provided.
What is the PumpFun Claims Bot MCP server?
PumpFun Claims Bot is an MCP server listed in the public MCP registry as io.github.nirholas/pumpfun-claims-bot. MCP server for PumpFun on-chain intelligence, tokens, claims, holders, and bundles. This page covers its npm package (pumpfun-claims-bot).
Is the PumpFun Claims Bot MCP server safe to use?
PumpFun Claims Bot scores 78 out of 100 on VerifyMCP. We recorded 2 known advisories against it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the PumpFun Claims Bot MCP server expose?
PumpFun Claims Bot exposes 9 tools: get_token_info, get_token_holders, get_token_trades, get_pool_liquidity, get_bundle_info, and 4 more. Their descriptions and schemas cost roughly 339 tokens of context every time the server is loaded.
Is the PumpFun Claims Bot MCP server still maintained?
PumpFun Claims Bot is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the PumpFun Claims Bot MCP server under?
PumpFun Claims Bot declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.