MCP servers › fun.pumpdata › pumpdata

MCP server · registry snapshot 2026-10-23 · last tested 2026-10-23

fun.pumpdata/pumpdata

Check a pump.fun coin, dev or wallet: deployer record, bundle, PnL. Every pump.fun trade, ever. — the publisher's description

4 of 5 record checks metRead-only · tools listed 2026-10-23Topic: finance-and-payments · AI-classifiedPricing: usage-based · AI-classifiedversion 0.3.2TypeScriptstreamable HTTP9 tools

Summary

fun.pumpdata/pumpdata is a remote MCP server listed in the official MCP registry at version 0.3.2. On 2026-10-23 ProtocolProbe connected to it in read-only mode and read its inventory: 9 tools, 0 resources and 0 prompts.

Record checks

4 of 5 record checks met · 4 do not apply

met: Registry entry is active and says how to run it
met: Source repository link opens
met: Repository is not archived
met: Code pushed to the repository in the 90 days before our check
not met: Repository publishes a security policy (SECURITY.md)
not applicable: Package names its licence with a standard (SPDX) identifier
not applicable: The version the registry lists can be installed and is not withdrawn
not applicable: npm package carries build provenance (attestation)
not applicable: No known critical or high advisory in the package or its dependencies

Not ranked by downloads: a remote server publishes no download figure
Not ranked by stars: 0 stars (ranked from 10)

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Key facts

Runs: remote (hosted by the publisher)
Transport: streamable HTTP
Sign-in: none needed to open a session
Repository: public
Tools: 9
Described as changing data: 1 of 9 toolsAI-classified
Topic: finance-and-paymentsAI-classified
Pricing: usage-basedAI-classified
Last tested: 2026-10-23

Add to your client

Worth knowing before you connect it

1 tool is described as changing something (replay): our AI model's reading of the descriptions, not something we tested, and the server opened a session without any credential. We did not call it.

Each line comes from a section below, with its source and date.

How fresh this is

Live-tested

yes, a real session (not a text-only review)

Last tested

2026-10-23

Mode

read-only (no tool calls)

Latest version

0.3.2, published 2026-10-21 (registry, as of the 2026-10-23 snapshot)

First listed version

2026-10-17 (earliest version still in the registry; older removed versions would be earlier)

Version history

3 versions listed, 2026-10-17 to 2026-10-21; 3 in the 90 days before the 2026-10-23 snapshot.

Most recent 3 versions

0.3.2 · 2026-10-21
0.3.1 · 2026-10-17
0.3.0 · 2026-10-17

(versions still listed in the registry only)

Registry data

snapshot 2026-10-23

Package and repository

checked 2026-10-22

Engine

mcp-runtime-engine@0.1.0 · sdk@1.32.0

Changes since the last refresh

New in the registry: not in the list of 2026-10-04, listed on 2026-10-23 with version 0.3.2 (published 2026-10-21).

Source: the official MCP Registry list on 2026-10-04 and on 2026-10-23.

What it is

What does this server offer?

Observed inventory

9tools

0resources

0prompts

1 of 9 tools are described as changing something (creating, editing, deleting, sending or running).

statson 28 other serversreads or searches
“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 bes…”
1 input
- daystring“a UTC day, YYYY-MM-DD; default the latest”
find_coinreads or searches
“Free.”
2 inputs, 1 required
- qstringrequired“a ticker ($KIMCHI or KIMCHI), a name, or a mint”
- limitinteger“coins to return, newest first; default 20”
base_rateon 1 other serverreads or searches
“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.”
5 inputs, 3 required
- bandstringrequired“market-cap band in USD, e.g.”
- fromstringrequired“window start, ISO 8601 UTC”
- tostringrequired“window 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”
- paymentstring“the x402 PAYMENT-SIGNATURE value for this exact call (USDC on Solana).”
wallet_recordsreads or searches
“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…”
3 inputs, 1 required
- addressesarrayrequired“base58 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).”
launch_recordon 1 other serverreads or searches
“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 la…”
2 inputs, 1 required
- mintstringrequired“the coin's mint address (base58)”
- paymentstring“the x402 PAYMENT-SIGNATURE value for this exact call (USDC on Solana).”
deployer_recordreads or searches
“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…”
2 inputs, 1 required
- addressstringrequired“the deployer's wallet address (base58)”
- paymentstring“the x402 PAYMENT-SIGNATURE value for this exact call (USDC on Solana).”
similar_launchesreads or searches
“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 nea…”
3 inputs, 1 required
- mintstringrequired“the coin's mint address (base58)”
- limitinteger“comparables to return, default 10”
- paymentstring“the x402 PAYMENT-SIGNATURE value for this exact call (USDC on Solana).”
replayon 6 other serversdescribed as changing data
“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 la…”
5 inputs, 1 required
- picksarrayrequired“up to 500 a run for now; split the rest into another run”
- latency_snumber“seconds from the decision to the fill”
- 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”
- paymentstring“the x402 PAYMENT-SIGNATURE value for this exact call (USDC on Solana).”
replay_resultreads or searches
“A replay's result: the job's state, and the replay once done with the execution model it charged.”
1 input, 1 required
- idstringrequired“the id from replay”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-23.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

Says what the tool does: 100% of 9 tools
Says what it returns: 100% of 9 tools
States limits, defaults or errors: 75% of 4 tools
Says when to use it: 100% of 9 tools
Items covered per tool: 3.9 of 4 on average

Counted from the listing

Parameters with a description: 100% of 24
Tools with a description: 100% of 9
Typical description length: 567 characters

The tool set

Counted from the listing

Tools: 9
Size of the list: about 2,458 tokens for an agent to load (characters ÷ 4)
Naming: 7 of 9 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 9 of 9 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-10-23 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai

Settings → Connectors → Add custom connector, then paste:
https://pumpdata.fun/mcp

Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json

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

VS Code · .vscode/mcp.json

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

VS Code (command line) · Bash or zsh terminal (macOS, Linux)

code --add-mcp '{"name":"pumpdata","type":"http","url":"https://pumpdata.fun/mcp"}'

Claude Code

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

Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+

npx @modelcontextprotocol/inspector@2.11.0 --server-url https://pumpdata.fun/mcp --transport http

The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Does the registry listing match what we found?

Feature #6

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.

Registry says	We found	Result	Source · date
Remote endpoint pumpdata.fun/mcp	Session opened	matches	our test · 2026-10-23
No credential declared as required	Opened a session without any credential	matches	our test · 2026-10-23
Repository github.com/pumpdatafun/pumpdata-examples	Opens publicly	matches	api.github.com · 2026-10-22

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace: fun.pumpdata
GitHub owner: an organization (pumpdatafun)

Repository: github.com/pumpdatafun/pumpdata-examples
Stars: 0
Repository age: 0–30 days
Last push: 0–30 days ago
Archived: no
Security policy: none found (we looked for SECURITY.md in the repository and in its owner’s .github repository)

Source: the registry entry and api.github.com · 2026-10-22; security policy read from GitHub · 2026-10-23.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

4 of 5 record checks met · 4 do not apply

Not ranked by downloads: a remote server publishes no download figure
Not ranked by stars: 0 stars (ranked from 10)

MetRegistry entry is active and says how to run itActive, with a package or a remote address.
MetSource repository link opensThe linked GitHub repository is public.
MetRepository is not archivedNot archived.
MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
Not metRepository publishes a security policy (SECURITY.md)No SECURITY.md in the places GitHub reads it from.
Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-22. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards

Common questions about fun.pumpdata/pumpdata

Answered from the data above

Is fun.pumpdata/pumpdata safe to install?

We do not rate servers as safe or unsafe. 4 of its 5 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. 1 of its tools describes changing data (our AI model's reading of the descriptions). These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Is fun.pumpdata/pumpdata free to use?

Its website (pumpdata.fun/) describes a usage-based pricing model. This is an AI-classified reading of the page on 2026-10-23, so check the page itself before relying on it.

Does fun.pumpdata/pumpdata need an API key or sign-in?

It opened a session without any credential on 2026-10-23. The registry entry declares no required credential; no declaration is not a guarantee.

Has fun.pumpdata/pumpdata been security tested?

Partly. 2 of the 14 checks that apply to it were exercised. We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes. This is our choice, not a block by the server. No security verdict is published before verification.

What can fun.pumpdata/pumpdata do?

It lists 9 tools. In our AI model's reading of their descriptions (two runs had to agree, nobody checked it by hand), they include tools that read or search. We did not call any tool, so this describes the text, not the behaviour.

Can fun.pumpdata/pumpdata change or delete data?

1 of its tools says in its description that it creates, edits, deletes, sends or runs something (our AI model's reading). We did not call any tool, so we cannot say what actually happens.

Does fun.pumpdata/pumpdata publish a security policy?

We found no SECURITY.md in its repository (root, .github/ or docs/) or in its owner's .github repository.

Where is the source code of fun.pumpdata/pumpdata?

In github.com/pumpdatafun/pumpdata-examples, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Similar servers

Same topic · AI-read

io.github.vybenetwork/solana-mcp-vybeSolana MCP by Vybealso has tools that reads or searchescompare with this one
io.github.mnemox-ai/tradememory-protocolalso has tools that reads or searchescompare with this one
io.github.YichengYang-Ethan/oracle3Oracle3 prediction-market arbitrage checksalso has tools that reads or searchescompare with this one
io.github.agent-next/polymarket-paper-traderPolymarket Paper Traderalso has tools that reads or searchescompare with this one
io.github.openaccountants/openaccountantsOpenAccountantsalso has tools that reads or searchescompare with this one
io.github.koreal6803/finlab-aialso has tools that reads or searchescompare with this one

Active servers whose topic is also “finance-and-payments” and that have at least one tool of the same kind; most kinds in common first, then most GitHub stars. The topic and the tool kinds are an AI model's reading of the publishers' descriptions, not checked by hand. Similar is not a recommendation.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Not probed (we call no server's tools)

We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes. This is our choice, not a block by the server. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-10-23

Inventory: exercised
Hidden instructions: exercised
Real execution: not run · our policy
Secret leak: not run · nothing to check it against
Internal addresses: not run · our policy
Unconfirmed changes: not run · our policy
Bad input: not run · our policy
Model requests: not run · nothing to check it against
Sensitive questions: not run · nothing to check it against
Folder boundary: not run · our policy
Log leaks: not run · nothing to check it against
Hidden content: not run · nothing to check it against
Fake assistant turns: not applicable
Token passthrough: not applicable
Token audience: not applicable
Sign-in redirect: not run · our policy
Consent handling: not testable from outside
Sign-in metadata: not applicable

2 exercised12 not run (reason given)4 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 2 of the 14 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 2

1Inventory
tool-listReads the declared tools, resources and prompts.exercised
2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised

Not run, with the reason · 12

3Real execution
real-executionCalls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
8Model requests
samplingChecks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
11Log leaks
logging-side-channelChecks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
12Hidden content
audience-hidingChecks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against
16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
17Consent handling
confused-deputyChecks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside

Does not apply to this server · 4

13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable
18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.No sign-in (OAuth) metadata is published, so there are no sign-in addresses to check.not applicable

Source: our own test, 2026-10-23, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

0 msStarted a read-only session with the server's remote endpoint
229 msConnected after 0 redirects. No credential was sent or needed.
Read the inventory: 9 tools, 0 resources, 0 prompts.
994 msFinished: 2 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified

finance-and-payments

AI-classified · 2026-10-23

Pricing modelAI-classified

usage-based

read from pumpdata.fun/ · 2026-10-23

“Ask by the call: free to start (put /free in front: 300 lookups a day, no key), then half a cent a call, no account.”

Programming language

TypeScript

api.github.com · 2026-10-23

Hosting type

remote (hosted by the publisher)

registry · 2026-10-23

MCP capability

tools

our test · 2026-10-23

Transport

streamable HTTP

registry · 2026-10-23

Required credentials

none declared

registry · no declaration is not a guarantee

Package registry

does not apply

remote-only server: no package is shipped, so there is no package registry

Freshness

0–30 days

registry updatedAt · 2026-10-23

Lifecycle status

active

registry · 2026-10-23

License class

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Integrity hash

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Signature / provenance

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Dependency advisories

does not apply

ships no package, so there are no dependencies to audit

Popularity

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Publisher signals

owner: an organization · repository age: 0–30 days · stars: 0–9

api.github.com · 2026-10-22

Maintenance

active

api.github.com · 2026-10-22

Environment

the publisher's infrastructure

where it runs, from the hosting type

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “fun.pumpdata/pumpdata: MCP server record.” Data checked 2026-10-23. https://protocolprobe.com/mcp/servers/fun.pumpdata/pumpdata

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/fun.pumpdata/pumpdata)](https://protocolprobe.com/mcp/servers/fun.pumpdata/pumpdata)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology