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