Repository navigation
v0.18.0 - MCP022: loopback bridges with no Origin check
What's new
MCP022 — a server bound to 127.0.0.1/localhost only still accepts cross-origin requests because it never checks the Origin header.
Binding to loopback is often (wrongly) treated as equivalent to "unreachable by web content." Any browser tab open on the same machine can still reach it via CORS or an unauthenticated WebSocket upgrade. This pattern has now surfaced three times independently: Ollama's long-known default-CORS behavior, BraveMCP's own HTTP bridge before it was fixed in v0.2.0, and Cline's currently-open Hub dashboard WebSocket bug.
Fires on a loopback-bound server (not bind-all — that's MCP018) alongside either a permissive CORS setup (bare cors(), bare CORS(app), or a literal wildcard header) or a WebSocket connection handler with no Origin check.
See the README and CHANGELOG for details.
151 tests passing (was 141). Dogfood self-scan clean.