Server data from the Official MCP Registry
Measured latency, time to first token and uptime for ~45 AI inference APIs, by region.
About
Measured latency, time to first token and uptime for ~45 AI inference APIs, by region.
Remote endpoints: streamable-http: https://llmlatency.dev/mcp
Security Report
Valid MCP server (1 strong, 1 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry. 1 finding(s) downgraded by scanner intelligence.
1 tool verified · Open access · 1 issue found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
Permissions Found in Source Code
Found by scanning the linked source code. This listing connects to a hosted endpoint, so none of this runs on your machine: it describes what the server software does where it is hosted.
How to Connect
Remote Plugin
No local installation needed. Your AI client connects to the remote endpoint directly.
Add this to your MCP configuration to connect:
{
"mcpServers": {
"dev-llmlatency-llm-latency-tracker": {
"url": "https://llmlatency.dev/mcp"
}
}
}Documentation
View on GitHubFrom the project's GitHub README.
📊 LLM Latency Tracker
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.txtindex. - 🗓️ 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-21
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.
| Region | Fastest provider (p50) | p50 | p95 | Uptime |
|---|---|---|---|---|
| Asia (Tokyo) | fireworks | 18 ms | 58 ms | 100% |
| Europe (Germany) | fireworks | 97 ms | 199 ms | 100% |
| South America (São Paulo) | openrouter | 62 ms | 100 ms | 100% |
| US (Central) | fireworks | 29 ms | 75 ms | 100% |
- Full dataset:
data/rankings/2026-10-21.json(latest) - Citable archive (DOI):
10.5281/zenodo.23388429— daily aggregates, CC-BY-4.0 - Hugging Face dataset: https://huggingface.co/datasets/llmlatency/llm-latency-tracker
- Kaggle dataset: https://www.kaggle.com/datasets/llmlatency/llm-latency-tracker
- Archived in Software Heritage:
swh:1:snp:2778cbabd72a70a629ee35fbd5ac536d1ccb7a9a - Python client: https://pypi.org/project/llmlatency/
- Live rankings and methodology: https://llmlatency.dev
- Machine-readable API: https://llmlatency.dev/api/rankings.json
- Model deprecation calendar: https://llmlatency.dev/deprecations
Snapshot generated 2026-10-21T07:23:54Z — this table is regenerated daily.
Reviews
No reviews yet
Be the first to review this server!
More Developer Tools MCP Servers
Rea
Freeby Morluto · Developer Tools
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
Paperclip
Freeby Paperclipai · Developer Tools
Trending hip-hop artist momentum scores across four cultural dimensions.
Git
Freeby Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
Fetch
Freeby Modelcontextprotocol · Developer Tools
Web content fetching and conversion for efficient LLM usage
Toleno
Freeby Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
MCP Marketplace
Freeby mcp-marketplace · Developer Tools
Search and install MCP servers from inside your AI client.
