mcpbeat

LLM Latency Tracker MCP Server

dev.llmlatency/llm-latency-tracker
answering

LLM Latency Tracker is answering right now. Last checked 14 min ago. It exposes 1 tools. Last commit 23 Jul 2026.

Measured latency & uptime for AI inference APIs, by region. Exposes a get_ai_api_latency tool.

Uptime history 40 hours of history
40 hours agonow
100.0%
Uptime 24h
91 of 91 checks
1
Tools
read from the server
113 ms
Response time
average over 24h
1
Stars
last commit 23 Jul 2026

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.

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 1

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.

Endpoints

URLTransportStateLatencyChecked
https://llmlatency.dev/mcp streamable-http answering 88 ms 14 min ago

LLM Latency Tracker — questions

Answers built from our own checks of this server.

What can LLM Latency Tracker do?
It exposes 1 tools, read directly from the server on our last check. Among them: get_ai_api_latency. 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 113 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 1 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 113 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?
Yes — it is published under the NOASSERTION licence, written in Python and 1 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.