PumpPill MCP server

Read-only token intelligence for Robinhood Chain (chainId 4663) and Solana, served as a hosted Model Context Protocol server.

https://api.pumppill.org/mcp

Streamable HTTP. No key, no account, nothing to install. Registry name: org.pumppill/token-safety (v1.2.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

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.

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.

Related MCP server: NoesisAPI

Tools

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

Member tools (5 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, never an error.

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.

Stdio-only clients

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.

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"}}}'

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 members: 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.

• 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.

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. 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.