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