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