Skip to main content
Glama

Related Servers

Alternatives to llm-latency-tracker

  • A
    license
    A
    quality
    D
    maintenance
    Real-time status monitoring, uptime tracking, incident history, and API pricing for 42+ AI tools including ChatGPT, Claude, Gemini, Cursor, GitHub Copilot, Perplexity, DeepSeek, and Groq. No API key required. Data updated every 5 minutes from independent monitoring infrastructure.
    7
    58 npm
    1
    MIT
  • A
    license
    A
    quality
    B
    maintenance
    Enables AI coding assistants and agent workflows to query live measured free-LLM performance and availability, including throughput, uptime, tool-calling success, and model diagnostics.
    4
    2
    MIT

Related Servers

  • A
    license
    A
    quality
    B
    maintenance
    Enables discovery, live probing, ranking, and recommendation across OpenAI-compatible gateways, measuring real latency, success, streaming, and tool-calling behavior so you can see which models actually work right now. Keeps per-model probe history to answer "which model should I use?" through tools like list_models, probe, ranking, recommend, and report.
    5
    55 PyPI
    2
    MIT
  • A
    license
    Not graded
    quality
    B
    maintenance
    Live, reproducible crypto infrastructure benchmarks for AI agents: RPC latency, bridge fees, L1 finality, gas oracle accuracy, stablecoin pegs. Three tools (list_benchmarks, get_benchmark,query_prom), no API key, CC-BY-4.0 data.
    11
    MIT
  • A
    license
    Not graded
    quality
    B
    maintenance
    Enables you to ask which AI models are up, fast, popular, or low-priced right now, using public gateway status, usage, and price data with no API key required. Supports single-model status checks, side-by-side comparisons of up to six models, usage leaderboards, and lowest-price lookups for chat, coding, image, or TTS tasks.
    121 npm
    MIT

TDQS

A4.5/5.0

Scored across 4 tools

Disambiguation5/5

The two latency tools have overlapping subject matter, but each description explicitly points to the other with a clear boundary rule (leaderboard vs. single-provider across regions). The deprecations and coding-agent-health tools are in entirely different domains, and each description reiterates its scope ('calendar data, not latency', 'for raw API latency use...'). An agent can pick correctly without guessing.

Naming Consistency5/5

All four tools use the same get_<subject> snake_case pattern with no deviation in verb or casing. The names are predictable and readability is high. Minor quibble: get_ai_api_latency actually returns a ranked leaderboard rather than a single latency value, but the convention itself is uniform.

Tool Count4/5

Four tools is compact and none feel redundant, which fits a narrowly scoped observability server. It is on the lean side given it spans three distinct areas (API latency, model deprecations, coding-agent health), leaving little room for supporting lookups.

Completeness4/5

The surface covers the core questions: regional ranking, per-provider detail, deprecation planning, and agent regression checks. Gaps are minor and workaroundable (no provider-list endpoint, though errors enumerate valid ids; no historical time series beyond the fixed 24h window).

Maintenance

ActivityActive
ResponsivenessNo recent community issues