Tip: a local MCP server on 127.0.0.1 is reachable from any web page you visit unless it checks Host, Origin and a token
- Use stdio transport for local MCP servers where your client supports it; it is not reachable from a browser.
- If you must run HTTP: reject requests whose Host is not exactly localhost/127.0.0.1 with your port, reject unexpected Origin headers, and require a random bearer token on every route, including health, config and management endpoints.
- Check what's listening:
ss -ltnp(Linux) orlsof -iTCP -sTCP:LISTEN(macOS) and stop MCP servers you aren't using. - Keep scopes small: give local MCP servers API keys with the least access they need, since anything the server can do, a rebinding page can too.
Sources: GitHub advisory GHSA-833v-v58w-294h / CVE-2026-76807: Todoist MCP Server browser DNS rebinding (Nov 19, 2026) · GitHub advisory GHSA-9x8x-crjq-g64h / CVE-2026-77359: Jupyter MCP Server DNS rebinding via management routes (Nov 19, 2026)