Home / MCP registry index / dev.llmlatency/llm-latency-tracker
LLM Latency Tracker
dev.llmlatency/llm-latency-tracker in the official MCP registry.
Endpoint https://llmlatency.dev/mcp. Source: github.com/mazamaka/llm-latency-tracker.
The registry describes it as: Measured latency, time to first token and uptime for ~45 AI inference APIs, by region.
We read its 2 tools on 2026-10-28. Nothing in them matched our tool-poisoning rules.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
get_ai_api_latency get_model_deprecations
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/dev-llmlatency-llm-latency-tracker)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.
Related
| Citiview Agent Market com.citiviewgroup.mcp/agent-market | 200 tools, nothing matched 2026-10-26 |
| Huggingface io.github.pipeworx-io/huggingface | 54 tools, nothing matched 2026-10-27 |
| io.github.DarthSander/agentdata-nl io.github.DarthSander/agentdata-nl | 53 tools, nothing matched 2026-10-22 |
| Gemini Crypto io.github.pipeworx-io/gemini-crypto | 52 tools, nothing matched 2026-10-27 |
| Rankwise com.tryrankwise/rankwise | 49 tools, nothing matched 2026-10-26 |
| Tensorust com.tensorust/mcp | 46 tools, nothing matched 2026-10-27 |