Scenario run on certisyn.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 20, 2026
- ResultPassed1 of 1 steps passed
- Scenariokeyword-search, version 1
- Servercertisyn 1.0.0MCP protocol 2025-06-18
- Addresshttps://app.certisyn.com/api/mcp
- Started2026-11-20 23:17:32 UTCtook 3,996 ms
- ClientINITE Atlas Verifier 1.0.0verifier verify-2, from sfo
- Tool list hash7313efe9bad5b1c529d643c518830d5c8ead7ca70ca778eb731730e7f1488a7c
1.
registry_searchokChecked for an answer that is neither an error nor empty · 992 ms · 1,334 bytes
Request sent
{"jsonrpc":"2.0","id":3,"method":"tools/call","params":{"name":"registry_search","arguments":{"q":"guide"}}}sha256 b8975041a9f44ddc9309f6237e8a5f3dd1197836168d2b570fd70cf5d9643640
Response received
JSON object, 5 keys: data (array), total (number), limit (number), offset (number), filters (object)
sha256 2d9c778fe6a0b41f934382a619275b7c37046367ab962f7287a17bbad091fa0a · 1,334 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. certisyn.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.