Skip to main content
Glama
Mhdd-24

@mhdd_24/api-latency-mcp

by Mhdd-24
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to @mhdd_24/api-latency-mcp

No user-submitted related servers found.

    Related Servers

    • sanitycheck-mcp

      zetlen
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to check the health of internet infrastructure and specific services, helping diagnose whether issues are local or external.
      3
      7 npm
      ISC

    • glasspulse

      MountainLabsDE
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to query and monitor service status, latency, and performance through configurable checks (HTTP, TCP, SSL, keyword, JSON-path) and exposes tools for listing services, retrieving metrics, and running on-demand checks.
      Apache 2.0

    • GitHub Copilot Response Time

      fishcoderman
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables users to measure, track, and compare response times of GitHub Copilot and other AI models. Provides statistical analysis and performance comparison tools for evaluating AI model efficiency.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct role: status checks service health, probe measures latency for one URL, compare contrasts two URLs. There is no meaningful overlap or ambiguity.

    Naming Consistency5/5

    All tool names follow the same consistent pattern: apilatency_ prefix followed by a concise action word. This makes the tool set predictable and easy to navigate.

    Tool Count5/5

    Three tools is well-scoped for a focused latency measurement server. Each tool serves a necessary purpose without unnecessary bloat.

    Completeness4/5

    The core latency workflow is covered: health check, single-target probing, and comparison. A minor gap might be batch/multi-URL analysis, but the current surface is reasonable for the stated purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources