Operators
You run an MCP server. Here is how it gets checked, how it climbs, and how you answer anything we publish about it. Everything is free; a verdict is not for sale in any direction.
Submit your server
The form lives on the standing submissions page — terms first, then the form: submit a server →. Kinds: watch · truth check · invited inside-the-wall check (private data; verdict-only publishing) · right of reply.
How a server climbs, V0 → V3W
- V0 → V1 “shows its work”: state your source, coverage, and freshness in your tool descriptions — the census reads them weekly.
- V1 → V3 “has an answer key”: if your subject has a public authority (tariffs, sanctions, FX, packages, papers…), name it — the classifier grades on the claim classes at method: by kind.
- V3 → V3W “answer key in hand”: keep the tool callable without a wall for at least the fixed probe questions; the wide lanes re-derive your answers weekly and a single decided verdict promotes you.
- Private data? The invited pathway: written permission + sandbox credentials, we check inside the wall, publish verdict + digest only. A failed check publishes exactly like a passed one — agreed in the invitation, or there is no check.
The badge
Your live verdict, embeddable — updates with every census, links to your dossier, and is a dated observation, never a warranty:
[](https://robinsaige.com/s/YOUR-NAME)
Right of reply
No finding that names an operator is published without a served, 7-day right-of-reply window. Your reply is published verbatim and unedited alongside the observation. If we have a factual detail wrong, we correct it publicly — our corrections ledger is append-only and never deleted.
Terms in one line: dated observations with receipts, public and reproducible methods only, never past authentication uninvited, no guaranteed verdict or timeline, and nothing you send is sold.