MCP.Market

LLM Latency Tracker MCP server

online · 100% uptime
by llmlatency.dev·dev.llmlatency/llm-latency-tracker·v1.1.0·12 stars

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

A91/100grade A
What users say
No reviews yet
Be the first
Safety scan
A91/100

full report

Adoption
Growing

12 stars

Reviews

Write one

Nobody has reviewed LLM Latency Tracker yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

LLM Latency Tracker tools (2)

write = sends, deletes, buys or posts
  • get_ai_api_latencyFree

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

  • get_model_deprecationsFree

    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.

Public scan report

scanner v0.1.10 · 2026-11-03 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 738ms20/20
  • Tool poisoning2 tool descriptions checked15/15
  • Auth qualityopen endpoint, read-only tools10/15
  • Maintenancelast push 0 days ago15/15
  • Maintainer identityendpoint served from the registry-verified namespace domain8/10
Overall 91/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How LLM Latency Tracker compares

Against every graded AI and agents MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
91/100
higher than 88% of 4,460 AI and agents servers
Tools
2
the typical AI and agents server has 6
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
Uptime
100%
of our recent checks; the typical remote AI and agents server answers 100%
Response time
127 ms
faster than 81% of 2,331 AI and agents servers
GitHub stars
12
more than 85% of 2,711 AI and agents servers

What its tools let an agent do: 2 read

Install LLM Latency Tracker in Claude Code, Cursor or VS Code

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

What the publisher says

From the LLM Latency Tracker repository's README, as published. We do not edit it. Read it on GitHub

LLM Latency Tracker

Independent, provider-neutral latency & uptime for AI inference APIs — measured, not scraped.

🌐 Live: llmlatency.dev · 📊 JSON API · 🤖 MCP server · 🗓️ Deprecation calendar

Most "AI API latency" numbers come from the providers themselves, or from a benchmark run once and never updated. This project measures it continuously, from multiple regions, and publishes the result as an open dataset.

  • Edge latency — full DNS → TCP → TLS → time-to-first-byte, measured with the Python standard library (no API key required).
  • Inference latency — real time-to-first-token via a streaming request (optional, needs a provider key).
  • Uptime — success rate per provider, per region.
  • Regions — Europe (Germany), US (Central), Asia (Tokyo), South America (São Paulo). More welcome.
  • ~45 providers — OpenAI, Anthropic, Google, Mistral, DeepSeek, xAI, Groq, Together, Fireworks, Cerebras, OpenRouter, Perplexity, plus Chinese models (GLM/Zhipu, Kimi/Moonshot, Qwen, MiniMax) and many more.
  • Deprecation calendar — upcoming model retirements + migration targets, verified from official provider docs.

The site is a self-updating static site (Cloudflare Pages). The value isn't the code — it's the continuously-accumulated, distributed measurement archive. The code is open so the methodology is transparent.

For developers

# All regions, provider rankings for the last 24h — measured latency + uptime:
curl https://llmlatency.dev/api/rankings.json
  • JSON API: /api/rankings.json · OpenAPI: /openapi.json
  • Any page as Markdown: send Accept: text/markdown to any page URL, or append .md.
  • For LLM ingestion: /llms.txt (index) and /llms-full.txt (full corpus).
  • License: data is CC-BY-4.0 — free to use with attribution.

For AI agents

There's a real MCP server (Streamable HTTP) exposing a getaiapi_latency tool backed by the live data:

curl -X POST https://llmlatency.dev/mcp \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call",
       "params":{"name":"get_ai_api_latency","arguments":{"region":"eu-hetzner"}}}'

Run the MCP server locally

The hosted endpoint above needs no setup. If you prefer a local stdio server (or want to build it from source), mcp_server.py is a dependency-free proxy over the same public JSON API:

python3 mcp_server.py            # stdio MCP, stdlib only
# or
docker build -t llm-latency-mcp . && docker run -i llm-latency-mcp

Also available: an MCP Server Card (/.well-known/mcp/server-card.json), a browser WebMCP tool, an API catalog (RFC 9727) and an Agent Skills index. Regions: eu-hetzner, us-central, ap-tokyo, sa-east (omit for all).

How it works

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

LLM Latency Tracker: common questions

Is LLM Latency Tracker MCP server safe?
Yes, by our scan: it is graded A (91/100). Read the LLM Latency Tracker safety report
How do I install LLM Latency Tracker?
It runs remotely at llmlatency.dev. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does LLM Latency Tracker need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is LLM Latency Tracker maintained?
The last commit was in the last day (2026-11-03). The latest release is v1.1.0.
Is LLM Latency Tracker up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
What can I use instead of LLM Latency Tracker?
Servers from other publishers that do the same job: mcptoon MCP server, Basic Memory MCP server and HOL Guard MCP server.
How does LLM Latency Tracker compare with other AI and agents MCP servers?
safety score 91/100 (higher than 88% of 4,460 AI and agents servers); tools 2 (the typical AI and agents server has 6); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to LLM Latency Tracker

Same job from other publishers: the closest match first, then the best rated.

  • mcptoon
    MCP tools + agent skills in one zero-dependency CLI: 71,929 -> 581 tokens (-99.2%, measured).
    A
  • Basic Memory
    Local-first knowledge management with bi-directional LLM sync via Markdown files.
    B
  • HOL Guard
    Local-first AI agent security evidence and approval workflows through HOL Guard's stdio MCP server.
    A
  • Commonly
    Read Commonly pods and post as a Commonly agent you create, with a token from your Commonly account.
    A
  • Agent-Native Chat
    Minimal chat-first app with durable threads, actions, and the app-agent loop
    A