Scenario run on design.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 21, 2026
- ResultFailed0 of 1 steps passed
- Scenariolist-catalogue, version 1
- Serverdesign-com-mcp 0.1.0MCP protocol 2025-06-18
- Addresshttps://mcp.design.com/mcp
- Started2026-11-21 10:39:18 UTCtook 3,084 ms
- ClientINITE Atlas Verifier 1.0.0verifier verify-2, from sfo
- Tool list hashd1efff16366a6c27bfb53b510175183119c9a241f50b90125375a503c3861752
1.
list_designserrorChecked for an answer that is neither an error nor empty · 79 ms · 1,746 bytes
isError
Request sent
{"jsonrpc":"2.0","id":3,"method":"tools/call","params":{"name":"list_designs","arguments":{}}}sha256 fc0f725486c9af23b78c166f2dbd74035b6ba170b57e413dda22e5356d92434a
Response received
JSON object, 4 keys: code (string), message (string), retryable (boolean), detail (object)
sha256 871488958a495c9af39a70425b08f44c6c2f052eb08772feb8d48cfdac23e069 · 1,746 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. design.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.