pumpdata

fun.pumpdata由 pumpdata.fun 发布官方发布者v0.3.2更新于 Oct 27, 2026

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

已验证Streamable HTTP可网页运行金融数据与分析

概览

AI 生成的概览

面向 pump.fun 的远程 MCP 服务器:查询代币、部署者与钱包,获取基准概率,并用完整交易历史回测选币。

可以做什么
  • 按代码或名称查找代币,并查看某个 mint 的发行记录:部署者历史、创建时的捆绑买入、内部人占比以及相似发行的后续表现
  • 按地址核查钱包,归类为赢家、机器人、抛售者或新钱包,并给出背后的 SOL 数据
  • 按钱包地址查看部署者战绩,包括近 90 天各次发行的结果
  • 获取某一市值区间的基准概率:3 小时内达到 2 倍、5 倍、10 倍、20 倍的比例
  • 找出与某代币同年龄段最相似的发行,以及它们随后 24 小时的表现
  • 用时间戳和仓位回测最多 500 笔选币,并轮询任务获取逐笔与汇总结果
适用场景
适合需要调研 pump.fun 代币、部署者或钱包,或想用历史基准概率和回测来检验交易想法而非凭感觉判断的场景。也适合已经能处理付费 API 调用的加密研究与智能体工作流。
运行要求
远程 streamable HTTP 端点 pumpdata.fun,无需账号或 API 密钥。付费调用通过 x402 以 Solana 主网 USDC 结算:客户端签署 USDC 转账,并带 PAYMENT-SIGNATURE 头重试,通常借助 x402 客户端库和 PUMPDATA_PAYER_KEY 之类的付款密钥。钱包需有 USDC,但不需要 SOL。部分接口和每日基准概率文件免费。
安装前请注意
多数查询按次收费(例如 0.005 至 0.01 美元,回测 2 美元),助手可能在未询问的情况下花费 USDC。付费调用需要用钱包密钥签署 USDC 转账,务必避免把密钥写进代码或提交到仓库。回测任务为排队执行,需要轮询结果。数据仅覆盖 pump.fun,且该服务与 pump.fun 无关联。

安装

在 SourceWeft 中

  1. 打开 控制台中的 pumpdata,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Web executable,通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体,或 SourceWeft 对话中。智能体会读取该服务器的安装指南,先向你展示发布者、端点和登录方式,经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/fun.pumpdata%2Fpumpdata/install.md,并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前,先告诉我它的发布者、端点和登录方式,等我确认。不要把 API 密钥写进命令或我会提交的文件;问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。

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

来源:README.md,提交 204616c

工具

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

输入参数day

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.

输入参数q必填limit

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.

输入参数to必填band必填from必填venuepayment

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.

输入参数mintpaymentaddresses必填

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.

输入参数mint必填payment

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.

输入参数address必填payment

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.

输入参数mint必填limitpayment

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.

输入参数exitpicks必填paymentlatency_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.

输入参数id必填

版本历史

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

评分

已满足适用检查项的 100%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分