Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/nirholas/pumpfun-claims-botWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/nirholas/pumpfun-claims-bot/pumpfun-claims-bot)<a href="https://agentmods.dev/mcp/nirholas/pumpfun-claims-bot/pumpfun-claims-bot"><img src="https://agentmods.dev/badge/mcp/nirholas/pumpfun-claims-bot/pumpfun-claims-bot.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
pumpfun-claims-bot scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 8d ago First seen · 13 lines scan A 3426a77f7536
pumpfun-claims-bot is an MCP server published in the GitHub repository nirholas/pumpfun-claims-bot (20 stars, last pushed today), with no licence file. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other mcp servers, from other repositories
binance-mcp
MCP server for Binance exchange - spot trading, staking, wallet, NFT, pay, mining, and more. Runs locally from the @nirholas/binance-mcp-server npm package. Needs 2 environment variables to run.
openchainbench
Live, neutral benchmarks for public RPC latency, oracles, bridges, perp DEX, and prediction markets. Remote server at openchainbench.com.
coingecko-mcp-server
Crypto market data via CoinGecko — prices, markets, history, trending, and deep coin metadata. Runs locally from the @cyanheads/coingecko-mcp-server npm package. Needs 2 environment variables to run.
pump-fun-sdk
Build extend and maintain pump - Token creation buying selling migration fee collection. Runs locally from the pump-fun-mcp npm package.
transaction-mcp-server
MCP Server for Ethereum transaction building, signing, and serialization. Runs locally from the transaction-mcp-server Python package.
ethereum-wallet-mcp
MCP server for Ethereum wallet generation and HD wallet operations. Runs locally from the ethereum-wallet-mcp Python package.