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