Skip to main content
Glama
Mhdd-24

@mhdd_24/api-health-mcp

by Mhdd-24
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to @mhdd_24/api-health-mcp

No user-submitted related servers found.

    Related Servers

    • web-doctor

      Baneado98
      A
      license
      A
      quality
      B
      maintenance
      Enables live website health checks including TLS, HTTPS, and security headers, returning an A-F grade with specific fixes.
      2
      MIT

    • Vigilo

      temmeik
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients such as Claude to check current uptime status, inspect monitors and incidents, trigger fresh checks, and retrieve status summaries from a self-hosted monitoring service.
      6 npm
      2
      MIT

    • 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

    • ssl-doctor

      Baneado98
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables live TLS/SSL certificate health checks for any hostname, providing expiry, hostname match, trust verdict, and a health score. Supports both free and paid deep tiers with protocol/cipher analysis.
      MIT
    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.3/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: showing defaults, checking a single URL, and checking multiple URLs. There is no overlap in scope, so an agent can easily select the correct tool.

    Naming Consistency5/5

    All tools follow the consistent 'apihealth_' prefix followed by a verb-like descriptor (status, check, check_many). The naming pattern is uniform and intuitive.

    Tool Count5/5

    With 3 tools covering the core health-check operations, the count is well-scoped for the server's narrow purpose. It is neither sparse nor excessive.

    Completeness4/5

    The toolset covers checking one or multiple URLs and viewing defaults, which covers the primary workflow. A minor gap is the lack of a way to modify defaults, but this is not essential for typical health-check usage.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources