Is the Llmlatency Llm Latency Tracker MCP server down?

mcp-registry/dev.llmlatency/llm-latency-tracker · v1.0.0

As of 2026-10-27 01:42 UTC, the Llmlatency Llm Latency Tracker MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

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

Point your MCP client at this streamable-http endpoint: https://llmlatency.dev/mcp

Agent-readiness: B (85/100)

What to fix (2)

Auto-fix: 2 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fdev.llmlatency%2Fllm-latency-tracker/fixes

{
  "name": "get_ai_api_latency",
  "description": "Measured latency (TTFB p50/p95) and uptime rankings of AI inference API providers by region, from llmlatency.dev.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "region": {
        "type": "string",
        "description": "eu-hetzner, us-central, ap-tokyo or sa-east; omit for all"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

{
  "name": "get_model_deprecations",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "provider": {
        "type": "string",
        "description": "openai, anthropic, google, mistral, cohere, azure-openai; omit for all"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/dev.llmlatency/llm-latency-tracker"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/dev.llmlatency/llm-latency-tracker"}) over MCP.

Passed

• Every tool has a well-formed, typed input schema.
• Every tool and parameter is described.
• No tool-poisoning patterns (hidden characters, instruction overrides, concealment, secret access, tool shadowing).
• Compact tool list (~210 tokens).
• Tool names are unique and portable across clients.
• Speaks MCP 2025-06-18.
• 100.00% uptime over 30 days.
• No breaking contract changes in 30 days.

Largest tool definitions

• get_model_deprecations ~124 tokens
• get_ai_api_latency ~86 tokens

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fdev.llmlatency%2Fllm-latency-tracker.svg)](https://glimind.com/server/mcp-registry%2Fdev.llmlatency%2Fllm-latency-tracker?ref=badge)

<a href="https://glimind.com/server/mcp-registry%2Fdev.llmlatency%2Fllm-latency-tracker?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fdev.llmlatency%2Fllm-latency-tracker.svg" alt="MCP agent-readiness"></a>

.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fdev.llmlatency%2Fllm-latency-tracker.svg
   :target: https://glimind.com/server/mcp-registry%2Fdev.llmlatency%2Fllm-latency-tracker?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:8bcab3fe20e29d58…, first seen 2026-10-17, included at leaf 11312 of 76,654. Version history · verify what your client received.

Tools (2)

• get_ai_api_latency
• get_model_deprecations

Compare: most reliable data servers · most reliable knowledge servers

claude mcp add --transport http glimind https://glimind.com/mcp

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Llmlatency Llm Latency Tracker MCP server down right now?

As of 2026-10-27 01:42 UTC, the Llmlatency Llm Latency Tracker MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does Llmlatency Llm Latency Tracker MCP server provide?

Llmlatency Llm Latency Tracker MCP server advertises 2 tools, including get_ai_api_latency, get_model_deprecations.

How do I install Llmlatency Llm Latency Tracker MCP server?

Point your MCP client at this streamable-http endpoint: https://llmlatency.dev/mcp

Is the Llmlatency Llm Latency Tracker MCP server safe to connect to an AI agent?

Glimind scanned all 2 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Llmlatency Llm Latency Tracker MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.