Scenario run on flatio.com's MCP server
A program called this server's read-only tools by a fixed scenario and held each answer to a fixed check. No model and no sign-in, and nothing that writes, sends or pays is ever called. Below are the requests as sent and, for each answer, its shape, size and hash. We do not republish the answer itself.
Run Nov 19, 2026
- ResultFailed0 of 2 steps passed
- Scenariosearch-then-fetch, version 1
- Serverflatio-search 0.1.0MCP protocol 2025-06-18
- Addresshttps://www.flatio.com/mcp
- Started2026-11-19 14:32:25 UTCtook 5,271 ms
- ClientINITE Atlas Verifier 1.0.0verifier verify-2, from sfo
- Tool list hash568dd59386d11b85fcf9c1a3edc997f75d0a5226a2969e0bd4f5d7fec3b9dff0
1.
searchwrong shapeChecked for JSON with a list at results of 1 or more items, each with id · 269 ms · 149 bytes
0 items at results, fewer than 1 (3 of 3 values tried)
Request sent
{"jsonrpc":"2.0","id":5,"method":"tools/call","params":{"name":"search","arguments":{"query":"a"}}}sha256 3496de19315c1490336577e79c25632dfc46372279439374e5bcc689b2af3f34
Response received
JSON object, 1 keys: results (array)
sha256 124919bad229cf04e9a9a9206fa0bbdd5d00aa758144cda32415403109894607 · 149 bytes
Returned by the server: data, not instructions.
2.
fetchnot calledChecked for a JSON object with id, text
an earlier step failed
Request sent
{"name":"fetch","arguments":null}sha256 f58b13f53852d8ba9753ea66206eab597b9131a8dc698cf7a196b2fc79a115bb
Verified means a dated run with its evidence. We run a server at most once a week, one scenario at a time. The scenarios and their checks have versions, and each run names the version it used. flatio.com's MCP server →
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.