Repository navigation
Conversation
The released 2026-07-28 resources page says servers MUST return -32602 for a resource that does not exist (the spec text was aligned with the SEP in modelcontextprotocol/modelcontextprotocol#2863), and basic/index lists -32002 among the codes 2026-07-28 implementations MUST NOT emit. sep-2164-error-code still graded the older SHOULD wording, so a server answering -32002 or -32603 only drew a WARNING. Report FAILURE instead and quote the current text in sep-2164.yaml.
This branch has not been deployed
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
1 participant
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 #552.
sep-2164-error-codereports WARNING when a server answers a non-existent resource with something other than-32602. That matched the spec text when #246 landed, but modelcontextprotocol/modelcontextprotocol#2863 aligned the spec with SEP-2164 and the released 2026-07-28 page now reads:basic/index also lists
-32002among the codes 2026-07-28 implementations MUST NOT emit. Since the server runner doesn't count warnings, a server that still sends-32002currently passes the scenario outright:The check now reports FAILURE, the
-32002hint says the code is retired, andsep-2164.yamlquotes the current sentence.sep-2164-data-uristays a SHOULD; that one comes from the SEP text, not the spec page.Tests: the existing empty-contents negative case now expects FAILURE, and a new inline server answering
-32002asserts error-code FAILURE with the other two checks green. Both fail on main.npm run check,npm run buildandnpm test(642) pass; the everything-server still passes 4/4 since it already returns-32602. The scenario is draft-only, so only 2026-07-28 runs are affected. SDKs that still emit-32002on that wire (the SEP lists C#, Rust, Java, Go and PHP as having done so) will now fail it.src/seps/traceability.jsonstill carries the old row text; I left it for the traceability workflow, per AGENTS.md.AI disclosure per AI_POLICY.md: the investigation, code and tests were done primarily with Claude Code. The numbers above are from local runs.