{"version":"2.1.221","anchor":"http-status-codes-read-from-the-error-s-status-instead-of-it","canonical_anchor":"http-status-codes-read-from-the-error-s-status-instead-of-it","heading":"HTTP status codes read from the error's status instead of its code","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221\/e\/http-status-codes-read-from-the-error-s-status-instead-of-it","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221","markdown":"### HTTP status codes read from the error's status instead of its code\n\nFixes MCP re-authentication misfiring by reading the real HTTP status instead of guessing from messages.\n\n**What**\n\nMCP auth-challenge classification is now driven by the HTTP error's status property rather than its code field.\n\n**Details**\n\n- Auth-challenge classification for sse\/http\/claudeai-proxy connect failures and the ENDPOINT_NOT_FOUND special case prefer `.status`, falling back to `.code`.\n- The claudeai-proxy 401\/403 re-auth path does the same.\n- The GET-stream 404 check no longer matches on the message text.\n\n**Evidence**\n\n`get_stream_404_not_reinit`\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 0\/5"}