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