{"version":"2.1.299","anchor":"redirects-stripped-from-mcp-fetch-responses","canonical_anchor":"redirects-stripped-from-mcp-fetch-responses","heading":"Redirects are removed from MCP fetch responses","tier":"internal","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/redirects-stripped-from-mcp-fetch-responses","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Redirects are removed from MCP fetch responses\n\nWhen a fetch made for an MCP connection gets a redirect, Claude Code now strips the address it points to, so it is not followed\n\n**What**\n\nMCP (Model Context Protocol) is how Claude Code connects to outside tools and services. When a web request made for MCP gets a redirect response (status 301, 302, 303, 307 or 308) that names a new address, Claude Code now removes that address from the response.\n\n**Why**\n\nIn practice, those redirects are not followed to the address the server named.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}