# pumpdata (remote · pumpdata.fun)

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

- Trust score: 61/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-18

## Components

- remote · `pumpdata.fun`: 61/100 (this document), [markdown](https://verifymcp.io/servers/fun-pumpdata-pumpdata/pumpdata.md), [page](https://verifymcp.io/servers/fun-pumpdata-pumpdata/pumpdata)

## Channel facts

- Endpoint: `https://pumpdata.fun/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.3.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-18.

- **Endpoint Security**: 60/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 56/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

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

### Claude

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

### Cursor

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

### VS Code

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

### Codex

```toml
[mcp_servers.fun-pumpdata-pumpdata]
url = "https://pumpdata.fun/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "fun-pumpdata-pumpdata": {
      "type": "remote",
      "url": "https://pumpdata.fun/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add fun-pumpdata-pumpdata --url 'https://pumpdata.fun/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  fun-pumpdata-pumpdata:
    url: "https://pumpdata.fun/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "fun-pumpdata-pumpdata": {
      "Transport": "http",
      "Url": "https://pumpdata.fun/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add fun-pumpdata-pumpdata -t streamable-http -u 'https://pumpdata.fun/mcp'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-18 (score 61, +1)

- [security] 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
- [functional regression] Schema quality: 1187 → 1558
- [functional improvement] Stability: unverified → 0.03
- [functional] New tool “similar_launches”
- [functional] New tool “stats”

### 2026-10-17 (score 60)

First indexed and scored.

## MCP tools (7)

### `stats` (~146 tokens)

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

Input parameters:

- `day` (string): a UTC day, YYYY-MM-DD; default the latest

### `base_rate` (~329 tokens)

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.

Input parameters:

- `band` (string, required): market-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
- `from` (string, required): window start, ISO 8601 UTC
- `payment` (string): 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…
- `to` (string, required): window end; a crossing needs its 3 h after, so an end under 3 h before the data's as-of is cut
- `venue` (string): default any

### `wallet_records` (~234 tokens)

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.

Input parameters:

- `addresses` (array, required): base58 wallet addresses
- `mint` (string): optional: the coin they are buying; a wallet with no record before its creation is 'new'
- `payment` (string): 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…

### `launch_record` (~191 tokens)

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.

Input parameters:

- `mint` (string, required): the coin's mint address (base58)
- `payment` (string): 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…

### `similar_launches` (~206 tokens)

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.

Input parameters:

- `limit` (integer): comparables to return, default 10
- `mint` (string, required): the coin's mint address (base58)
- `payment` (string): 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…

### `replay` (~305 tokens)

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.

Input parameters:

- `bankroll_sol` (number): SOL at risk at once; a pick with no room is skipped
- `exit` (object): take (x the entry), trail (share off the high), hold_s (seconds); any combination
- `latency_s` (number): seconds from the decision to the fill
- `payment` (string): 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…
- `picks` (array, required): up to 500 a run for now; split the rest into another run

### `replay_result` (~49 tokens)

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.

Input parameters:

- `id` (string, required): the id from replay

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/fun-pumpdata-pumpdata/pumpdata#diagnostics

## Score history

- 2026-10-18: 61
- 2026-10-17: 60

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

## Links

- Remote endpoint: https://pumpdata.fun/mcp
- Repository: https://github.com/pumpdatafun/pumpdata-examples
- Website: https://pumpdata.fun/
- Changelog RSS feed: https://verifymcp.io/servers/fun-pumpdata-pumpdata/pumpdata.xml
- Changelog JSON feed: https://verifymcp.io/servers/fun-pumpdata-pumpdata/pumpdata.json
- HTML version of this page: https://verifymcp.io/servers/fun-pumpdata-pumpdata/pumpdata