vulkill_get_scan_status — VulKill Security MCP Tool
vulkill_get_scan_status
(vulkill get scan status) is one of 12 tools on the
VulKill Security
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call vulkill_get_scan_status from your client
- Claude Code VulKill Security vulkill_get_scan_status run in your project directory
- Claude Desktop VulKill Security vulkill_get_scan_status ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor VulKill Security vulkill_get_scan_status ~/.cursor/mcp.json
- VS Code VulKill Security vulkill_get_scan_status .vscode/mcp.json
- Zed VulKill Security vulkill_get_scan_status ~/.config/zed/settings.json
- Windsurf VulKill Security vulkill_get_scan_status ~/.codeium/windsurf/mcp_config.json
- Cline VulKill Security vulkill_get_scan_status ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI VulKill Security vulkill_get_scan_status ~/.gemini/settings.json
- Grok VulKill Security vulkill_get_scan_status .mcp.json (in your project root)
- ChatGPT VulKill Security vulkill_get_scan_status Settings → Connectors → Advanced → Developer mode
- Claude.ai VulKill Security vulkill_get_scan_status Settings → Connectors → Add custom connector
- LangChain VulKill Security vulkill_get_scan_status pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http vulkill-security https://app.vulkill.com/api/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.