Scenario run on replo.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 19, 2026
- ResultFailed0 of 1 steps passed
- Scenariolist-catalogue, version 1
- Serverreplo 1.0.0MCP protocol 2025-06-18
- Addresshttps://api.replo.app/v1/mcp
- Started2026-11-19 08:07:07 UTCtook 3,384 ms
- ClientINITE Atlas Verifier 1.0.0verifier verify-2, from sfo
- Tool list hash8dc1cc8e94bb54e6cf73dbe461d0bcc3d0144ef40b6b6d430d044f7fbd4562ca
1.
list_comment_threadserrorChecked for an answer that is neither an error nor empty · 379 ms · 249 bytes
isError
Request sent
{"jsonrpc":"2.0","id":3,"method":"tools/call","params":{"name":"list_comment_threads","arguments":{}}}sha256 536c020a1aa72695998f131f73023c546c998941d120b0ccee94870249281121
Response received
Text, 138 characters
sha256 5cf197bba1e50f8ecf04a9104adf69c0faa9c83223a85386bc3cdd56c56d9aee · 249 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. replo.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.