Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

pumpdata

REMOTE · PUMPDATA.FUN

pump.fun history for trading agents: base rates, wallet and launch records, replay. Paid per call.

Available components

61 Trust /100

Last scanned (5 hours ago)

Scores higher than 45% of remote servers

Reachable. Last reached 18 Oct 2026.

Category Crypto and Web3

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security60
Transport & Reachability100
Schema Quality & AI Usability56
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1558 tokens (~222/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
  • Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 18 Oct 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “replay” rewrote its description, which is the text the model reads security
    • Tool “wallet_records” rewrote its description, which is the text the model reads security
    • Schema quality: 1187 → 1558 ▼ functional
    • Stability: unverified → 0.03 ▲ functional
    • New tool “similar_launches” functional
    • New tool “stats” functional
  • 17 Oct 26 60

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 18 Oct 2026 · Probed https://pumpdata.fun/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=pumpdata.fun CN=WE1,O=Google Trust Services,C=US 15 Oct 2026 13 Jan 2027 ECDSA 256 ECDSA-SHA256 6352f62209ac1f5a13d8641d72b193f8
SANs: pumpdata.fun, www.pumpdata.fun, *.www.pumpdata.fun
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of pumpdata.fun. — Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
fun. present 47728 13 Verified
pumpdata.fun. present 2371 13 Verified
pumpdata.fun. Verified address RRset verified with the apex keys
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://pumpdata.fun/mcp Verified 200
http (plaintext) http://pumpdata.fun/mcp HTTPS enforced 301 https://pumpdata.fun/mcp
MCP tools · 7 exposed · ~1,460 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
base_rate ~329

How often it happens anyway. How many coins first traded inside a market-cap band in a window, how many of those then reached 2x, 5x, 10x and 20x within 3 h, and the median peak. 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.

NameTypeReqDescription
bandstringyesmarket-cap band in USD, e.g. 15k-28k; each edge snaps to the nearest of 5k, 10k, 15k, 20k, 28k, 40k, 60k, 100k, 250k, 1000k, and the answer says the band used
fromstringyeswindow start, ISO 8601 UTC
paymentstring–the x402 PAYMENT-SIGNATURE value for this exact call (USDC on Solana). Leave it out to get the offer: the price, the payee and the network come back as the error content and as _meta['payment-require…
tostringyeswindow end; a crossing needs its 3 h after, so an end under 3 h before the data's as-of is cut
venuestring–default any

No output schema declared.

No examples provided.

launch_record ~191

This launch, historically. The deployer's record at this 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). $0.005 a call, USDC on Solana over x402.

NameTypeReqDescription
mintstringyesthe coin's mint address (base58)
paymentstring–the x402 PAYMENT-SIGNATURE value for this exact call (USDC on Solana). Leave it out to get the offer: the price, the payee and the network come back as the error content and as _meta['payment-require…

No output schema declared.

No examples provided.

replay ~305

Your picks, replayed honestly. 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. 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.

NameTypeReqDescription
bankroll_solnumber–SOL at risk at once; a pick with no room is skipped
exitobject–take (x the entry), trail (share off the high), hold_s (seconds); any combination
latency_snumber–seconds from the decision to the fill
paymentstring–the x402 PAYMENT-SIGNATURE value for this exact call (USDC on Solana). Leave it out to get the offer: the price, the payee and the network come back as the error content and as _meta['payment-require…
picksarrayyesup to 500 a run for now; split the rest into another run

No output schema declared.

No examples provided.

replay_result ~49

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.

NameTypeReqDescription
idstringyesthe id from replay

No output schema declared.

No examples provided.

similar_launches ~206

The launches most like this one at the same age, named with their mints, 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. Not a prediction: what launches that looked like this did next. $0.005 a call, USDC on Solana over x402.

NameTypeReqDescription
limitinteger–comparables to return, default 10
mintstringyesthe coin's mint address (base58)
paymentstring–the x402 PAYMENT-SIGNATURE value for this exact call (USDC on Solana). Leave it out to get the offer: the price, the payee and the network come back as the error content and as _meta['payment-require…

No output schema declared.

No examples provided.

stats ~146

Free. Yesterday on pump.fun (one UTC day), or any day kept: coins launched and graduated, SOL and USD volume, traders, failed transactions; who made money (top 10 wallets by net SOL, the 5 biggest losers, the share of traders down); the top coins by volume, the fastest graduations, the biggest launches; launches and the 1 h graduation rate per UTC hour; launches dead by their second hour; the busiest deployers. `summary` is one paragraph to quote. Each wallet and coin names the paid call that goes deeper (wallet_records, launch_record).

NameTypeReqDescription
daystring–a UTC day, YYYY-MM-DD; default the latest

No output schema declared.

No examples provided.

wallet_records ~234

What these wallets have been since day one: for each address its class by rule (winner: took out more than it put in over 20+ coin-weeks; bot: a coin traded 20+ times in a week or 500+ coins; 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. Up to 50 addresses a call. $0.01 a call, USDC on Solana over x402.

NameTypeReqDescription
addressesarrayyesbase58 wallet addresses
mintstring–optional: the coin they are buying; a wallet with no record before its creation is 'new'
paymentstring–the x402 PAYMENT-SIGNATURE value for this exact call (USDC on Solana). Leave it out to get the offer: the price, the payee and the network come back as the error content and as _meta['payment-require…

No output schema declared.

No examples provided.

Install

How do I install the pumpdata MCP server?

pumpdata is a hosted endpoint at https://pumpdata.fun/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · pumpdata.fun

# add to Claude Code
claude mcp add --transport http fun-pumpdata-pumpdata 'https://pumpdata.fun/mcp'
Common questions

What is the pumpdata MCP server?

pumpdata is an MCP server listed in the public MCP registry as fun.pumpdata/pumpdata. pump.fun history for trading agents: base rates, wallet and launch records, replay. Paid per call. This page covers its hosted endpoint (https://pumpdata.fun/mcp).

Is the pumpdata MCP server safe to use?

pumpdata scores 61 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the pumpdata MCP server expose?

pumpdata exposes 7 tools: stats, base_rate, wallet_records, launch_record, similar_launches, and 2 more. Their descriptions and schemas cost roughly 1,460 tokens of context every time the server is loaded.

Does the pumpdata MCP server require authentication?

No. We connected to pumpdata without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the pumpdata MCP server still maintained?

pumpdata is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.