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