| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
…elcontextprotocol#1072) The HttpServletStatelessServerTransport was returning HTTP 200 for all JSON-RPC responses, including METHOD_NOT_FOUND errors. Per the MCP Streamable HTTP specification (2026-07-28), an unrecognized method must return HTTP 404 with JSON-RPC error code -32601, not HTTP 500 or 200. This caused OpenAI's hosted MCP client to receive HTTP 500 (or 200 with an error body it could not process) when sending server/discover requests, resulting in HTTP 424 external_connector_error from the Responses API. The fix maps METHOD_NOT_FOUND (-32601) responses to HTTP 404 at the transport layer. All other JSON-RPC errors continue to use HTTP 200 per standard JSON-RPC conventions.
|
hi, honest question, why this repo looks dead? no commits/merged PRs in last month or so, is it really dead? |
Sorry, something went wrong.
no idea. i will there was more traction and active reviews |
Sorry, something went wrong.
|
Summer time in Europe, everyone was basically off. We're back online. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Summary
The 2026-07-28 Streamable HTTP spec requires that an unsupported RPC method return HTTP 404 with JSON-RPC error -32601, not HTTP 500. Right now HttpServletStatelessServerTransport returns 200 for everything, including unrecognized methods like server/discover. OpenAI's hosted MCP client hits this path and surfaces a 424 external_connector_error to users.
This PR adds a mapJsonRpcErrorToHttpStatus() helper that maps -32601 to 404. It's a small, isolated change that unblocks production traffic without waiting for full 2026-07-28 lifecycle support tracked in #1011.
Test plan
Fixes #1072