πŸ“Š LLM Latency Tracker

MCP serverMonitoring & ops

Your AI can tell you how fast and reliable different AI inference providers are, using measured latency, time to first token, and uptime data for around 45 APIs. The measurements are broken down by region, so it can compare providers where it matters for you.

Use πŸ“Š LLM Latency Tracker in Claude, ChatGPT or Ahel Desktop

Free. Sign in, add πŸ“Š LLM Latency Tracker and connect your AI. About a minute.

Also: Claude Code Β· Cursor Β· Codex

Then ask your AI: use πŸ“Š LLM Latency Tracker to get ai api latency

Details

Available today. Use it from your connected AI after setup.

After adding it, ask your AI for latency, time to first token, or uptime numbers for the providers and regions you care about, or to compare a few providers side by side.

πŸ“Š LLM Latency TrackerStart free

What your AI can do with it

  • Look up measured latency for around 45 AI inference APIs
  • Check time to first token for a specific provider
  • See uptime figures for AI inference providers
  • Compare providers within a specific region
  • Find which providers respond fastest in a given region

Install πŸ“Š LLM Latency Tracker

The server’s own address, for the clients that take one directly. Or connect Ahel once and every client you use reads it from one address, with the account kept on Ahel rather than in each client’s config.

  • Claude Code

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

    Run it once in your project, then open /mcp to approve any sign-in the server asks for.

  • Claude Desktop

    https://llmlatency.dev/mcp

    Add a custom connector in Settings, paste this address, and approve the sign-in.

  • Cursor

    cursor://anysphere.cursor-deeplink/mcp/install?name=llm-latency-tracker&config=eyJ1cmwiOiJodHRwczovL2xsbWxhdGVuY3kuZGV2L21jcCJ9

    Open the link and Cursor adds the server at that address.

  • ChatGPT

    https://llmlatency.dev/mcp

    In Settings, enable Developer mode, create an MCP app, and paste this address. Your plan and workspace must allow custom apps.

  • Codex

    codex mcp add llm-latency-tracker --url 'https://llmlatency.dev/mcp'

    Run it once, then sign in with codex mcp login llm-latency-tracker if the server asks for an account.

From the project's README

As published by mazamaka/llm-latency-tracker in README.md.

Measure AI API latency and uptime across regions, and publish the results as open data.

🌐 Live rankings · JSON API · MCP endpoint

⚑ What it does

  • 🌍 Regional measurements β€” compare provider response times and availability from distributed probe nodes.
  • ⏱️ Two probe types β€” network time to first byte (TTFB) and optional inference time to first token (TTFT).
  • πŸ“ˆ Open dataset β€” daily rankings, historical snapshots and regional p50 / p95 statistics.
  • πŸ€– Agent access β€” JSON API, MCP, Markdown pages and an llms.txt index.
  • πŸ—“οΈ Model lifecycle β€” a deprecation calendar with links to provider announcements.

πŸ”§ Built for measurement

  • Python standard-library core for edge probes; provider keys are needed for inference probes.
  • SQLite storage and regional aggregation, with remote nodes shipping measurements to a central node.
  • Static publishing for the website and JSON datasets.
  • CI checks for tests and linting; published snapshots include their measurement date.

Reading the results: edge TTFB measures network/API responsiveness, not model generation speed. Compare it separately from inference TTFT; results depend on region, probe type and time window.

πŸš€ Quick start

Use the public data without installing anything:

curl https://llmlatency.dev/api/rankings.json

Or run edge probes locally with Python 3.12+:

git clone https://github.com/mazamaka/llm-latency-tracker.git
cd llm-latency-tracker
REGION=local python3 run.py
python3 aggregate.py --region local

For a local stdio MCP server over the published API (stdlib only, no keys):

python3 mcp_server.py

Tools: get_ai_api_latency (provider leaderboard per region), get_provider_latency (one provider across regions), get_model_deprecations (model shutdown calendar), get_coding_agent_health (Claude Code / Codex speed and accuracy drift). All read-only.

Inference probes, API access & site generation β†’ Β· Deployment β†’

πŸ§ͺ Contributing

Add a provider, bring a new probe region, or improve the measurement code. See CONTRIBUTING.md for setup and checks.


Python Β· SQLite Β· JSON API Β· MCP Β· Cloudflare Pages

Code: MIT Β· Data: CC-BY-4.0, with attribution to llmlatency.dev.

Daily snapshot β€” 2026-10-10

Measured latency across 46 AI inference providers in 4 regions. Method: distributed edge (DNS→TCP→TLS→TTFB) + inference (TTFT) probes, last 24h. License: CC-BY-4.0.

RegionFastest provider (p50)p50p95Uptime
Asia (Tokyo)fireworks16 ms60 ms100%
Europe (Germany)fireworks98 ms199 ms100%
South America (SΓ£o Paulo)openrouter62 ms104 ms100%
US (Central)fireworks28 ms77 ms100%

Snapshot generated 2026-10-10T07:22:13Z β€” this table is regenerated daily.

Tools it offers (2)

What this server listed when Ahel dialed its public endpoint in Oct 2026, with no key and no account of yours. The names are the server’s own.

  • get_ai_api_latency
  • get_model_deprecations

Signals

GitHub stars
2
Last commit
Sep 2026
Advanced
Delivery
llm-latency-tracker MCP server β†’ your Ahel connector (mcp.ahel.ai) β†’ your AI.
Item type
mcp-server
Key
dev-llmlatency-llm-latency-tracker
Source
github.com/mazamaka/llm-latency-tracker
Hosted endpoint
https://llmlatency.dev/mcp