Fix error behavior on unregistered handlers in stateless server handler#800
Open
maff wants to merge 1 commit intomodelcontextprotocol:mainfrom
Open
Conversation
Instead of throwing an McpError, it now returns with a JSON-RPC method not found error (-32601), aligned with the stateful implementation.
maff
force-pushed
the
fix-stateless-server-unregistered-handler-behavior
branch
from
caf8474 to
3ac4484
Compare
maff
commented
Feb 16, 2026
| HttpResponse<String> response; | ||
|
|
||
| try { | ||
| HttpRequest request = HttpRequest.newBuilder() |
Author
There was a problem hiding this comment.
ℹ️ Not using the MCP client here as it would throw a client error due to missing capabilities advertised in initialization response.
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.
When a client requests a resource without a registered handler despite a stateless server not advertising it, the server now returns with a JSON-RPC method not found error (-32601), aligned with the stateful implementation.
Motivation and Context
Closes issue #784
How Has This Been Tested?
Integration test covering unregistered handler response with stateless transport.
Breaking Changes
Behavioral change to return a proper JSON-RPC error instead of a HTTP 500 response. Breaking only in terms of changed behavior in case of an error.
Types of changes
Checklist
Additional context