Remote server over plain HTTP

High remote-http

The connection to the server is not encrypted: anyone on the network path can read the tool calls, the data they return and any token sent with them, or change them.

Why it matters

Remote MCP servers receive every tool call and return data the model reads. Over plain http://, that traffic and any Authorization header can be read or changed by anyone between you and the server: public Wi-Fi, a compromised router, a proxy. A changed response is a direct route to prompt injection.

How to fix it

Use the server's https:// address. Plain http:// is only acceptable for a server on your own machine (localhost).

Use the https:// address the vendor documents. The only reasonable exception is a server on your own machine (localhost), where the traffic never leaves it.

Before

"url": "http://mcp.example.com/sse"

After

"url": "https://mcp.example.com/sse"

Applies to every MCP client that reads a JSON config: Claude Desktop, Claude Code, Cursor, VS Code, Windsurf and others.

Other checks

Published ; awaiting review.