Skip to main content
Glama
ni-c

healthchecks-mcp

by ni-c
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to healthchecks-mcp

No user-submitted related servers found.

    Related Servers

    • health-monitor-mcp

      oaslananka
      A
      license
      A
      quality
      B
      maintenance
      MCP server for monitoring health of MCP servers, GitHub Actions, GitLab pipelines, and HTTP endpoints with health history, TLS expiry, assertions, diagnostics, and alerts.
      22
      94 npm
      2
      MIT

    • cronalert-mcp

      jaredhobbs
      A
      license
      A
      quality
      B
      maintenance
      MCP server for CronAlert uptime monitoring — manage monitors, check results, and incidents from any MCP-compatible AI client.
      9
      131 npm
      MIT
    • uptrack-mcp by Uptrack-App

      uptrack-mcpofficial

      Uptrack-App
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for Uptrack uptime monitoring. Manage monitors and incidents from AI agents like Claude, ChatGPT, and Cursor.
      10 npm
      MIT
    • SolidPing by fclairamb

      SolidPingofficial

      fclairamb
      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

    • watchgoose-mcp

      bartekrutkowski
      A
      license
      A
      quality
      A
      maintenance
      Connects MCP-capable AI clients to a monitoring API to inspect cron and recurring-task checks, with opt-in mutations for pings, integrations, and check changes.
      3
      1
      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

    A4.4/5.0

    Scored across 14 tools

    Disambiguation5/5

    Every tool targets a distinct resource and action: checks, pings, flips, integrations, badges, API key info, and service status are cleanly separated. The only potentially adjacent pair, list_pings and list_flips, is clearly differentiated by description as recent pings versus up/down transitions.

    Naming Consistency5/5

    All tools follow a consistent snake_case verb_noun pattern: list_*, get_*, create_*, update_*, delete_*, pause_*, resume_*. The get/list split consistently distinguishes single-resource fetches from multi-item listings.

    Tool Count5/5

    14 tools is well within the ideal 3-15 range and appropriate for a Healthchecks project management surface. Each tool covers a meaningful API operation without padding or redundant alternatives.

    Completeness5/5

    The tool set covers the full check lifecycle: create, read, list, update, pause, resume, delete, plus historical data from pings and flips, integrations, badges, and API key diagnostics. No significant missing operation remains for the stated project-monitoring domain.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources