MCP Conformance Engineering: Versioning, Evidence, and Operations
A server is not conformant because its happy path worked through one SDK. Conformance lives at the wire, at version boundaries, through intermediaries, and during rollback.
100 minutesBuildPythonMembers
Learning Objectives
- Turn normative MCP rules into golden and negative wire transcripts.
- Keep strict
2026-07-28behavior separate from bounded legacy fallback. - Distinguish additive unknown fields from an invalid unknown
resultType. - Compare raw JSON-RPC evidence with an SDK-normalized view.
- Prove header and body integrity through a real proxy boundary.
- Gate releases with redacted transcript, health, and rollback evidence.