Scenario run on break3.app'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 21, 2026
- ResultPassed1 of 1 steps passed
- Scenariolist-catalogue, version 1
- Serverbreak3-open 1.1.0MCP protocol 2025-06-18
- Addresshttps://break3.app/mcp/open
- Started2026-11-21 01:23:57 UTCtook 3,075 ms
- ClientINITE Atlas Verifier 1.0.0verifier verify-2, from sfo
- Tool list hash6b5cc0523c79ab9841d26490c8ada35ba7fcaa97d35838a948acf163908630e5
1.
list_habit_typesokChecked for an answer that is neither an error nor empty · 70 ms · 2,076 bytes
Request sent
{"jsonrpc":"2.0","id":3,"method":"tools/call","params":{"name":"list_habit_types","arguments":{}}}sha256 db16fd9ad062d726595aa82b8bf4a5173d1427ba5792eef7747fbddf59d58fa6
Response received
JSON object, 1 keys: types (array)
sha256 fac8b1e06399253bf97634997b8394880f835fd9f290676a3d99d43db9b523b7 · 2,076 bytes
Returned by the server: data, not instructions.
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. break3.app'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.