Groundtruth MCP Server

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

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.

One creator in, one small answer out: is this creator known bad, with the rug rate, the chain baseline and the multiple that justifies the verdict. The cheapest call on this server -- use it when all you need is the decision rather than the wallet list. known_bad is null, never false, for a creator we have no record of. The data behind it is a batch export, so a creator who launched in the last hour is not in it yet; every response carries the timestamp it was generated.

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 published record carries the peak and the final multiple, not the path between them. Say "at most" when you quote it. Launches with no recorded multiple are excluded from BOTH the stake and the return, so the two describe the same set -- quote computed_for and of, never just the total. Solana only today: the Robinhood outcome record carries no peak multiple, so neither row can be computed there.

Look up one token and return what GROUNDTRUTH recorded about it: the outcome label (rugged, died, graduated, survived, or no outcome recorded), liquidity and market-cap figures, holder counts, and the record of the wallet that launched it. Accepts a Solana mint or a Robinhood Chain 0x contract address. This is the same read the public site performs when someone pastes a contract address.

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.

How often calls sealed under this API key were right. Groups them by band and by what the coin actually did, resolved from the same record 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.

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 chain baseline or worse -- a bare rug rate is noise, the multiple is a decision. known_bad is null, NEVER false, for a creator we have no record of: absence is not innocence.

Given one creator address, return every wallet that was early in that creator's launches: the role each played (creator, operator_pool, repeat_buyer, one_off), how many of this creator's launches it was early in versus how many it was early in anywhere, and that wallet operator's own rug rate. Also returns the apparent-versus-true collapse: how many wallets LOOK independent versus how many distinct actors they actually are, after merging wallets with near-identical launch histories. Rates come with the chain baseline, because a rate without its baseline is not a finding. This is the analysis no other source produces.

Seal a verdict BEFORE the outcome exists, so it can be scored 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. Seal 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 number.

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 rug time, and it travels in the answer. Below 30 such calls the percentiles are null and enough_data is false -- say "not enough resolved calls to state a time" rather than quoting a number. Omit every argument to get the whole table in one call.