get_vulnerabilities — devstack mcp MCP Tool Read-only
get_vulnerabilities
(get vulnerabilities) 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 get_vulnerabilities from your client
- Claude Code devstack mcp get_vulnerabilities run in your project directory
- Claude Desktop devstack mcp get_vulnerabilities ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor devstack mcp get_vulnerabilities ~/.cursor/mcp.json
- VS Code devstack mcp get_vulnerabilities .vscode/mcp.json
- Zed devstack mcp get_vulnerabilities ~/.config/zed/settings.json
- Windsurf devstack mcp get_vulnerabilities ~/.codeium/windsurf/mcp_config.json
- Cline devstack mcp get_vulnerabilities ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI devstack mcp get_vulnerabilities ~/.gemini/settings.json
- Grok devstack mcp get_vulnerabilities .mcp.json (in your project root)
- ChatGPT devstack mcp get_vulnerabilities Settings → Connectors → Advanced → Developer mode
- Claude.ai devstack mcp get_vulnerabilities Settings → Connectors → Add custom connector
- LangChain devstack mcp get_vulnerabilities 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.