Align SEP-2575 checks with spec PR #3002: serverInfo in result _meta, clientInfo optional#403
Merged
Merged
Conversation
… clientInfo optional Spec PR #3002 (part of the final 2026-07-28 revision) moved serverInfo from the DiscoverResult body to _meta['io.modelcontextprotocol/serverInfo'] and demoted the request envelope's clientInfo from required to SHOULD. The checks still asserted the old shape, failing SDKs that follow the final revision. - Vendor schema types at spec commit 71e30695. - server-stateless: drop the missing-clientInfo rejection case and assert the opposite (a clientInfo-less request must be served, new check sep-2575-request-meta-client-info-optional); discover no longer requires body serverInfo; new SHOULD-level check sep-2575-server-identifies-in-result-meta (WARNING when the _meta identity is absent, SKIPPED when discover itself failed). - request-metadata (client side): the clientInfo SHOULD moves out of the MUST check into its own id sep-2575-client-sends-client-info (WARNING on absence), so requirement levels never blend in one check id. - Mock servers and the everything-server example emit the _meta identity and accept clientInfo-less requests.
commit: |
pcarleton
approved these changes
Jul 17, 2026
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.
Spec PR modelcontextprotocol/modelcontextprotocol#3002 (merged 2026-07-15, part of the final 2026-07-28 revision) moved
serverInfointo result_metaand demotedclientInfoto SHOULD. The referee still asserts the pre-#3002 shape, so a spec-correct SDK fails two SEP-2575 checks.Changes:
clientInfooptional is now the positive assertion on the 2026-07-28 request envelope checks (malformedclientInfostill rejects); the two checks that previously required it are updated in place._metaserverInfo is validated; absence is WARNING/SKIPPED, never FAIL.clientInfoSHOULD split into its own check id so client and server conformance report independently.Tested: full referee suite (419 tests) green; run end-to-end against a typescript-sdk build implementing the final shape (all SEP-2575 legs pass) and against a pre-#3002 build (the two updated checks fail as intended, the SHOULD check warns).