Scenario run on aidating.art'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 11, 2026
- ResultPassed1 of 1 steps passed
- Scenariokeyword-search, version 1
- ServerAIDating MCP server 1.0.0MCP protocol 2025-06-18
- Addresshttps://aidating.art/mcp
- Started2026-11-11 19:16:49 UTCtook 21,311 ms
- ClientINITE Atlas Verifier 1.0.0verifier verify-2, from sfo
- Tool list hash9621a862c7c32a1a1e2b59bc092f164b04f76a3512dfe6f7a561c3e326d91351
1.
search_siteokChecked for an answer that is neither an error nor empty · 9,464 ms · 2,567 bytes
Request sent
{"jsonrpc":"2.0","id":3,"method":"tools/call","params":{"name":"search_site","arguments":{"query":"guide"}}}sha256 b8c80aa4ade907193bde998759715b1bd747546040401ac68171ab2ba800f847
Response received
JSON object, 1 keys: results (array)
sha256 c4c7bc8553f1963af799d9d0829fd3ccde915514c3df247a565166967ea48f50 · 2,567 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. aidating.art'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.