Remote MCP · Endpoint
LLM Latency Tracker MCP server
No. LLM Latency Tracker answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://llmlatency.dev/mcp
The last check completed an MCP handshake.
- Registry name
- dev.llmlatency/llm-latency-tracker
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 86 ms
- Tools exposed
- 2 tools
- Uptime, last 30 days
- 100% from 17 checks
- Described by its publisher as
- Measured latency, time to first token and uptime for ~45 AI inference APIs, by region.
- Website
- https://llmlatency.dev/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 86 ms |
| 2 days ago | Handshake completed | 77 ms |
| 4 days ago | Handshake completed | 56 ms |
| 5 days ago | Handshake completed | 121 ms |
| 7 days ago | Handshake completed | 133 ms |
| 8 days ago | Handshake completed | 311 ms |
| 9 days ago | Handshake completed | 111 ms |
| 12 days ago | Handshake completed | 57 ms |
| 13 days ago | Handshake completed | 119 ms |
| 15 days ago | Handshake completed | 71 ms |
| 16 days ago | Handshake completed | 86 ms |
| 17 days ago | Handshake completed | 58 ms |
| 19 days ago | Handshake completed | 54 ms |
| 20 days ago | Handshake completed | 57 ms |
| 20 days ago | Handshake completed | 51 ms |
| 21 days ago | Handshake completed | 79 ms |
| 22 days ago | Handshake completed | 135 ms |
The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 responding of 17.
How to read this
- ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
- ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
- ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
- ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.
Listing data comes from the official MCP registry. Glide is not affiliated with LLM Latency Tracker and makes no claim about it beyond what these checks measured.