Skip to main content
Glama
oaslananka

health-monitor-mcp

by oaslananka
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to health-monitor-mcp

No user-submitted related servers found.

    Related Servers

    • mcp-server-health-monitor

      dbsectrainer
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP-native health monitoring that probes MCP servers using the list_tools protocol handshake, detects version drift, stores history in SQLite, and generates an HTML dashboard.
      24 npm
      MIT

    • Frank MCP Server

      cbuckley-code
      F
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that provides typed, audited, least-privilege tools for monitoring AWS infrastructure and GitHub pipelines, including instance health, service status, logs, deployment status, CI workflow runs, failed jobs, and PR checks.
      -

    • tibet-pol-mcp

      Humotica
      A
      license
      A
      quality
      D
      maintenance
      MCP server for running infrastructure health checks with TIBET provenance. It enables users to define, execute, and audit process health checks with dependency chaining and drift tracking.
      6
      MIT

    • MCP Health Monitor

      oaslananka
      A
      license
      A
      quality
      B
      maintenance
      Monitor MCP server health, uptime, response times, and Azure DevOps pipeline status
      14
      12 npm
      1
      MIT

    • automation-health-mcp

      chainwright
      A
      license
      A
      quality
      C
      maintenance
      An MCP server for auditing automation health, finding failures, stale logs, and non-functional endpoints that report success while quietly failing.
      7
      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

    A3.9/5.0

    Scored across 22 tools

    Disambiguation5/5

    Each tool targets a distinct resource type (MCP server, HTTP target, GitHub Actions, GitLab pipeline) and action (register, list, check, unregister). The cross-cutting tools (check_all, get_dashboard, get_report, get_monitor_stats) have clearly separate purposes, so there is no ambiguity.

    Naming Consistency5/5

    All tool names follow a verb_noun pattern (register, list, check, unregister, get, set) with the resource type clearly stated. Minor singular/plural variations (e.g., list_http_targets vs. register_http_target) are natural and do not break consistency.

    Tool Count5/5

    With 22 tools covering four distinct target types (MCP servers, HTTP, GitHub Actions, GitLab pipelines) plus cross-cutting monitoring and reporting, the count is well-scoped for the server's broad purpose. Each tool earns its place, and the count is not excessive for the feature set.

    Completeness4/5

    The lifecycle for each target type is covered: register, list, check, and unregister. There is no explicit update/edit operation for target configurations (e.g., modifying assertions), but agents can work around this by unregistering and re-registering. Overall, the surface is solid with only minor gaps.

    Maintenance

    ActivityStale
    ResponsivenessResponsive

    Resources