Scenario run on tridentstack.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 18, 2026
- ResultPassed1 of 1 steps passed
- Scenariokeyword-search, version 1
- Servertridentstack-docs 1.0.0MCP protocol 2025-06-18
- Addresshttps://docs.tridentstack.com/mcp
- Started2026-11-18 20:17:11 UTCtook 3,101 ms
- ClientINITE Atlas Verifier 1.0.0verifier verify-2, from sfo
- Tool list hashaf93572eea5c46eeb7ccecd7df36baee529e7ef766170d7d107389eaf15aa219
1.
search_docsokChecked for an answer that is neither an error nor empty · 87 ms · 4,744 bytes
Request sent
{"jsonrpc":"2.0","id":3,"method":"tools/call","params":{"name":"search_docs","arguments":{"query":"guide"}}}sha256 237a1df0f08022d9ba9d1981d0508ad5ba691031f64f14bb83b0d68e62b6e5a3
Response received
JSON list, 8 items of type object; keys of the first: id, title, source, url, snippet, score
sha256 7f16b5e8865d79f4b0849c789923308a885c770454e7ab0f604cd8cfad054c9f · 4,744 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. tridentstack.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.