Polymarket and Predict.fun historical tick data, plus backtest quotes and status, over MCP
Nothing to run from here
Groundtruth is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
15
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Dev records, pump.fun + Robinhood Chain: launches, rugs, bonded, live last mint. Every figure has N.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http groundtruth-mcp https://api.groundtruths.xyz/mcp
# 2 — ask your agent for something these tools do
# groundtruth_scan_coin, groundtruth_screen_creator, groundtruth_screen_batch and 12 more
Groundtruth costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
GRAll 1 server
groundtruths1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http groundtruth-mcp https://api.groundtruths.xyz/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
15 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
What the KOL wallet launched, and how it ended. Rugged of resolved, seconds to the pull, every count with its N. One call. When the dev is on a KOL list, envelope.kol carries tag KOL / TOP PROFIT, the lists, yes-no flags and rank (never a name). Look up one token and return what GROUNDTRUTH counted about it: the outcome label (rugged, died, graduated, survived, or no outcome), liquidity and market
| Parameter | Type | Required | Notes |
|---|---|---|---|
| address | string | yes | A Solana mint (base58) or a Robinhood Chain contract address (0x...). Example: So11111111111111111111111111111111111111112 |
Given one creator address, return every wallet that was early in that creator's launches: the role each played (creator, repeat_buyer, one_off), how many of this creator's launches it was early in versus how many it was early in anywhere, and the creator's own rug rate against the chain baseline, because a rate without its baseline is not a finding. It does not say who owns the wallets. LIVE FIELD
| Parameter | Type | Required | Notes |
|---|---|---|---|
| creator | string | yes | Creator address. base58 for Solana, 0x... for Robinhood Chain. |
| chain | string | no | Which chain the creator launched on. |
| role | string | no | Optional filter. Omit for all roles. |
| limit | integer | no | Maximum wallet rows to return. The response reports wallets_truncated when it caps. |
Screen up to 200 creator addresses in ONE call and get one compact row each: launches, rug rate, the chain baseline, the multiple of that baseline, wallets tied, and the apparent-versus-true operator collapse. Use this instead of calling groundtruth_screen_creator in a loop. known_bad is true only when the creator is in the published set, has at least 5 resolved launches, and rugs at 1.5 times the
| Parameter | Type | Required | Notes |
|---|---|---|---|
| creators | array | yes | Creator addresses. base58 for Solana, 0x... for Robinhood Chain. |
| chain | string | no | Which chain these creators launched on. |
What the KOL wallet launched, and how it ended. Rugged of resolved, seconds to the pull, every count with its N. One call. kol: when the creator is on a public KOL list (kolscan, the pump.fun leaderboard, kolscan.fun, KolHood, Kolosseum) -- tag KOL or TOP PROFIT, the lists, tg / x / verified as yes-no, the list rank, listed now; null when it is on none. Never a name or handle. One creator in, one
| Parameter | Type | Required | Notes |
|---|---|---|---|
| creator | string | yes | Creator address. base58 for Solana, 0x... for Robinhood Chain. |
| chain | string | no | Which chain the creator launched on. |
One WALLET in, its counts out, from GROUNDTRUTH's own Solana capture tape (not a third party feed). Each of four fields is x/n with a one-line definition of n beside it, its rate, the same rate over all wallets, and the word above, below or about ("about" = within 2 percentage points): bad_share (buys in coins from creators with 5+ launches, 80%+ rugged, judged at each coin's launch; n = buys in c
| Parameter | Type | Required | Notes |
|---|---|---|---|
| wallet | string | yes | A Solana wallet address (base58). |
For a copy bot about to follow a wallet into a coin: the coin's creator counts (to that coin's launch when we have them), the wallet's counts from the capture tape, and one line built from those counts only, e.g. "creator: SAME DEV · {r} OF {n} RUGGED (counted to this coin's launch) · wallet: {a}/{b} sells within 60 s before a rug, {vs} the all-wallet rate · {c}/{d} buys where a wallet that first
| Parameter | Type | Required | Notes |
|---|---|---|---|
| wallet | string | yes | The wallet being copied (Solana, base58). |
| ca | string | yes | The coin (Solana mint, base58). |
What the KOL wallet launched, and how it ended. Rugged of resolved, seconds to the pull, every count with its N. One call. The wallets on kolscan, the pump.fun leaderboard, kolscan.fun, KolHood and Kolosseum that launched coins, counted by GROUNDTRUTH: tag KOL or TOP PROFIT, launches, rugged / resolved, PULL, bonded, last mint, and list juice (Telegram / X / verified as yes-no, list rank, listed n
No parameter schema on file.
What the KOL wallet launched, and how it ended. Rugged of resolved, seconds to the pull, every count with its N. One call. JUST IN: launches by wallets on the KOL and top-profit lists, newest first, each with that wallet's rugged / resolved before it; AGAIN: rugs on their coins with the seconds to the pull. 10 minutes behind. Free: the newest 3; with an API key, 30 (or /v1/kol/feed over x402).
No parameter schema on file.
Return the public accuracy scoreboard: how many forward calls GROUNDTRUTH has made, how many have resolved, and how those resolved. Use this to judge how much weight to give the other tools.
No parameter schema on file.
Return the corpus-level figures the site publishes: launches captured per chain, how many resolved, and the share that rugged, died, survived or graduated, with the generation timestamp. This is market data GROUNDTRUTH has captured, not exhaustive coverage from a start date -- use it for baselines, not for totals of all activity.
No parameter schema on file.
WITHDRAWN 2026-09-29: the bands did not beat an age-matched baseline, so this now returns nulls plus band_withdrawn. Was: how fast coins in a given risk band actually rugged: median seconds from GROUNDTRUTH first seeing the curve to the rug, with p25 and p75, for one chain, band and window. Use it to answer "how long would I have had". The denominator is calls that rugged in the window AND carry a
| Parameter | Type | Required | Notes |
|---|---|---|---|
| chain | string | no | solana (pump.fun) or rh (Robinhood Chain) |
| band | string | no | withdrawn: GROUNDTRUTH no longer assigns a band; ignored |
| window | string | no | the resolution window; defaults to 24h |
What $100 would have done across a creator's last N resolved launches. Returns two rows. held_to_end is a MEASUREMENT: the recorded multiple at the end of each launch, with rugged launches counted as zero because the liquidity was pulled. clock_upper_bound is a CEILING, not a prediction: it uses the recorded PEAK multiple and only where the peak arrived at or before the band p25, because the publi
| Parameter | Type | Required | Notes |
|---|---|---|---|
| creator | string | yes | the creator wallet (base58) |
| n | integer | no | how many of the most recent resolved launches, 1-12, default 10 |
| usd | number | no | the stake per launch in dollars, default 100 |
Stamp a verdict ahead of the outcome, so it can be counted later. This is the honesty mechanism: the row is hash-chained to the previous one under your API key, so a verdict cannot be edited or removed after the coin resolves. Stamp every call you make, including the ones you are confident about -- a scorecard built only from remembered wins is not a scorecard. Returns the row hash and sequence nu
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ca | string | yes | the coin address you are calling |
| chain | string | no | — |
| band | string | no | your own call, in your own scorecard; GROUNDTRUTH no longer publishes a band |
| rule_id | string | no | optional: your own rule label |
| note | string | no | optional, up to 200 characters |
How often calls stamped under this API key were right. Groups them by band and by what the coin actually did, resolved from the same data the card reads. A call whose coin has not resolved counts as PENDING, never as a win -- report pending alongside resolved, because the denominator is the point. Also returns whether the hash chain is intact; if it is not, say so rather than quoting the numbers.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | rows to read, 1-500, default 200 |
List the dated autopsies GROUNDTRUTH has published. Each is a writeup of one launch and what happened to it. Returns the available days; fetch a specific one from the public site at /autopsy/<day>.
No parameter schema on file.
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Groundtruth or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.3.0.
1.3.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Groundtruth can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.