pumpdata

fun.pumpdataPublished by pumpdata.funOfficial publisherv0.3.2Updated Oct 27, 2026

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

VerifiedStreamable HTTPWeb executableFinanceData & Analytics

Overview

AI-generated overview

Remote MCP server for pump.fun data: look up coins, deployers and wallets, get base rates, and backtest picks against full trade history.

What you can do
  • Look up coins by ticker or name and get a mint's launch record: deployer history, creation bundle, insider share and how similar launches fared
  • Check wallets by address and classify them as winner, bot, supply seller or new, with the SOL behind it
  • Get a deployer's record by wallet address, including launch outcomes over the last 90 days
  • Get base rates for coins in a market-cap band: how many reached 2x, 5x, 10x or 20x within 3 hours
  • Find launches most similar to a given coin at the same age and how each went over the next 24 hours
  • Replay and backtest up to 500 picks with timestamps and sizes, then poll the job for per-pick and total results
When to use it
Useful when an assistant needs to research pump.fun coins, deployers or wallets, or to sanity-check a trading idea against historical base rates and backtests instead of guessing. Suited to crypto research and agent workflows that already handle paid API calls.
Requirements
Remote streamable HTTP endpoint at pumpdata.fun; no account or API key. Paid calls are settled in USDC on Solana mainnet via x402: the client signs a USDC transfer and retries with a PAYMENT-SIGNATURE header, typically using an x402 client library and a payer key such as PUMPDATA_PAYER_KEY. The wallet needs USDC but no SOL. Some endpoints and a daily base-rate file are free.
Before you install
Most lookups cost money per call (for example $0.005 to $0.01, and $2 for a replay), so an assistant can spend USDC without asking. Paid calls require signing a USDC transfer with a wallet key; keep that key out of code and repositories. Replay jobs are queued and must be polled. Data covers pump.fun only and the service is not affiliated with pump.fun.

Installation

In SourceWeft

  1. Open pumpdata in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/fun.pumpdata%2Fpumpdata/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

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

README

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.

callasksprice
GET /baserate?band=15k-28k&from=<iso>&to=<iso>&venue=anyhow many coins first traded inside a market-cap band in a window, and how many reached 2x, 5x, 10x, 20x within 3 h$0.005
POST /wallets {"addresses": [...], "mint": "<optional>"}what up to 50 wallets have been: winner, bot, supply seller, new, with the SOL behind it$0.01
GET /launch/{mint}the deployer's record, the bundle at creation, the insiders' share, and how launches that looked the same went over 24 h$0.005
POST /replay {"picks": [{"mint", "at", "size_sol"}, ...]}up to 500 picks replayed against the chain's history with fees and fills (a queued job; poll GET /replay/{id})$2

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 PUMPDATA_PAYER_KEY (base58, or the solana-keygen JSON array). The wallet needs USDC and no SOL. Never commit the key.

filewhatrun
x402-fetch.tsplain fetch with the official client, @x402/fetch + @x402/svmnpm run fetch
elizaos-action.tsElizaOS (@elizaos/core 1.x): a pumpdata plugin with a PUMPDATA_BASE_RATE actionnpm run eliza
solana-agent-kit-tool.tssolana-agent-kit v2: an Action in a plugin, run through executeActionnpm run agent-kit
vercel-ai-tool.tsVercel AI SDK (ai v7): a tool() for generateText / streamTextnpm run ai-sdk
npm installexport PUMPDATA_PAYER_KEY='<secret key>'npm run fetch        # yesterday's (UTC) $15-28K base rate, any venuenpm 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.

Source: README.md at commit 204616c

Tools

9

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

Parametersday

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

Parametersqrequiredlimit

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

Parameterstorequiredbandrequiredfromrequiredvenuepayment

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 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) and the numbers behind it: pnl_sol, put_in, took_out, coins, first_seen. 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.

Parametersmintpaymentaddressesrequired

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 in the first 10 s and the share of supply they took), the insiders' share now, curve progress, 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 deployed this token, is this dev legit. Facts, no verdict. $0.005 a call, USDC on Solana over x402, or a free key.

Parametersmintrequiredpayment

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

Parametersaddressrequiredpayment

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

Parametersmintrequiredlimitpayment

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

Parametersexitpicksrequiredpaymentlatency_sbankroll_sol

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.

Parametersidrequired

Version history

3
  1. v0.3.2LatestOct 21, 2026
  2. v0.3.1Oct 17, 2026
  3. v0.3.0Oct 17, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts