high
Remote MCP server over unencrypted http
A remote (non-localhost) MCP server is reached over http:// instead of https://.
Why it matters
Tool calls, results and any tokens travel in clear text, so anyone on the network path can read or change them.
How to fix it
Use an https:// endpoint. If the server is internal, put it behind TLS anyway.
Before
{
"mcpServers": {
"reports": {
"url": "http://mcp.internal.example.com/sse"
}
}
}After
{
"mcpServers": {
"reports": {
"url": "https://mcp.internal.example.com/sse"
}
}
}Illustrative configs. The checker flags the “before” version with this finding and not the “after” version.
Other checks
- Secret written into an MCP config
- Secret passed as a command-line argument
- Secret inside an MCP server URL
- Remote MCP server with no credentials configured
- Unpinned MCP server package or image
- MCP server installs without asking (npx -y)
- MCP server container runs --privileged
- MCP server container shares the host network
- Broad host folder or Docker socket mounted into an MCP container
- MCP filesystem server with access to a very broad path
- MCP server launched through a shell
- MCP server that can run shell commands
- MCP tools auto-approved or always allowed