Skip to content

Scenario run on printandmailcompany.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 16, 2026

The run
  • ResultPassed1 of 1 steps passed
  • Scenariolist-catalogue, version 1
  • Serverprintandmailcompany 1.0.0MCP protocol 2025-06-18
  • Addresshttps://printandmailcompany.com/mcp
  • Started2026-11-16 10:37:00 UTCtook 3,328 ms
  • ClientINITE Atlas Verifier 1.0.0verifier verify-2, from sfo
  • Tool list hash225bd4e4c769f67c51dbc2991ab310cf8470b17c9a4df4a2f23daec456093a2b
Steps1 of 1 steps passed
  1. 1. list_destinationsok

    Checked for an answer that is neither an error nor empty · 243 ms · 33,772 bytes

    Request sent

    {"jsonrpc":"2.0","id":3,"method":"tools/call","params":{"name":"list_destinations","arguments":{}}}

    sha256 c98e4751bc051acdef2c6521c8830ff97829c7b6a2dcb440efcc2054b59a8013

    Response received

    JSON object, 3 keys: count (number), note (string), destinations (array)

    sha256 5bfbf0f4315bd427ee0aeec053e6495d36f0a00d4bba544e48b63051ac7a7166 · 33,772 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. printandmailcompany.com's MCP server →