scan_vulnerabilities_batch — devstack mcp MCP Tool
scan_vulnerabilities_batch
(scan vulnerabilities batch) is one of 10 tools on the
devstack mcp
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call scan_vulnerabilities_batch from your client
- Claude Code devstack mcp scan_vulnerabilities_batch run in your project directory
- Claude Desktop devstack mcp scan_vulnerabilities_batch ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor devstack mcp scan_vulnerabilities_batch ~/.cursor/mcp.json
- VS Code devstack mcp scan_vulnerabilities_batch .vscode/mcp.json
- Zed devstack mcp scan_vulnerabilities_batch ~/.config/zed/settings.json
- Windsurf devstack mcp scan_vulnerabilities_batch ~/.codeium/windsurf/mcp_config.json
- Cline devstack mcp scan_vulnerabilities_batch ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI devstack mcp scan_vulnerabilities_batch ~/.gemini/settings.json
- Grok devstack mcp scan_vulnerabilities_batch .mcp.json (in your project root)
- ChatGPT devstack mcp scan_vulnerabilities_batch Settings → Connectors → Advanced → Developer mode
- Claude.ai devstack mcp scan_vulnerabilities_batch Settings → Connectors → Add custom connector
- LangChain devstack mcp scan_vulnerabilities_batch pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http devstack-mcp https://devstack-mcp.vercel.app/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 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.