fix #724, restore compliance to 2025-11-25 spec #725
+19
−0
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
overheadhunter
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
ignore unknown values during deserialization of
ClientCapabilities.ElicitationMotivation and Context
This fixes a deserialization issue in the initialization request sent from clients using the
2025-11-25protocol.How Has This Been Tested?
Test added
Breaking Changes
No, deserialization is now less strict.
Types of changes
Checklist
existing tests* pass locally* I had local issues with starting
docker.io/tzolov/mcp-everything-server:v3used in one of the tests. Up until this test, everything was green.Additional context
see #724