MCP Health Monitor MCP Server

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add health-monitor-mcp -- npx -y health-monitor-mcp

{
  "mcpServers": {
    "health-monitor-mcp": {
      "args": [
        "-y",
        "health-monitor-mcp"
      ],
      "command": "npx"
    }
  }
}

[mcp_servers.health-monitor-mcp]
command = "npx"
args = ["-y", "health-monitor-mcp"]

{
  "mcpServers": {
    "health-monitor-mcp": {
      "args": [
        "-y",
        "health-monitor-mcp"
      ],
      "command": "npx"
    }
  }
}

{
  "mcpServers": {
    "health-monitor-mcp": {
      "args": [
        "-y",
        "health-monitor-mcp"
      ],
      "command": "npx"
    }
  }
}

This one needs environment variables set before it will start: HEALTH_MONITOR_DB (Custom path for the SQLite database), HEALTH_MONITOR_AUTO_CHECK (Set to '1' to enable background scheduled checks), HEALTH_MONITOR_RETENTION_DAYS (Number of days to retain health check history), HEALTH_MONITOR_MAX_CONCURRENCY (Maximum concurrent scheduled and interactive server checks), GITHUB_TOKEN (Optional GitHub token with Actions read access for private repositories and higher API rate limits), GITLAB_TOKEN (Optional GitLab token with read access to private projects, pipelines, jobs, and traces), HEALTH_MONITOR_GITLAB_BASE_URL_ALLOWLIST (Comma-separated self-hosted GitLab HTTPS origins allowed for monitoring), HEALTH_MONITOR_HTTP_TARGET_ALLOWLIST (Comma-separated private HTTP(S) origins allowed only in the full runtime profile). The author declared them in the registry entry; get the values from the project itself.