Skip to main content
Glama
eiabhiram

API Health Check MCP Server

by eiabhiram

Related Servers

Alternatives to API Health Check MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Monitor MCP server health, uptime, response times, and Azure DevOps pipeline status
      14
      12 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables real-time data streaming through Server-Sent Events with timestamp broadcasting and server monitoring capabilities. Optimized for deployment on Render.com with health checks and status endpoints.
      284 npm
      -
    • A
      license
      A
      quality
      B
      maintenance
      Uptime monitoring for websites, APIs, SSL certificates, domain expiry, ping and TCP/UDP ports. 15 tools to list, create, pause and delete monitors, pull incident timelines with error codes, and read hourly or daily uptime and response-time statistics.
      15
      37 npm
      1
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Uptime monitoring from your AI agent: create and diagnose checks (40 types: HTTP, TCP, DNS, SSL, ICMP, databases, message queues and more), read results and incidents, and manage status pages and maintenance windows. Built into the self-hostable SolidPing server, served over streamable HTTP at /api/v1/mcp.
      42
      12
      AGPL 3.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Official Hyperping MCP server for uptime, API, cron and server monitoring. 26 tools covering monitors, outages and timelines, uptime, response time, MTTR and MTTA, on-call schedules and escalation policies, over a remote Streamable HTTP endpoint with Bearer token auth and no install.
      1
      MIT

    TDQS

    B3.4/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of ambiguity between tools.

    Naming Consistency5/5

    The single tool uses a clear snake_case naming convention, so no inconsistency exists.

    Tool Count1/5

    A single tool that checks only one hardcoded endpoint is trivial for a health check server, which would typically need multiple endpoints or generic checks.

    Completeness1/5

    The tool surface is severely incomplete, as it only covers checking one specific endpoint, lacking support for other endpoints or dynamic health checks.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues