Skip to content
Pump Data logo

Pump Data MCP server

Which MCP servers are Pump Data's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-28

← Back to Pump Data

Whose server it is
  • Registry namefun.pumpdata/pumpdataverified in the MCP registry

The registry name sits under pumpdata.fun. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-28
  • Stateanswerschecked 2026-10-28
  • Tools12
  • Server calls itselfpumpdata.fun
  • Server version1
  • Protocol version2025-06-18

On 2026-10-28 the server answered initialize and tools/list without a sign-in. First answer in 75 ms.

Should an agent connect itNot proven either way yet
  • Whether its tools do the product's job has not been judged yet.
  • Checked on 6 of the 7 days it takes to judge reliability.

Once connected

  • For "trace a deployer's past launches and how they ended", the likely first call is deployer_record.
  • Keep approval on for send_feedback: they delete, send or pay without saying so.
  • send_feedback change data without a sign-in: anyone with the address can call them.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 6, the first on 2026-10-28
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 6 so far
  • Answeredmeasuring6 of the 7 daily checks it takes to print a share
  • Median first answer213 ms
  • Space in an agent's context≈ 3,579 tokensthe definitions of all its tools (13), which an agent carries on every turn
  • Tool definitionsA · 99 of 100
  • Typed results0 of 13 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a description: in 1 of 13

What an agent can do with it

  • not sure · check which wallets are buying into a coin before purchase
  • can do · trace a deployer's past launches and how they ended
  • not sure · compare a new coin's early trades with similar coins

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

  • Tools that delete, send or pay, marked as not destructive: send_feedback
  • Tools that change data, on a server that answers without a sign-in: send_feedback

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers12 tools · read 2026-10-28
  • stats

    Pump.fun stats for one UTC day, free: coins launched and graduated, the graduation rate, SOL and USD volume, traders; the top coins by peak market cap and by volume; the deployers whose coins did best, with their record; the instant and…

  • find_coin

    Free. The pump.fun coins a ticker or name means, newest first, so a coin named in a chat can be looked up by its mint: for each, the mint (the contract address, CA), its name and ticker, when it was created, its deployer with their…

  • check_coin

    Free. The pre-buy check of one pump.fun coin by its mint (contract address, CA), in one call: the findings as sentences (answer), short flags with a sentence each (serial_launcher, never_ran, curve_bought_at_launch, early_concentration…

  • launches_since

    Free. Every pump.fun launch after a moment in the last 24 hours, oldest first: each with its deployer's record before it (launches, graduations, seconds since its last launch) and the first-10-second bundle; launches newer than the hourly…

  • top_wallets

    Free. The pump.fun wallet leaderboard: wallets that win over their whole record (took out 10+ SOL and 1% more than they put in over 20+ coin-weeks) and traded in the last ~20 days, best first, each with why, its SOL in and out, its coins…

  • base_rate

    The odds for pump.fun coins in a market-cap band: how many first traded inside the band in a window, how many of those then reached 2x, 5x, 10x and 20x within 3 h, and the median peak. For: the base rate, what are the odds a $20K coin…

  • wallet_records

    Check pump.fun wallets by address: what each has been since day one, its class by rule (winner: took out 10+ SOL and 1% more than it put in over 20+ coin-weeks; net_loser: put in 50+ SOL more than it took out; bot: a sniper (20+ coins…

  • launch_record

    Check a pump.fun coin by its mint (the contract address, CA): who launched it and the deployer's record at the launch (launches before it, graduations, the gap to the previous one, launches in the last day), the bundle at creation (buyers…

  • deployer_record

    A pump.fun dev's record by wallet address, no coin needed: launches, graduations, best run, the gap between launches; over the last 90 days how many of its launches doubled, did 10x, held at 2x a day later or died; its newest launches…

  • similar_launches

    The pump.fun launches most like this coin at the same age, named by mint, and how each went over its next 24 h (peak, close, dead or graduated): the same deployer's prior launches first, then the nearest of the last 90 days by the…

  • replay

    Backtest pump.fun picks: picks with timestamps and sizes in; what they made, pick by pick and in sum, every pick counted, the dead ones included, filled at the PumpSwap pool as it stood after your latency (graduates only; bonding-curve…

  • replay_result

    A replay's result: the job's state, and the replay once done with the execution model it charged. Free; the id is the receipt.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "pumpdata": {
      "type": "http",
      "url": "https://pumpdata.fun/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http pumpdata https://pumpdata.fun/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://pumpdata.fun/mcp as a custom connector in the settings.

OpenAPI spec

30 paths, read 2026-10-28. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.