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 天 6 小時
- 30 天內合併 PR
- 39
環境準備
- 沒有 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 於 2 天前認領。 未關閉bug
難度 2/5 1-3 小時 新手友好度 82/100
modelcontextprotocol/ruby-sdk#609 ·
維護者通常 1 天內回覆
-
Default capabilities advertise listChanged, prompts, resources and logging on a tools-only stateless server可能已有人在做 @koic 於 1 天前認領。 未關閉bug
難度 3/5 1-2 天 新手友好度 56/100
modelcontextprotocol/ruby-sdk#619 ·
維護者通常 1 天內回覆
-
Error responses carry "id": null, which the MCP schema does not allow可能已有人在做 @koic 於 2 天前認領。 未關閉bug
難度 3/5 半天 新手友好度 45/100
modelcontextprotocol/ruby-sdk#606 ·
維護者通常 1 天內回覆
-
String request ids are limited to letters, digits, "_" and "-"可能已有人在做 @koic 於 3 天前認領。 未關閉bug
modelcontextprotocol/ruby-sdk#603 · 已指派 1 人 ·
維護者通常 1 天內回覆
-
Methods of undeclared capabilities return -32603 instead of -32601可能已有人在做 @koic 於 3 天前認領。 未關閉bug
modelcontextprotocol/ruby-sdk#602 · 已指派 1 人 ·
維護者通常 1 天內回覆
查看 modelcontextprotocol/ruby-sdk 的全部 Issue
相似的 Issue
-
難度 2/5 1-3 小時 新手友好度 85/100
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 75/100
thewca/worldcubeassociation.org#16088 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 72/100
Homebrew/homebrew-core#319232 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 66/100
維護者通常 1 天內回覆
-
enhancement help wanted
難度 2/5 1-3 小時 新手友好度 78/100
ecosyste-ms/repos#1215 ·
維護者通常 1 天內回覆