Requests with "id": null are run like notifications
维护者通常 1 天内回复
评估
这个 Issue 还没有评估数据。
描述
I'm wiring the SDK into a Rails app (stateless Streamable HTTP, JSON responses) and noticed that a request with "id": null isn't rejected. The server treats it like a notification: the method runs, but no response is produced, so over HTTP the client gets a 202 Accepted with an empty body.
For a tool that changes data, that's a write the client never hears about. The spec rules null ids out for requests:
- Requests MUST include a string or integer ID.
- Unlike base JSON-RPC, the ID MUST NOT be
null.
(Basic Protocol, Requests, same wording in 2026-07-28)
Repro with 1.7.0 (main at 9d12f51 behaves the same):
require "mcp"
calls = 0
echo = MCP::Tool.define(
name: "echo",
description: "Echoes the text back",
input_schema: { properties: { text: { type: "string" } }, required: ["text"] },
) do |text:, server_context: nil|
calls += 1
MCP::Tool::Response.new([{ type: "text", text: text }])
end
server = MCP::Server.new(name: "repro", version: "1.0.0", tools: [echo], capabilities: { tools: {} })
server.handle_json('{"jsonrpc":"2.0","id":null,"method":"tools/call","params":{"name":"echo","arguments":{"text":"hi"}}}')
# => nil
server.handle_json('{"jsonrpc":"2.0","method":"tools/call","params":{"name":"echo","arguments":{"text":"hi"}}}')
# => nil
calls # => 2
JsonRpcHandler.valid_id? accepts nil on purpose (the error message says "or be an integer or null"), which fits plain JSON-RPC but not MCP.
The second call, without any id, is a notification by JSON-RPC rules, so it's a slightly different case. But tools/call isn't a notification in MCP, and the Streamable HTTP transport allows a server to answer a notification it can't accept with an HTTP error (e.g. 400). Running it silently seems like the riskiest option.
What I'd expect:
"id": nullis answered with Invalid Request (-32600) and the method doesn't run.- A request method sent without an id is refused, or at least not executed.
- 主要语言
- Ruby
- 星标
- 924
- 派生
- 136
- 平均合并
- 1 天 5 小时
- 30 天内合并 PR
- 37
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
modelcontextprotocol/ruby-sdk 的其他 Issue
-
Empty members in the Accept header cause a 500可能已有人在做 @koic 今天认领。 未关闭bug
难度 2/5 1-3 小时 新手友好度 82/100
modelcontextprotocol/ruby-sdk#609 ·
维护者通常 1 天内回复
-
Error responses carry "id": null, which the MCP schema does not allow可能已有人在做 @koic 今天认领。 未关闭bug
难度 3/5 半天 新手友好度 45/100
modelcontextprotocol/ruby-sdk#606 ·
维护者通常 1 天内回复
-
String request ids are limited to letters, digits, "_" and "-"可能已有人在做 @koic 于 1 天前认领。 未关闭bug
modelcontextprotocol/ruby-sdk#603 · 已指派 1 人 ·
维护者通常 1 天内回复
-
Methods of undeclared capabilities return -32603 instead of -32601可能已有人在做 @koic 于 1 天前认领。 未关闭bug
modelcontextprotocol/ruby-sdk#602 · 已指派 1 人 ·
维护者通常 1 天内回复
-
Support modelcontextprotocol/experimental-ext-triggers-events可能已有人在做 @koic 于 4 天前认领。 未关闭enhancement
modelcontextprotocol/ruby-sdk#594 · 已指派 1 人 ·
维护者通常 1 天内回复
查看 modelcontextprotocol/ruby-sdk 的全部 Issue
相似的 Issue
-
难度 1/5 1 小时以内 新手友好度 72/100
TheOdinProject/curriculum#31465 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 66/100
-
agent:triaged bug bughunt pm:bundler priority:p1
难度 2/5 1-3 小时 新手友好度 70/100
SocketDev/socket-patch#1573 · 1 条评论 ·
维护者通常 1 天内回复
-
Generated server webpack config keeps Rspack's manifest and CSS extraction plugins可能已有人在做 @justin808 今天认领。 未关闭bug
难度 2/5 1-3 小时 新手友好度 72/100
shakacode/react_on_rails#5184 ·
维护者通常 1 天内回复
-
bug chat verified
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 6 天内回复