mcp-release-qa

Build the candidate revision, start the documented entry point, and run one complete protocol session covering initialize, discovery methods, and representative invocations. Record exact commands, raw responses, and a PASS or FAIL verdict as reproducible evidence.

Build four inventories from source registrations, live discovery output, generated catalogs, and documentation, then compare by stable identifier. Report entries missing at runtime, stale names or schemas, and install commands that fail to start the server.

Probe requests before initialization, malformed JSON-RPC envelopes, unknown methods, unsupported protocol versions, repeated initialization, and invalid arguments. Each response must carry the correct request ID, a useful error message, and no side effects or leaked stack traces.

Yes, the process covers STDIO, Streamable HTTP, and SSE transports. For STDIO, stdout must carry only protocol messages with logs on stderr; for HTTP, record status codes, MCP headers, and session identifier handling.

A new process creates a new STDIO session, so one-shot requests test several incomplete sessions instead of one valid session. Keeping initialize, initialized notification, discovery, and invocation in one session proves real protocol compliance.