{"version":"2.1.232","anchor":"mcp-sse-connections-survive-a-failing-close-handler","canonical_anchor":"mcp-sse-connections-survive-a-failing-close-handler","heading":"MCP SSE connections survive a failing close handler","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/mcp-sse-connections-survive-a-failing-close-handler","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### MCP SSE connections survive a failing close handler\n\nOne misbehaving close handler can no longer break shutdown of your MCP SSE connections.\n\n**What**\n\nFor MCP servers connected over SSE, an error thrown by a close handler no longer escapes; it is logged and counted, so one bad handler cannot take down the shutdown path.\n\n**Details**\n\n- The failure is reported as its own metric, `cli_sse_close_handler_threw`.\n- Two separate checks for whether the connection is going away, an abort signal and a state string comparison, were replaced by one helper.\n\n**Evidence**\n\n`cli_sse_close_handler_threw`\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}