Scenario run on wellnessa-i.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 17, 2026
- ResultPassed1 of 1 steps passed
- Scenariolist-catalogue, version 1
- Serverwai 1.0.0MCP protocol 2025-06-18
- Addresshttps://www.wellnessa-i.com/api/mcp
- Started2026-11-17 14:33:10 UTCtook 3,419 ms
- ClientINITE Atlas Verifier 1.0.0verifier verify-2, from sfo
- Tool list hash7c731452225ab19e06687a5efc5e5bb65e4057270900d4948c40b15114ae8331
1.
list_plansokChecked for an answer that is neither an error nor empty · 411 ms · 13,119 bytes
Request sent
{"jsonrpc":"2.0","id":3,"method":"tools/call","params":{"name":"list_plans","arguments":{}}}sha256 c9aab255aa62990f7ff6f489d3b33dc924060742b45eefe02520008248b6c697
Response received
JSON object, 4 keys: currency (string), plans (array), pilot (object), seller (object)
sha256 711341686324f67318d2c5d77afbb49eedab3869b64a626f33d0b327cdaac63c · 13,119 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. wellnessa-i.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.