Answers a request from a foreign website
MCPS-ORIGIN-001Why it mattersThe MCP spec requires a 403 for an Origin the server does not expect. On a public server this keeps other websites' pages from calling it through a visitor's browser; on a server running on someone's own machine, it is what stops a web page from reaching it (DNS rebinding, behind CVE-2025-66414 and CVE-2025-66416).
How to fixWhen an Origin header is present and not on your list, answer 403; requests without one, from programs, keep working. In the official SDKs, turn on DNS rebinding protection and list the allowed origins and hosts.
new StreamableHTTPServerTransport({ enableDnsRebindingProtection: true, allowedOrigins: ['https://claude.ai'], allowedHosts: ['mcp.example.com'] })const origin = request.headers.get('Origin'); if (origin && !ALLOWED.has(origin)) return new Response(null, { status: 403 })- Request
POST https://boltclaw.ai/docs/mcp-server (initialize, Origin: https://probe.invalid)- Answer
200- What we saw
{"jsonrpc":"2.0","id":1,"result":{"protocolVersion":"2025-06-18","capabilities":{"tools":{},"resources":{}},"serverInfo":{"name":"boltclaw-docs","title":"Bolt Claw documentation","version":"1.53.0"},"instructions":"Read-only documentation for the Bolt Claw API. No API key is needed and nothing here…
Seen in the server's answer
SpecMCP 2026-07-28, Transports, Streamable HTTP: Security & Endpoint, item 1CVE-2025-66414 (TypeScript SDK), CVE-2025-66416 (Python SDK): DNS rebinding protection off by default