Remote MCP server over unencrypted HTTP
MediumAV-MCP-110NetworkMCP config packNew in 2.0
What it finds
A remote MCP server is reached over plain http:// rather than https://.
Why it matters
Anyone on the network path can read the traffic — including tokens — and change tool results or inject instructions on the way.
What an attacker could do: Tool results and credentials can be read or altered in transit.
How to fix it
Use the https:// endpoint. Only use plain http for servers on localhost.
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_PLAINTEXT_REMOTE
- How it detects
- Looks for a specific risky pattern in the code or config.
- Confidence
- Definite: the risky setting is written plainly in the file.
- 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
- MS-2.10
- SOC 2
- CC6.7
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.
Related checks
- Webhook without visible signature verificationAV-NET-003 · High
- Server-side request to a caller-controlled URLAV-NET-004 · High
- TLS certificate verification disabledAV-NET-005 · High
- Code reaches the cloud metadata endpointAV-NET-006 · High
- Plaintext HTTP endpointAV-NET-001 · Medium
- Permissive CORS (wildcard origin)AV-NET-002 · Medium