PumpPill — token safety and measured outcomes

PumpPill MCP server

Token intelligence for Robinhood Chain (chainId 4663) and Solana, and agentic trading on Robinhood Chain, served as a hosted Model Context Protocol server.

https://api.pumppill.org/mcp

Streamable HTTP. No key, no account, nothing to install for the read tools. Registry name: org.pumppill/token-safety (v1.6.0). How-to page: https://www.pumppill.org/for-agents

This repository holds the connection instructions, example client configs and the registry manifest. The server itself is hosted by PumpPill; its source is not published here.

What it answers

For trading bots, one call before a buy: pre_trade_check answers clear, caution, avoid or unknown for a Robinhood Chain contract or a Solana mint, with the reasons. The same answer is plain HTTP at GET https://api.pumppill.org/api/pretrade/{address}, free and without a key.

The questions that cost people money: can this contract be sold, which contract is the real one behind a ticker, what has this deployer launched before, which wallets hold enough to move a pool, and what happened to the tokens PumpPill logged, with the losers counted.

And the chain as it happens: what launched in the last hours with its market now, one token's 24 hour buys and sells with the developer's launch record and the wallet that funded the developer, the token's trade tape, PumpPill's Ignition momentum calls with the 28-day record of their exit rule (losers included), and the themes spreading through new launch names on Robinhood Chain and Solana. Wallets come as prefixes.

And what traders are doing: which tokens traders on the FOMO app are gathering on, with PumpPill's own risk read beside each one, and the calls PumpPill's room posted with how each has done since, losers included. whats_moving returns both, plus the newest flags, in one call.

Every result carries a cite string and a timestamp for when the read was taken. A token PumpPill has not read comes back as found: false, which means "not in the index", never "safe". Nothing here predicts a price or recommends a trade. Answers about a token carry a trade_link that opens it in PumpPill's Telegram trade bot; it is a place to trade, present on every token alike, not a pick.

And, with an agent key from the trade bot, your agent can trade: it checks a rule you built on pumppill.org/customize and buys new matches from your PumpPill trade bot wallet. PumpPill reads each token before any buy and refuses a red flag, your limits apply, and every order lands in your Telegram with an off switch. See Agentic trading.

Tools

Public (29 tools, read-only, no key)

Member tools (4 tools)

These answer a PumpPill member. They are listed for everyone; called without a membership they answer with what sits behind them and a link. Three of them can also be bought one call at a time with x402 (see Pay per call).

30 tools in all: 22 public, 4 for members (3 of those payable per call), 4 for agentic trading.

Agentic trading (4 tools, agent key)

A member's AI agent buys and sells Robinhood Chain tokens from their PumpPill trade bot wallet. The key (ppa_…) is made in @PumpPill_Trade_Bot under Settings, AI agent, and sent as the header X-Agent-Key. Open to everyone for 30 days from the first key, then part of PumpPill Premium. Full guide: https://www.pumppill.org/learn/agentic-trading-set-up-your-ai-agent

Every order, placed or refused, is a Telegram message to the member with a one-tap "Turn agent off". The agent never sees the wallet's private key.

Resource and prompts

• pumppill://facts — the quotable fact sheet: what the index covers, headline figures, how to cite them and what they do not mean.
• check_before_buying(address) — the full read on one contract, with the limits stated.
• real_contract_for_ticker(symbol) — which of the contracts using a name is the one that matters.

Connect

Claude Code

claude mcp add --transport http pumppill https://api.pumppill.org/mcp

Claude on the web or desktop (Pro, Max, Team, Enterprise)

Settings → Connectors → Add custom connector. Name it PumpPill, paste https://api.pumppill.org/mcp, and leave the OAuth fields empty. The public tools then work in any chat. The member tools need a header that claude.ai cannot send, so use an editor client for those.

A Claude Desktop build without custom connectors can bridge over stdio instead; see examples/claude_desktop_config.json.

Cursor

One click: Add to Cursor (GitHub may not open cursor:// links; the same link is on /for-agents). Or by hand, in ~/.cursor/mcp.json:

{
  "mcpServers": {
    "pumppill": { "url": "https://api.pumppill.org/mcp" }
  }
}

The same block works in Windsurf, Cline and other clients that take a remote MCP server.

VS Code

One click: Add to VS Code · VS Code Insiders. Or by hand, in .vscode/mcp.json (VS Code names the transport):

{
  "servers": {
    "pumppill": { "type": "http", "url": "https://api.pumppill.org/mcp" }
  }
}

ChatGPT

Add it as a connector with the same URL. search and fetch are the tools ChatGPT calls. ChatGPT cannot send a custom header, so it cannot use the member tools or trade.

OpenAI Agents SDK

from agents import Agent
from agents.mcp import MCPServerStreamableHttp

async with MCPServerStreamableHttp(params={"url": "https://api.pumppill.org/mcp"}) as pumppill:
    agent = Agent(name="RH reader", mcp_servers=[pumppill])

See examples/openai-agents.py.

Stdio-only clients and agent frameworks (ElizaOS and others)

npx -y mcp-remote https://api.pumppill.org/mcp

Member tools

A member sends their sign-in token as a header:

Authorization: Bearer <claim>

The whole connect line can be copied from the member's page at https://www.pumppill.org/premium. In Cursor that is a "headers" object beside the URL; see examples/cursor-mcp-member.json. Treat the claim like a password: keep it in a header, never in a URL, and never commit it.

Agentic trading

Send the agent key as a header. Claude Code:

claude mcp add --transport http pumppill https://api.pumppill.org/mcp --header "X-Agent-Key: ppa_your_key"

Cursor, Windsurf, Cline: see examples/cursor-mcp-agent.json. Then paste the instructions the AI agent card on https://www.pumppill.org/customize writes. Buying on its own needs an agent that runs on a schedule; a chat window only acts while you talk to it.

Check the connection

curl -sX POST https://api.pumppill.org/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"curl","version":"0"}}}'

Pay per call (x402)

No membership? An agent with a wallet can buy a single answer from three of the member tools, paid in USDC on Base through x402:

1. Call the tool. Without a membership or a payment, it answers with an x402 payment request: the price, the network (Base), the asset (USDC) and where to pay.
2. An x402 client signs a USDC authorization and repeats the same call with the payment in _meta["x402/payment"].
3. The answer carries the settlement receipt in _meta["x402/payment-response"].

A payment is collected only when the tool returns a real answer: a miss, an error or a refused read costs nothing. One payment buys one call of one tool. my_watched_wallets stays members only. Clients without x402 support (Claude and ChatGPT today) show the request as an error that names both ways in.

Limits

• Public tools spend nothing. They answer from stored reads and never trigger a live scan. A token PumpPill has not read yet is queued for reading, and is usually available a few minutes later.
• Two tools spend, and only for a member or a caller who paid for that call: rh_scan_now and x_chatter. Both are annotated as not read-only and not idempotent so a client asks before calling them.
• Rate limits: 240 requests a minute per address and 60 a minute per client, then HTTP 429.
• Two tools move money, the member's own and only with their agent key: agent_buy and agent_sell. Both are annotated destructive and not idempotent. Limits are the member's own.
• Coverage: answers cover what PumpPill has scanned, not every contract on either chain.

How to read the answers

• Quote cite and the as-of timestamp. Figures are recomputed continuously, and a number without its time goes stale within the hour.
• A flag is a finding with evidence, not a verdict. It says what is structurally true about a contract, not what the price will do.
• An outcome figure is a count, not a success rate for anyone who bought. Entry is the market cap at the moment PumpPill logged the token, which is not a price anyone was offered.
• found: false is an honest miss. Say so rather than filling the gap.
• FOMO figures count traders on one app whose feed shows large trades only. Say "FOMO traders", not "buyers", and never quote a trade size: none is known.
• trade_link opens the token in PumpPill's Telegram trade bot. Offer it when someone asks how to buy or sell. A flagged token carries one too, so it is never a recommendation.

Privacy

The server records one line per tool call: the tool name, whether it succeeded, how long it took, whether a membership header was present (yes or no), and the name the client declares for itself. It does not record the membership token or who is asking. A paid call also keeps the payment record needed to settle it (tool, price, and the paying wallet named in the signed authorization). Member tools send the token to PumpPill only to check the membership. Full policy: https://www.pumppill.org/privacy

Terms

Research, not advice. Nothing returned by this server is financial advice, an offer, or a recommendation to buy or sell anything, and a clean read is evidence, not an endorsement. Quote it with attribution and a link to the page the result cites. Terms of use: https://www.pumppill.org/terms · citation terms: https://www.pumppill.org/for-agents#terms

Links

• Website: https://www.pumppill.org
• For agents: https://www.pumppill.org/for-agents
• The MCP server, explained: https://www.pumppill.org/blog/pumppill-mcp-server-token-safety-for-ai-assistants
• Contact: pumppillai@gmail.com

License

The contents of this repository (documentation, example configs, manifest) are MIT licensed; see LICENSE. The hosted service and the PumpPill name and logo are not covered by it.