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