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