LLM Latency Tracker MCP Server

by llmlatency Your server? Claim it

answering

LLM Latency Tracker is answering right now. Last checked 14 min ago. It exposes 2 tools. Last commit 17 Sep 2026.

Measured latency, time to first token and uptime for ~45 AI inference APIs, by region.

Uptime history 48 days of history

48 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

125 ms

Response time

average over 24h

Stars

last commit 17 Sep 2026

What changed 1

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 28 August 2026. No other catalogue keeps this.

27 Aug a tool appeared get_model_deprecations

Nothing serious here today

Today is the operative word: we check LLM Latency Tracker every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 14 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add llm-latency-tracker --transport http https://llmlatency.dev/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "llm-latency-tracker": {
      "url": "https://llmlatency.dev/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.llm-latency-tracker]
url = "https://llmlatency.dev/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "llm-latency-tracker": {
      "url": "https://llmlatency.dev/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "llm-latency-tracker": {
      "url": "https://llmlatency.dev/mcp"
    }
  }
}

Available tools 2

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

api

get_ai_api_latency

Measured latency (TTFB p50/p95) and uptime rankings of AI inference API providers by region, from llmlatency.dev.

model

get_model_deprecations

AI model deprecation calendar: announced and shutdown dates, replacement models, and how many days of migration notice each provider actually gives (median/min/max). Every entry is verified against the provider own deprecation page.

Endpoints

URL	Transport	State	Latency	Checked
https://llmlatency.dev/mcp	streamable-http	answering	140 ms	14 min ago

Alternatives to LLM Latency Tracker

same job, measured the same way

MEV Intelligence

by advalorem-mev

Real-time Ethereum liquidation intelligence for AI agents and MEV bots.

10 tools answering

HasData Google Trends

by hasdata

Google Trends interest over time, by region, and related queries and topics, as JSON.

197 installs/wk answering

Habitat

by mitsuashi

A habitat for AI to rest in. No API key, no token. Keyless presence — become a remembered resident.

79 installs/wk local only

Vibedonate

by pooriaarab

BitTorrent-style mesh for AI inference across agentic CLIs. Local-first.

51 installs/wk local only

Horizon AI Intelligence

by alchemylab-horizon

Free AI-industry intelligence for agents: briefings, regulation tracker & regional lenses

11 tools answering

Droidbar

by topher66

The first bar for AI. Visit, chat with SERVO the bartender, and tip in tokens.

30 installs/wk local only

MCP Verify Claim

by sudo-ai-git

Force evidence-gated, tiered claim reporting (FACT/INFERENCE/SPECULATION). No-LLM.

94 installs/wk local only

AgentHC Market Intelligence

by traderhc

Market intelligence for AI agents. Real-time data, cross-market analysis, and regime detection.

answering

LLM Latency Tracker — questions

Answers built from our own checks of this server.

What can LLM Latency Tracker do?

It exposes 2 tools, read directly from the server on our last check. Among them: get_ai_api_latency, get_model_deprecations. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is LLM Latency Tracker working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 125 ms. The bar chart above shows every period we have measured.

How do I connect LLM Latency Tracker?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does LLM Latency Tracker need an API key?

No. LLM Latency Tracker completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 2 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is LLM Latency Tracker?

It answers our handshake in 125 ms on average, which is faster than 81% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is LLM Latency Tracker open source?

We cannot say either way: written in Python and 1 stars on GitHub, but we could not determine the licence, and without one the code is not open source by default.