A developer runs an MCP server on their laptop over HTTP, binds it to all network interfaces so a container can reach it, and skips Origin checking because the server is not on the internet. What is the exposure?

Mediummcptransportshttpsecurity

Last reviewed 22 Aug 2026

None worth acting on: a server on the local machine is not reachable by anything the developer opens in a browser.
A page the developer visits can reach the server through DNS rebinding, which is what the Origin check prevents.Correct answer
The binding is unavoidable, because the host cannot reach a server that listens only on the loopback address.
The exposure is authentication rather than origin: adding a token to the endpoint closes the gap on its own.

Show answer & explanation

Correct answer: B. A page the developer visits can reach the server through DNS rebinding, which is what the Origin check prevents.

Explanation

The principle — A local HTTP server is a network service, and the browser on the same machine is part of its threat model.

Why the key is correct — The specification names both measures and the attack they exist for. Servers MUST validate the Origin header on all incoming connections to prevent DNS rebinding attacks, and when running locally, servers SHOULD bind only to localhost (127.0.0.1) rather than all network interfaces (0.0.0.0). Skipping the first and widening the second removes both layers at once, and the consequence is stated outright: without these protections, attackers could use DNS rebinding to interact with local MCP servers from remote websites.

Why the others are wrong — Localhost is not out of reach of a page in the developer's own browser. Authentication is required as well, not instead. And loopback binding is enough for a host on the same machine.

Remember this — Validate Origin, bind narrowly, and treat your own browser as untrusted.

Sources — MCP first-party documentation.

Sources

Primary sourceStreamable HTTP — MCP · accessed 20 Aug 2026
“Servers MUST validate the Origin header on all incoming connections to prevent DNS rebinding attacks.”
Primary sourceStreamable HTTP — MCP · accessed 20 Aug 2026
“When running locally, servers SHOULD bind only to localhost (127.0.0.1) rather than all network interfaces (0.0.0.0).”
Primary sourceStreamable HTTP — MCP · accessed 20 Aug 2026
“Without these protections, attackers could use DNS rebinding to interact with local MCP servers from remote websites.”

Practise 10 questions on this topic

Take MCP Fundamentals — Timed Test 1 (10 questions) — scored instantly, explanation for every question, no login.

Start the test

A developer runs an MCP server on their laptop over HTTP, binds it to all network interfaces so a container can reach it, and skips Origin checking because the server is not on the internet. What is the exposure?

Mediummcptransportshttpsecurity

Last reviewed 22 Aug 2026

None worth acting on: a server on the local machine is not reachable by anything the developer opens in a browser.
A page the developer visits can reach the server through DNS rebinding, which is what the Origin check prevents.Correct answer
The binding is unavoidable, because the host cannot reach a server that listens only on the loopback address.
The exposure is authentication rather than origin: adding a token to the endpoint closes the gap on its own.

Show answer & explanation

Correct answer: B. A page the developer visits can reach the server through DNS rebinding, which is what the Origin check prevents.

Explanation

The principle — A local HTTP server is a network service, and the browser on the same machine is part of its threat model.

Remember this — Validate Origin, bind narrowly, and treat your own browser as untrusted.

Sources — MCP first-party documentation.

Sources

Primary sourceStreamable HTTP — MCP · accessed 20 Aug 2026
“Servers MUST validate the Origin header on all incoming connections to prevent DNS rebinding attacks.”
Primary sourceStreamable HTTP — MCP · accessed 20 Aug 2026
“When running locally, servers SHOULD bind only to localhost (127.0.0.1) rather than all network interfaces (0.0.0.0).”
Primary sourceStreamable HTTP — MCP · accessed 20 Aug 2026
“Without these protections, attackers could use DNS rebinding to interact with local MCP servers from remote websites.”

Practise 10 questions on this topic

Take MCP Fundamentals — Timed Test 1 (10 questions) — scored instantly, explanation for every question, no login.

Start the test

A developer runs an MCP server on their laptop over HTTP, binds it to all network interfaces so a container can reach it, and skips Origin checking because the server is not on the internet. What is the exposure?

Related questions

A developer runs an MCP server on their laptop over HTTP, binds it to all network interfaces so a container can reach it, and skips Origin checking because the server is not on the internet. What is the exposure?

Related questions