fix: pass SEP-2243 client conformance#1012
Open
DaleSeo wants to merge 1 commit into
Open
Conversation
DaleSeo
force-pushed
the
fix/sep-2243-client-conformance
branch
from
July 18, 2026 14:42
1d70824 to
619a260
Compare
DaleSeo
marked this pull request as ready for review
July 18, 2026 14:56
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
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.
Fixes #978
Motivation and Context
Updates the Rust conformance client to pass the SEP-2243 standard, custom, and invalid tool-header scenarios. Header scenarios now negotiate the draft protocol through discovery, consume the conformance runner's
toolCallscontext, and reject malformedx-mcp-headertools before they reach callers.The client previously initialized before draft request metadata was available, ignored camelCase tool-call context, and left invalid header-annotated tools visible even after rejecting them from the header cache.
How Has This Been Tested?
The conformance runner passes all checks for
http-standard-headers(3/3),http-custom-headers(18/18), andhttp-invalid-tool-headers(11/11).Breaking Changes
None.
Types of changes
Checklist