{"version":"2.1.309","anchor":"mcp-client-stops-sending-the-listen-stream-get-when-the-serv","canonical_anchor":"mcp-client-stops-sending-the-listen-stream-get-when-the-serv","heading":"MCP connections can skip the listening request when a server says it does not accept it","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309\/e\/mcp-client-stops-sending-the-listen-stream-get-when-the-serv","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309","markdown":"### MCP connections can skip the listening request when a server says it does not accept it\n\nIf an MCP server's last reply says it does not accept GET requests, Claude Code stops sending the GET that opens a listening stream and answers it itself\n\n**Unclear.** It is not stated what condition switches this behaviour on.\n\n**What**\n\nAn MCP server is an outside program that gives Claude Code extra tools. Over some connections, Claude Code sends a GET request (one kind of web request) to open a listening stream, a long-lived connection the server can use to send messages back on its own.\n\nClaude Code now remembers whether the server's most recent reply carried an `Allow` header, the part of a reply that lists which kinds of request the server accepts, and whether that list left out GET. If it did, Claude Code stops sending later GET requests to that server. It answers each one itself with a 405 \"method not allowed\" result and logs the reason. This only happens under a certain condition.\n\n**Why**\n\nIt saves Claude Code from repeatedly trying to open a listening stream with a server that has already said it does not support one.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}