Scenario run on finzdata.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 11, 2026
- ResultPassed1 of 1 steps passed
- Scenariokeyword-search, version 1
- ServerFinzData 1.1.0MCP protocol 2025-06-18
- Addresshttps://api.finzdata.com/mcp
- Started2026-11-11 23:23:37 UTCtook 3,681 ms
- ClientINITE Atlas Verifier 1.0.0verifier verify-2, from sfo
- Tool list hash0203265556b9e5ee665ff9adc8822262c71f2cc8def16794d12263dfc1e171d5
1.
search_datasetsokChecked for an answer that is neither an error nor empty · 676 ms · 1,521 bytes
Request sent
{"jsonrpc":"2.0","id":3,"method":"tools/call","params":{"name":"search_datasets","arguments":{"query":"guide"}}}sha256 d2cbc043f0050c047caddbf44a4cd37c888cb01ab15504aba003f7ab2afca8e5
Response received
JSON object, 3 keys: ok (boolean), result (array), meta (object)
sha256 08a22bc98d21a6a43369ab6ab1fc23be6b25271d82d844a1cb9fe33cde0659ce · 1,521 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. finzdata.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.