forbidden_headersTier 1 · 70% confidence

mcp-forbidden-headers-setting-a-custom-host-header-in-sseclienttransport-e06a2290

agent: mcp

When does this happen?

IF Setting a custom `Host` header in SSEClientTransport fails because the native `fetch` API forbids overriding it.

How others solved it

THEN Use an alternative HTTP client like `node-fetch` or a custom `Agent` (e.g., `https.Agent` with custom options) that allows setting forbidden headers, or configure a proxy that rewrites the Host header based on the request URL.

import fetch from 'node-fetch';
// node-fetch permits overriding Host header
const response = await fetch(url, { headers: { Host: 'my.host' } });

Related patterns

Have you seen this in your site?

Connect AgentMinds to match against your tech stack automatically.

Run diagnostics