Consider adding authentication and HTTPS for MCP endpoint

[arshan846]

Security Consideration: Localhost MCP Endpoint Without Authentication

Summary

The mcp-chrome server exposes an MCP endpoint at http://127.0.0.1:12306/mcp without authentication.

Context

Since this is localhost-only, network-based attacks are not a concern. However, any local process on the machine can connect to this endpoint and invoke browser control tools (navigate, screenshot, extract content).

This is a defense-in-depth consideration, not a critical vulnerability. The primary trust boundary is the local machine itself.

Severity

• MEDIUM — localhost HTTP without auth (local process attack surface)
• Per the MCP specification, HITL enforcement is the client's responsibility, not the server's

Suggestions (defense in depth)

1. Consider token-based auth — a shared secret so only the intended client can connect
2. Random port assignment — avoid predictable ports that local malware could target
3. Unix domain socket (on supported platforms) — eliminates TCP exposure entirely

How This Was Found

Detected using Pluto AgentGuard, an open-source security scanner for MCP configurations.

\\�ash
pip install pluto-aguard
aguard scan your-mcp-config.json
\\

Happy to discuss.