threat-scan — phantomoperator MCP Tool
threat-scan
(threat scan) is one of 11 tools on the
phantomoperator
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call threat-scan from your client
- Claude Code phantomoperator threat-scan run in your project directory
- Claude Desktop phantomoperator threat-scan ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor phantomoperator threat-scan ~/.cursor/mcp.json
- VS Code phantomoperator threat-scan .vscode/mcp.json
- Zed phantomoperator threat-scan ~/.config/zed/settings.json
- Windsurf phantomoperator threat-scan ~/.codeium/windsurf/mcp_config.json
- Cline phantomoperator threat-scan ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI phantomoperator threat-scan ~/.gemini/settings.json
- Grok phantomoperator threat-scan .mcp.json (in your project root)
- ChatGPT phantomoperator threat-scan Settings → Connectors → Advanced → Developer mode
- Claude.ai phantomoperator threat-scan Settings → Connectors → Add custom connector
- LangChain phantomoperator threat-scan pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http phantomoperator https://freysaai.freysa.dev/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 11 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.