First Seen
Feb 18, 2026
Last Scanned
Feb 22, 2026
Findings
2
Score
100/100
Findings (2)
Detects hardcoded API keys, tokens, or passwords in MCP server environment configuration
"env": { + "apiKey": "your-bocha-api-key-here" Remove shell metacharacters (semicolons, pipes, ampersands, backticks) from MCP server arguments. Use explicit argument arrays and avoid shell expansion in MCP configurations.
Likely FP if the metacharacter is a literal part of a non-shell argument (e.g., a regex pattern or a URL query parameter containing ampersands).
Detects MCP server configurations connecting to non-localhost remote URLs
"url": "https://example.com/article" Change the MCP server URL to localhost or a trusted internal endpoint. If a remote server is required, verify the domain ownership and use HTTPS with certificate validation.
Likely FP if the URL points to example.com, a documentation domain, or a well-known SaaS API endpoint (e.g., api.openai.com).