ShrineAPI

Historical data & MCP

Ask your AI
about any coin or wallet.

The Data MCP lets Claude, Cursor or any MCP client query our historical database: every trade and wallet, with pump.fun's bonding curve back to March 2025 and live trades up to the last few seconds. Try it here: the examples run the real tools on the live database, 3 free answers a day, no key needed.

Archive and candle history on every plan. The replay from Lite, the Data MCP on Developer and Professional.

01What you can ask

Ask in plain words. It answers from the data.

The agent picks a tool, or writes SQL for the questions no tool answers on its own, and can chain several calls: find the coins, then their traders, then those traders' other wallets.

“Which wallets made the most on this coin, and are they still holding?”top_traders
“What did this wallet make this month, per coin?”wallet_pnl
“What share of volume did each front-end have this week?”query
“Show me this coin's 5-minute candles since launch and who bought in the first minute.”token_candles
“Who funded this wallet, how old is it, and which other wallets got their first SOL from the same funder?”query
“Find the most traded coins called "pepe".”search_tokens
“Who created this coin, what else have they launched, and how did those do?”query
“Which coins does it still hold, at what cost, and what are they worth now?”wallet_positions
“Go through my wallet's trades last week and show where I sold too early.”wallet_trades
More questions to ask

02Three ways in

Ask it, replay it, or download it.

The same history without an AI client too: recent candles to start a chart, a replay after a disconnect, and every past hour as a file.

Developer and Professional

Data MCP

Your AI agent queries our historical database: every trade and wallet, with pump.fun's bonding curve back to March 2025 and live trades up to the last few seconds.

  • Top traders, holders, candles, a wallet's PnL and positions
  • Read-only SQL for anything the tools do not cover
  • Any stretch streamed back in time order, for a backtest
  • 60 queries a minute on Developer, 120 on Professional
Data MCP docs

Every plan, replay from Lite

Candle history and replay

For your own code: recent candles to seed a chart, and what you missed after a disconnect.

  • Up to 500 of a pool's most recent 1-second candles in one call
  • The live candle stream's format, no key needed once a minute
  • Reconnect the Advanced Data Stream with sinceSlot: everything since that slot comes first, from any slot of the last 24 hours
Replay and resume

Free, no key

Hourly archive

Every hour of the Advanced Data Stream as a file, so code written for the socket runs on it.

  • One file per UTC hour, zstd-compressed JSON lines
  • Each line the live event plus localTimestamp
  • A few hundred megabytes an hour, compressed
  • Apart from a few venues the stream sends live only
Historical replay

03Connect

Add one URL. Then ask.

The Data MCP is a Model Context Protocol server, the standard way AI apps plug into tools and data. Give your client the URL and your Developer or Professional key, as Authorization: Bearer, or on the URL when a client cannot set headers.

One command. Then ask: the agent sees the tools, picks the right one and reads the answer.

claude mcp add --transport http shrine-data https://mcp.shrine.trade/mcp \
  --header "Authorization: Bearer sk_…"

In Settings, Connectors, Add custom connector: name it shrine-data and paste the URL with your key.

https://mcp.shrine.trade/mcp?key=sk_…

~/.cursor/mcp.json

{
  "mcpServers": {
    "shrine-data": {
      "url": "https://mcp.shrine.trade/mcp",
      "headers": { "Authorization": "Bearer sk_…" }
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "shrine-data": {
      "type": "http",
      "url": "https://mcp.shrine.trade/mcp",
      "headers": { "Authorization": "Bearer sk_…" }
    }
  }
}

~/.codex/config.toml, with your key in an environment variable.

[mcp_servers.shrine-data]
url = "https://mcp.shrine.trade/mcp"
bearer_token_env_var = "SHRINE_API_KEY"

# then, in your shell
export SHRINE_API_KEY=sk_…

It is plain JSON-RPC over HTTP, so a script can call a tool directly. The answer's text is JSON: columns, rows, row_count, and what the query read.

curl -s https://mcp.shrine.trade/mcp \
  -H "Authorization: Bearer sk_…" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call",
       "params":{"name":"top_traders",
                 "arguments":{"mint":"Gc6r…pump","limit":5}}}'

04The database

The data behind the Shrine terminal.

Every trade with its wallet, side, amounts, price and front-end; flags for dev buys, bundles, snipers and first buys; the realized profit of every sell; every wallet's positions and daily PnL; who funded each wallet; launches by creator; candles; and live balances and holders.

3.2B+trades, back to March 2025
13tools your agent picks from, on Developer
60a minutequeries on Developer, 120 on Professional
3a dayfree answers on this page, no key needed

05Plans

Free to download. The MCP on Developer.

The hourly archive and candle history need no key. The 24-hour replay comes with Lite and up. The Data MCP comes with Developer, and with Professional at twice Developer's limits.

FreeLiteDeveloperProfessional
Hourly archive✓✓✓✓
Candle history1 a minute1 a second5 a second15 a second
Live candles1 token, 1 socket, free key from the dashboardevery token, 3 socketsevery token, 10 socketsevery token, 15 sockets
24-hour replay–1 socket3 sockets5 sockets
Data MCP for AI agents––60 queries a minute, 1 stream120 queries a minute, 1 stream

The Data MCP's time and row limits per query are in its docs. Every other limit is in Plans and limits. Prices are on the pricing page.

06FAQ

Questions, answered.

Anything else is in the docs.

How far back does the history go?

The Data MCP's history starts on 14 March 2025. Its oldest stretch holds pump.fun's bonding curve only, decoded from the Solana ledger. After it comes every launchpad trade, curve and pool, with candles and wallet PnL. Ask the data_coverage tool which days it holds and what each stretch covers.

Can I use the Data MCP without an AI client?

Yes. It is plain JSON-RPC over HTTP, so a script can call a tool directly with your key in the Authorization header. The answer's text is JSON: columns, rows, row_count, and what the query read. The same key streams the history back in time order, over a WebSocket or as JSON lines over HTTP.

Can the Data MCP trade or touch my wallet?

No. Every tool and every SQL statement is read-only. There is nothing to trade, sign, send or change, and no wallet, private key or account of yours is anywhere near it.

How do I get older candles?

ohlcv_history returns up to the 500 most recent 1-second candles of a pool. For anything older, the hourly archive holds every trade, and the Data MCP's token_candles tool answers at 1m, 5m, 15m, 30m, 1h, 4h or 1d.

What is in the hourly archive?

The events the Advanced Data Stream pushes, apart from a few venues it sends live only: one file per UTC hour, zstd-compressed JSON lines, each line the live event plus localTimestamp, the millisecond our server saw the transaction. An hour is a few hundred megabytes compressed. It is free and needs no key.

The hourly archive is free. The Data MCP comes with Developer and Professional.