Compatibility intelligence
Findings
Review confirmed behavior and its upstream reporting state.
VerifiedNot actionable upstream
protocol-behaviorThe TypeScript SDK surfaces duplicate responses through its error callback while keeping the session usable.
Verified compatibility behavior: the TypeScript SDK reported the duplicate response through its error callback, preserved the first result, and remained usable for a same-session ping. No upstream defect was identified in the source report.
VerifiedIssue opened by MCP Failure Lab
protocol-behaviorRuby MCP SDK 1.6.1 accepts tool responses missing jsonrpc or declaring jsonrpc "1.0" over stdio and Streamable HTTP in all three repeats.
VerifiedIssue opened by MCP Failure Lab
recoveryAfter rejecting a malformed response, the stdio client stops processing later responses.
VerifiedIssue opened by MCP Failure Lab
protocol-behaviorThe client accepts a response declaring JSON-RPC 1.0 instead of rejecting it.
VerifiedEvidence added to existing issue
reliabilityC# MCP SDK 2.2.0 stdio cleanup waits for the five-second shutdown timeout after successful cancellation recovery.
C# MCP SDKv2.2.0ScenarioLate Response After CancellationRepositorymodelcontextprotocol/csharp-sdkEvidence1
VerifiedEvidence added to existing issue
recoveryPython MCP SDK 2.2.0 propagates active-request session loss through the surrounding transport task context.
Python MCP SDKv2.2.0ScenarioSession Loss During Active RequestRepositorymodelcontextprotocol/python-sdkEvidence1
VerifiedIssue opened by MCP Failure Lab
recoveryAn exited stdio child leaves same-session and new Streamable HTTP sessions disconnected.
VerifiedEvidence added to existing issue
recoveryAn upstream HTTP disconnect can terminate the proxy and leave the active session unusable.
VerifiedEvidence added to existing issue
compatibilitymcp-proxy 0.12.0 clean installs can resolve an incompatible MCP SDK and fail during import.
VerifiedIssue opened by MCP Failure Lab
reliabilityA cancelled long-running operation can delay stdio client cleanup beyond the configured bound.
Official Everything Serverv2026.8.31ScenarioCleanup After TimeoutRepositorymodelcontextprotocol/serversEvidence1
Page 1 of 2