MCP.Market

pumpdata MCP server

online · 100% uptime
by pumpdata.fun·fun.pumpdata/pumpdata·v0.3.2
No reviews yet

Check a pump.fun coin, dev or wallet: deployer record, bundle, PnL. Every pump.fun trade, ever.

A91/100grade A
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
A91/100

full report

Adoption
Growing

0 stars

Reviews

Write one

Nobody has reviewed pumpdata yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

pumpdata tools (11)

write = sends, deletes, buys or posts
  • base_rateFree

    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 does 10x, how often does it happen anyway. A crossing is a coin's first trade with a market cap inside the band (a coin that jumps over the band in one trade has none); the peak is the highest market cap, curve or pool, in the 3 h after it; USD is at the SOL price of the trade's hour. $0.005 a call, USDC on Solana over x402, or a free key.

  • check_coinFree

    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, bundled, insiders, lookalikes_die), rules_say (skip, or no flags: your call) and the launch record behind them: the deployer's record, the bundle at creation, the insiders' share, who holds most, how launches like it went. For: check this coin, is this a rug, should I buy this, is this coin bundled. Facts, no verdict.

  • deployer_recordFree

    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; and the base rate for its next launch from deployers with the same record. For: this dev's history, a serial deployer, has this creator rugged before, the deployer's track record. Facts, no score. $0.005 a call, USDC on Solana over x402, or a free key.

  • find_coinFree

    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 launches and graduations, whether it graduated, its market cap at five minutes and its first-day peak. For: what is $KIMCHI's CA, which Kimchi is the real one, find this coin by name, the mint for this ticker. Covers every coin that completed its bonding curve (about 300K); a coin still on its curve is not here yet. A mint given as q returns that coin's name. Then launch_record on the mint.

  • launch_recordFree

    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 in the first 10 s and the share of supply they took), the insiders' share now, whether one or two wallets bought the whole curve as it launched (curve_bought_at_launch, with the share they still hold), curve progress, the market cap now and the real SOL behind it (sol_reserve_now), its holder count, its 20 biggest wallets now (top_holders), the 20 that made the most SOL on it with their classes (top_traders, coins launched since the tables' build), and how launches that looked the same at this age went over their next 24 h (graduation share, peak and close quantiles, how many died). For: check this coin, a rug check, is this coin bundled, who holds it, who made money on it, who deployed this token, is this dev legit. Facts, no verdict. $0.005 a call, USDC on Solana over x402, or a free key.

  • replayFree

    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 picks, and picks outside the archive, are counted in skipped_not_covered until curve fills ship), with every fee, the fixed costs and the bankroll you set. For: backtest my calls, would this strategy have made money, replay these picks with real fills. The most recent eight weeks come back apart from the rest, once per rule to each payer. A run is a queued job: the result is {id, state: queued}; poll replay_result with the id. $2 a run, USDC on Solana over x402; a run that fails is rerun free on the same id.

  • replay_resultFree

    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.

  • similar_launchesFree

    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 deployer's record, the first-10 s buyers, the insiders' share and curve progress, each saying why it is similar. For: coins like this one, what happened to launches like this, comparables. Not a prediction: what launches that looked like this did next. $0.005 a call, USDC on Solana over x402, or a free key.

  • statsFree

    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 fastest graduations; launches and the 1 h graduation rate per UTC hour; launches dead by their second hour. For: pump.fun today or yesterday, how many coins launched, how many graduated, the biggest coin of the day. `checks` lists any number that failed a sanity check: never quote one. `summary` is one paragraph to quote. Each coin and deployer names the paid call that goes deeper (launch_record, deployer_record).

  • top_walletsFree

    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 and its recent pace (trades a day, median hold). followable: true keeps the ones a copier can keep up with (under 20 trades a day, a median hold of 2 minutes or more, under half its trades fast). For: who should I copy trade, the best pump.fun traders, smart money wallets. Not pump.fun's own leaderboard, which ranks recent profit. Then wallet_records for any wallet's full record.

  • wallet_recordsFree

    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 bought in their create block, half or more of its new coins) or 1,500+ trades a day; supply_seller: took out 1.5x what it put in, 100 SOL or more; new: no record before the mint you name, or before today; none: no rule fits, usually too young for them), why (the rule it met, with its numbers) and the numbers behind it: pnl_sol, put_in, took_out, coins, first_seen, recent (its pace). For: who is buying this coin, is this wallet a bot, a wallet's PnL, a holder check on the top buyers. Up to 50 addresses a call. $0.01 a call, USDC on Solana over x402, or a free key.

Public scan report

scanner v0.1.10 · 2026-10-25 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 522ms20/20
  • Tool poisoning11 tool descriptions checked15/15
  • Auth qualityopen endpoint, read-only tools10/15
  • Maintenancelast push 8 days ago15/15
  • Maintainer identityendpoint served from the registry-verified namespace domain8/10
Overall 91/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How pumpdata compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
91/100
higher than 85% of 48,255 servers
Tools
11
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
206 ms
faster than 63% of 30,031 servers

What its tools let an agent do: 10 read · 1 run or deploy

Install pumpdata in Claude Code, Cursor or VS Code

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

What the publisher says

From the pumpdata repository's README, as published. We do not edit it. Read it on GitHub

pumpdata examples

Calling pumpdata.fun from an agent or a script: every pump.fun trade, ever, bonding curve and PumpSwap, since pump.fun's first day, read from the chain's ledger with the dead coins kept, sold by the call in USDC over x402 on Solana. No key, no account.

Free, no payment: yesterday's base rate for every band at /public/baserate.json, refreshed hourly.

Contract: /openapi.json. Docs for agents: /llms.txt. A skill: /skill.md.

How a call is paid

  1. Call without payment. The answer is 402 with the offer in the body and in the PAYMENT-REQUIRED header: price, payee, network (USDC on Solana mainnet), and a Bazaar declaration of the inputs.
  2. Sign a USDC transfer for that amount with your wallet (the facilitator pays the network fee; you need no SOL).
  3. Call again with the signed payment in PAYMENT-SIGNATURE. The answer is the data, with the receipt in PAYMENT-RESPONSE.

The x402 client libraries do steps 2 and 3 for you. Every answer carries X-Data-As-Of (the build it comes from) and X-Data-From (where the data begins). A window with no data answers 404 and costs nothing.

The examples

  • curl.sh: the 402 and the free file, no wallet needed.
  • node.mjs: a paid call with @x402/fetch and a Solana keypair.
  • python.py: the 402 and the free file from Python; the paid retry with the x402 package.
  • mcp.md: the same calls as MCP tools (Claude Code, Cursor, Cline, Claude Desktop).

Check the base rate before you ape: agent recipes

A paid GET /baserate ($0.005) in four shapes, each 17-21 lines. The payer key comes from PUMPDATAPAYERKEY (base58, or the solana-keygen JSON array). The wallet needs USDC and no SOL. Never commit the key.

npm install
export PUMPDATA_PAYER_KEY='<secret key>'
npm run fetch        # yesterday's (UTC) $15-28K base rate, any venue
npm run typecheck

The three framework files reuse baseRate() from x402-fetch.ts. Run on their own, they call the action or tool directly, the way the framework would, so no model or agent is needed to try them.

Not affiliated with pump.fun.

Nothing above is checked by us. What we check is on the safety report.

pumpdata: common questions

Is pumpdata MCP server safe?
Yes, by our scan: it is graded A (91/100). Read the pumpdata safety report
How do I install pumpdata?
It runs remotely at pumpdata.fun. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does pumpdata need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is pumpdata maintained?
The last commit was 17 days ago (2026-10-17). The latest release is v0.3.2.
Is pumpdata up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does pumpdata compare with other MCP servers?
safety score 91/100 (higher than 85% of 48,255 servers); tools 11 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.