MCP server listens on all network interfaces without auth

HighAV-MCP-112MCPMCP config packNew in 2.0

What it finds

An MCP server binds to 0.0.0.0 (every network interface) and has no visible authentication.

Why it matters

Anyone who can reach this machine on the network — other people on the Wi-Fi, other containers, sometimes the internet — can call its tools directly.

What an attacker could do: Strangers on the network could run this server's tools.

How to fix it

Bind to 127.0.0.1 for local use. If it must be remote, put it behind OAuth or a bearer token and TLS.

Pro shows the corrected code for your exact file, step by step, and re-scans to confirm the fix. See plans

Check details

Finding code: MCP_SERVER_PUBLIC_BIND
How it detects: Looks for a risky pattern, and stays quiet when a matching safeguard is present.
Confidence: Likely: strong signal, but review it in context.
Scans: MCP client configuration files: claude_desktop_config.json, .cursor/mcp.json, .vscode/mcp.json, .mcp.json
OWASP LLM Top 10: LLM07 - Insecure Plugin Design
NIST AI RMF: GV-4.1
SOC 2: CC6.1, CC6.6

Check your agent for this

Paste your agent code or MCP config. The free scan runs all 124 checks in about 10 seconds — no account needed.

Scan an agent free Run it in CI or your editor

Related checks