fix: recognize 2026-07-28 MCP methods - #1076
Merged
Merged
Conversation
DaleSeo
marked this pull request as ready for review
July 28, 2026 20:41
alexhancock
approved these changes
Jul 28, 2026
Merged
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
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.
Closes #1075.
Motivation and Context
The compatibility parser ignores unknown notifications after deserialization fails. Because the registry was still based on MCP 2025-06-18, a malformed
notifications/subscriptions/acknowledgedmessage could be mistaken for an unrelated notification and silently discarded. This change recognizes the current discovery, subscription, and elicitation methods so parse failures surface correctly.How Has This Been Tested?
cargo test -p rmcp --lib transport::async_rw::testBreaking Changes
None. Existing legacy method names remain recognized.
Types of changes
Checklist