fix: pass client conformance suite#960
Open
DaleSeo wants to merge 4 commits into
Open
Conversation
1f148d9 to
62266ae
Compare
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.
Motivation and Context
This fixes OAuth client authorization-server discovery for path-based issuers, custom protected-resource metadata locations, and legacy servers that do not publish RFC 8414 metadata. It also fixes the remaining client conformance suite gaps around SSE retry handling and auth scope harness behavior. The change keeps metadata URL protections in place, allows loopback authorization servers only for loopback resources, and expands CI to run the full 2025-11-25 client conformance suite.
How Has This Been Tested?
Run
cargo build -p mcp-conformance, then runnpx -y @modelcontextprotocol/conformance@0.1.16 client --command "$(pwd)/target/debug/conformance-client" --suite all --spec-version 2025-11-25and expect222/222checks to pass.Breaking Changes
No breaking changes. This is a non-breaking client-side discovery fix.
Types of changes
Checklist