Scenario run on mekktup.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 22, 2026
- ResultPassed1 of 1 steps passed
- Scenariokeyword-search, version 1
- Servermekktup 1.0.0MCP protocol 2025-06-18
- Addresshttps://mekktup.com/api/v1/agents/mcp
- Started2026-11-22 04:26:46 UTCtook 3,241 ms
- ClientINITE Atlas Verifier 1.0.0verifier verify-2, from sfo
- Tool list hashfe06e573965cc60fee0b233dabd7f5034105a1fdc2cda2b3f030775801354f88
1.
search_destinationsokChecked for an answer that is neither an error nor empty · 234 ms · 163 bytes
Request sent
{"jsonrpc":"2.0","id":3,"method":"tools/call","params":{"name":"search_destinations","arguments":{"q":"guide"}}}sha256 0fada7006b2e371023eeaf09f60369848693deb230c49c1b19555c93e43bd1fe
Response received
JSON object, 2 keys: cities (array), items (array)
sha256 e8ca00a4a1f267a5714ccc98685c47a9d5ef39f9786d8ed2ade364e413b5112f · 163 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. mekktup.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.