The pre-ship checklist

No server we build ships until it clears this checklist, current as of the 2026-07-28 revision. It is published in full, including the lines that are inconvenient, because a checklist you can read is a better trust signal than a badge you cannot verify. Most of it is automated; the last section is the human review that a test cannot replace.

Protocol

• Negotiates 2026-07-28; no dependence on removed sessions or the old handshake.
• Serves Streamable HTTP; no reliance on deprecated HTTP+SSE.
• Roots, Sampling and Logging usage inventoried against the twelve-month window.

Auth and scope

• OAuth 2.1 with PKCE for remote; API key for internal.
• Audience claim validated; client tokens never forwarded downstream.
• Least-privilege role; the server can reach only the named sources.
• Every scope in the running server matches the signed manifest.

Write safety

• Every write tool has an explicit scope and a required dry-run.
• No destructive delete exists anywhere in the tool surface.

The manual review that cannot be automated

A test suite catches regressions. It does not catch a tool named so ambiguously the model picks it for the wrong job, an error message the model cannot act on, or a scope that is technically valid and practically too wide. The founder reads the diff for those before anything deploys.