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