Scenario run on bytetrail.space'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 12, 2026
- ResultPassed1 of 1 steps passed
- Scenariokeyword-search, version 1
- ServerByteTrail 4.1.3MCP protocol 2025-06-18
- Addresshttps://bytetrail.space/mcp
- Started2026-11-12 14:01:54 UTCtook 4,741 ms
- ClientINITE Atlas Verifier 1.0.0verifier verify-2, from sfo
- Tool list hashde35fb223cd84756cafd99cee430bd0179f0a7d899abefaf1b0c8c9a5cef88c5
1.
searchokChecked for an answer that is neither an error nor empty · 1,733 ms · 23,394 bytes
Request sent
{"jsonrpc":"2.0","id":3,"method":"tools/call","params":{"name":"search","arguments":{"query":"guide"}}}sha256 cc689211ad2ae9968c4829e76098a74a14958358d378c7e4769346d09b171b75
Response received
JSON object, 3 keys: papers (array), entities (array), as_of (string)
sha256 8029036cb087f79b13c93b4f16084605d153d4493652544e8fe2cf4a8a59734f · 23,394 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. bytetrail.space'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.