feat(mcp): accept the 2025-11-25 handshake too, so shipping clients connect - #36
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The endpoint was strict 2026-07-28 only, which no released MCP client speaks yet - every current client opens with the 2025-11-25
initializehandshake and was refused, so nothing could connect. This serves BOTH revisions from one handler: a request that DECLARES 2026-07-28 gets the strict rules (server/discover, per-request _meta, header mirroring); anything else is a legacy 2025-11-25 client (initialize handshake, no _meta, no mirroring). The 2026-07-28 security property (header/body agreement) is never relaxed for a request that declares that version. Health gate adds a legacy-initialize probe + keeps the modern reject() tests; conformance 23/23; adversarial review found no mirroring bypass and confirmed the gate catches a regression either way.