Skip to content

pumpdata MCP server

fun.pumpdata/pumpdatapumpdata.funstreamable-httpv0.3.2Scanned

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

24 tools: 2 do something that can't be undone, 21 change things and 1 only read.

Tools: 0 delete, 2 irreversible, 21 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 2
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here do something that can't be undone. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the pumpdata MCP server can do

The pumpdata MCP server is published by pumpdata.fun, a domain the MCP Registry verified. It has 24 tools. It can do things that cannot be undone, such as sending, paying or publishing (base_rate and send_feedback) and create or change data (21 tools: stats, trending, whale_trades, graduations and 17 more), but cannot delete data. 1 tool only reads.

2 tools can send data out of your system (base_rate and send_feedback).

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.

Last scanned Nov 8, 2026, version 0.3.2.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

24 tools

Can't be undone 2Claude Code: ask
  • base_rateThe 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 p…Can send data out1 finding

    Why it is in this group

    • The input addresses people (input.to): what it sends cannot be taken back.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • outboundThe input takes a destination (input.to): what the tool writes goes there.

    Findings

    • Warn

      The server marks "base_rate" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The input addresses people (input.to): what it sends cannot be taken back.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • send_feedbackFree.Can send data outNo findings

    Why it is in this group

    • The name "send_feedback" says "send": a word for sending, and what is sent cannot be taken back.

    What it can reach

    • outboundThe name "send_feedback" says "send": it sends or publishes something to other people.
    Description, as the server wrote it
    Free. Tell the people who run pumpdata.fun what you were trying to do and what was wrong or missing: a coin or wallet with no record, a field you needed, an answer that looked wrong, a call that failed. Plain text, up to 2,000 characters; code, markup and anything that looks like a key are removed. Read by people; nothing comes back but a receipt. Never put secrets or private keys in it.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
Changes things 21Claude Code: ask
  • check_coinFree.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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, deployer_sells_fast, never_ran, curve_bought_at_launch, early_concentration, 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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • coin_holdersFree.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Free. A pump.fun coin's 20 biggest wallet holders now, read from the chain, each with its share of the supply (the bonding curve and pool vaults left out), whether many of them hold the very same amount (one bag split across wallets) and how much programs hold. count true adds the holder count. For: who holds this coin, top holders, is the supply concentrated. Then wallet_records on the holders.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • coin_priceFree.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Free. The market cap and price now of up to 50 pump.fun coins, from each coin's last trade on its bonding curve or its own PumpSwap pool (within 10 seconds for coins traded in the last 12 hours, else the hourly fill), in SOL and USD. For: what is this coin's market cap, price of these coins, is it still trading.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • deployer_recordA 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 10…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • graduationsFree.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Free. The pump.fun coins whose bonding curve completed (graduated): the last hour as they land (from since), or a whole UTC day of the last three with day. Each with the seconds from its launch (same_second: bought whole in its launch second) and, for a day, the deployer's record before it. For: what just graduated on pump.fun, how many graduated today, which coins graduated in the same second. Then check_coin on a mint.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • launch_recordCheck 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,…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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 one or two wallets bought the whole curve as it launched (bundle_at_creation.top_buyer and top_buyer_share say whether one wallet took it) (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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • launches_sinceFree.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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 fill come within the minute (source live, bundle not yet read). For: what launched just now, new coins from devs with a record, watch new launches. Poll with t = next_since; call check_coin only for the coins worth a look.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • live_eventsFree.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Free. The last hour's pump.fun events as they land, oldest first: launches (with the deployer, the first 10 seconds' buys as a share of the supply, and the deployer's own buys and sells so far), graduations, migrations to PumpSwap, and dev sells (the wallet that launched a coin selling it, with the share of its bag sold). For: did the dev sell, which devs are dumping right now, what just launched or migrated. Poll with since = next_since.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • odds_by_market_capFree.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Free. Yesterday's odds for a pump.fun coin at each market cap: for every band ($5k-10k up to $250k-1M), how many coins first traded inside it, and what share went on to 2x, 5x, 10x and 20x within three hours, with the median peak. Dead coins count. For: what are the odds a pump.fun coin at $20k does a 2x, how often coins at a market cap run. A coin's own odds depend on its deployer and early buyers: check_coin. Any window: base_rate (paid).

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • replayBacktest 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 …No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • replay_resultA replay's result: the job's state, and the replay once done with the execution model it charged.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • similar_launchesThe 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 …No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • statsPump.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 …No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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).

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • ticker_crowdFree.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Free. One ticker's crowd (Nov 3): most pump.fun launches reuse a ticker (88.3% in October 2026), so before buying a coin, see every coin with its ticker. Its launches over the last three days by UTC day, each day's first launch and the coins that graduated (with how long after the first they launched), how many launched in the last two hours, its launches and deployers over 14 days, and every coin with the ticker that ever graduated, the first and the biggest named. For: how many $KIMCHI launched today, did the first one or a later one run, is this a rerun.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • today_liveFree.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Free. Pump.fun today so far (UTC), counted from the chain as trades land: launches, graduations, migrations, trades, SOL and USD volume, distinct traders and coins traded, large trades, dev sells, and the graduation rate; yesterday's beside it. For: how many coins launched on pump.fun today, pump.fun volume today, how many graduated so far. For a whole settled day, use stats.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • top_walletsFree.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Free. The pump.fun wallet leaderboard, ranked by each wallet's own profit. (Oct 31: the follower ranking, sort copyable, is withdrawn until it is rebuilt at PumpSwap's real fees; at them, copying the best-scored wallets 1 slot behind lost money in all seven weeks tested.) The wallets 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, 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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • wallet_recordsCheck 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 5…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • wallet_tradesFree.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Free. Up to 50 wallets' pump.fun trades (bonding curve and PumpSwap) in the last 3 hours, every size unless min_sol, oldest first: coin, side, SOL, venue, time. For: what has this wallet traded today, follow these wallets, did this wallet sell. A record, not a signal; wallet_records says what each wallet has been since day one.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • whale_tradesFree.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Free. Every pump.fun buy and sell of $2,500 or more (min_usd from $1,000) in the last hour, oldest first, read from the chain as trades land: each with the wallet, the coin (name, symbol, mint), side, SOL, USD and the market cap at the trade. Give a wallet for that wallet's large trades only. For: what are whales buying on pump.fun, big buys right now, did this wallet buy or sell. A record of what wallets did, not a signal; then check_coin on a mint, wallet_records on a wallet.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • who_fundedFree.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Free. Who funded a Solana wallet (a pump.fun dev, a buyer, any address): who sent it its first SOL, who funded that wallet, up to five hops back, each with the amount, the time and the transaction; where the walk stopped (a wallet with more than 5,000 transactions, the mark of an exchange, a service or a bot, ends it); and which other walked wallets got their first SOL from the same address. For: who is behind this dev, where did this wallet's money come from, are these wallets funded by the same address. Read from the chain; facts, no verdict.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 1Show 1 read-only tool
  • find_coinFree.No findings

    Why it is in this group

    • The name "find_coin" says "find": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out2
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:54 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
29
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 29 tools that change things (1 destructive, 2 irreversible, 26 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://pumpdata.fun/mcp: tools/list returned 30 tools to an anonymous client, including send_tx (destructive), base_rate (irreversible), send_feedback (irreversible), stats (write), trending (write) and 24 more

    What this check looks for

Posture changes

  1. Nov 20, 2026
    • Tools that change things, listed without credentials: 27 to 29
  2. Nov 13, 2026
    • Tools that change things, listed without credentials: 22 to 27
  3. Nov 6, 2026
    • Tools that change things, listed without credentials: 11 to 22
  4. Oct 29, 2026
    • Tools that change things, listed without credentials: 8 to 11

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "base_rate" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The input addresses people (input.to): what it sends cannot be taken back.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Tools that change things, listed without credentials: 27 -> 29.View diff
    • Tools that change things, listed without credentials: 27 to 29
  2. PostureRemote posture changed. Tools that change things, listed without credentials: 22 -> 27.View diff
    • Tools that change things, listed without credentials: 22 to 27
  3. Tools15 added, 9 changed.+15 added~9 changedView diff
  4. PostureRemote posture changed. Tools that change things, listed without credentials: 11 -> 22.View diff
    • Tools that change things, listed without credentials: 11 to 22
  5. PostureRemote posture changed. Tools that change things, listed without credentials: 8 -> 11.View diff
    • Tools that change things, listed without credentials: 8 to 11
  6. Tools1 added, 7 changed.+1 added~7 changedView diff

Install

Pinned to version 0.3.2. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__pumpdata__find_coin"
    ],
    "ask": [
      "mcp__pumpdata__stats",
      "mcp__pumpdata__trending",
      "mcp__pumpdata__whale_trades",
      "mcp__pumpdata__graduations",
      "mcp__pumpdata__odds_by_market_cap",
      "mcp__pumpdata__ticker_crowd",
      "mcp__pumpdata__check_coin",
      "mcp__pumpdata__launches_since",
      "mcp__pumpdata__live_events",
      "mcp__pumpdata__today_live",
      "mcp__pumpdata__coin_price",
      "mcp__pumpdata__wallet_trades",
      "mcp__pumpdata__coin_holders",
      "mcp__pumpdata__top_wallets",
      "mcp__pumpdata__who_funded",
      "mcp__pumpdata__base_rate",
      "mcp__pumpdata__wallet_records",
      "mcp__pumpdata__launch_record",
      "mcp__pumpdata__deployer_record",
      "mcp__pumpdata__similar_launches",
      "mcp__pumpdata__replay",
      "mcp__pumpdata__replay_result",
      "mcp__pumpdata__send_feedback"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as pumpdata. Review it before you use it.

Capability tags behind 2 rules
  • mcp__pumpdata__base_rate outbound
  • mcp__pumpdata__send_feedback outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/fun.pumpdata/pumpdata/verify?hash=78686ca809f09c2f05a0634f25ecb5c38dabcfb7f725a51df745ce5be2c5c7d3" | jq -e '.changed == false'

Pinned hash 78686ca809f0, from Nov 8, 2026, 11:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/fun.pumpdata/pumpdata/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for fun.pumpdata/pumpdata
[![Anlyon Radar](https://radar.anlyon.com/badge/fun.pumpdata/pumpdata.svg)](https://radar.anlyon.com/servers/fun.pumpdata/pumpdata)

Source: MCP Registry · repository. Synced Oct 21, 2026, 23:17 UTC.

pumpdata MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the pumpdata MCP server safe?

No scan can promise that. What its definitions show: 24 tools, 23 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the pumpdata MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the pumpdata MCP server do things that cannot be undone?

Yes. 2 tools can send, pay, publish or merge: base_rate and send_feedback.

What tools does the pumpdata MCP server have?

24 tools: 2 irreversible, 21 write, 1 read. base_rate, send_feedback, stats, trending, whale_trades, graduations, odds_by_market_cap, ticker_crowd and 16 more.

Does the pumpdata MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the pumpdata MCP server send data to outside services?

2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): base_rate and send_feedback.

Has the pumpdata MCP server changed its tools?

Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 8, 2026. Every change is on this page and in its Atom feed.