LLM Latency Tracker
dev.llmlatency/llm-latency-trackerllmlatency.devstreamable-httpv1.1.0Scanned
Measured latency, time to first token and uptime for ~45 AI inference APIs, by region.
2 tools: 2 only read.
- Reads private data · 1
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
Anlyon alternative
Run the operations that matter as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
2 tools
Only reads 2Show 2 read-only tools
get_ai_api_latencyMeasured latency (TTFB p50/p95) and uptime rankings of AI inference API providers by region, from llmlatency.dev.No findings
Why it is in this group
- The name "get_ai_api_latency" says "get": a word for reading.
Description, as the server wrote it Measured latency (TTFB p50/p95) and uptime rankings of AI inference API providers by region, from llmlatency.dev.
get_model_deprecationsAI model deprecation calendar: announced and shutdown dates, replacement models, and how many days of migration notice each provider actually gives (median/min/max).Reads private dataNo findings
Why it is in this group
- The name "get_model_deprecations" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "calendar": it reads calendars.
Description, as the server wrote it 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.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input or outbound.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Oct 22, 2026, 14:46 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 0
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http llm-latency-tracker https://llmlatency.dev/mcpclaude mcp add --transport http llm-latency-tracker https://llmlatency.dev/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__llm-latency-tracker__get_ai_api_latency",
"mcp__llm-latency-tracker__get_model_deprecations"
],
"ask": [],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as llm-latency-tracker. Review it before you use it.
Capability tags behind 1 rule
- mcp__llm-latency-tracker__get_model_deprecations private-data
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://anlyon.dev/api/v1/servers/dev.llmlatency/llm-latency-tracker/verify?hash=7642de9ffb470a622e5c4a213b11a7245a3509cab741f556a21ecd128bfd0747" | jq -e '.changed == false'Pinned hash 7642de9ffb47, from Oct 21, 2026, 18:38 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://anlyon.dev/servers/dev.llmlatency/llm-latency-tracker/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://anlyon.dev/servers/dev.llmlatency/llm-latency-tracker)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:11 UTC.