Health Monitor MCP Server

health-monitor-mcp keeps local registries of MCP servers, GitHub Actions workflows, GitLab pipelines, and generic HTTP endpoints. It performs live checks, records bounded evidence in SQLite, evaluates MCP alert thresholds, and returns JSON or Markdown diagnostics suitable for agents and operators. Its 22 documented tools cover check, register, github, actions.

People connecting DevOps & monitoring tools to Claude, Cursor, VS Code, or another MCP client. The project is written in TypeScript.

VERIFIED ACTIVE

LAST COMMIT 2026-07-22 · ★ 2 · #51 OF 101 MAINTAINED DEVOPS & MONITORING · VERIFIED 2026-08-25

MIT · TypeScript servers · how we verify → /methodology

01 · Install Health Monitor

before you install - you'll need

Set HEALTH_MONITOR_ALLOW_STDIO, HEALTH_MONITOR_GITLAB_BASE_URL_ALLOWLIST, HEALTH_MONITOR_HTTP_TARGET_ALLOWLIST, HEALTH_MONITOR_PROFILE, HEALTH_MONITOR_HTTP_TOKEN, HEALTH_MONITOR_HTTP_ORIGIN_ALLOWLIST before connecting. HEALTH_MONITOR_STDIO_ALLOWLIST, GITHUB_TOKEN, GITLAB_TOKEN are optional or environment-specific per the README.

Claude Code

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

Claude Desktop / Cursor / VS Code - add to config

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

Same JSON for Cursor. For VS Code, rename the top-level key from `mcpServers` to `servers`.

Using another client? Same JSON, different key

Claude Desktop · mcpServers

Cursor · mcpServers

VS Code · servers

Windsurf · mcpServers

Zed · context_servers

Cline · mcpServers

Roo Code · mcpServers

Continue · mcpServers

LibreChat · mcpServers

Gemini CLI · mcpServers

Codex CLI · mcp_servers

Full setup guides: every client.

02 · Evidence

Security posture

What to check before giving this server access to your agent - from the registry, GitHub, and our own probes. We don't score safety; we show what's verifiable.

runs as local process (stdio) - runs on your machine with your user's permissions

license MIT - declared in the repository

npm package health-monitor-mcp - unscoped; check the name against the project README before installing

registry namespace io.github.oaslananka is GitHub-verified and matches the repo owner

03 · What Health Monitor can do

Prose above is summarized from the project's README and registry record - no invented capabilities.

What you can build

With this server connected, an agent can run one MCP health check, check latest GitHub run and failed job/step diagnostics, check latest pipeline and bounded failed-job traces, and check response assertions and TLS expiry.

Capability map

Tools grouped from the project's README - what Health Monitor lets an agent do.

read & search

8 tools - e.g. Return MCP uptime and latency history; Return a cross-provider JSON dashboard; Return a cross-provider Markdown report

get_uptime · get_dashboard · get_report · list_servers · list_github_actions · list_gitlab_pipelines…

Check

5 tools - e.g. Run one MCP health check; Check latest GitHub run and failed job/step diagnostics; Check latest pipeline and bounded failed-job traces

check_server · check_github_actions · check_gitlab_pipeline · check_http_target · check_all

Register

4 tools - e.g. Register an MCP target; Register a GitHub workflow; Register a GitLab project pipeline

register_server · register_github_actions · register_gitlab_pipeline · register_http_target

Unregister

4 tools - e.g. Remove an MCP target; Remove a GitHub target and its history; Remove a GitLab target and its history

unregister_server · unregister_github_actions · unregister_gitlab_pipeline · unregister_http_target

update

1 tool - e.g. Configure MCP health thresholds

set_alert

Latest releases

health-monitor-mcp-v1.4.0 · 2026-07-22

1.4.0 (2026-07-22) · add generic HTTP and TLS monitoring

health-monitor-mcp-v1.3.0 · 2026-07-22

1.3.0 (2026-07-22) · add GitLab CI/CD pipeline monitoring (#106) (62e6dab), closes #41

health-monitor-mcp-v1.2.1 · 2026-07-22

1.2.1 (2026-07-22) · enforce MCP Registry description limit

04 · Who maintains Health Monitor

MCP Health Monitor is maintained by oaslananka. We track 9 MCP servers from oaslananka - 6 actively maintained, 101 combined GitHub stars, oldest repo from May 2026. Full record: all servers from oaslananka.

  1. KiCad MCP Pro Production-grade MCP server for KiCad EDA - PCB design, DRC, simulation, BOM, DFM, and manufacturing. ★ 57
  2. easyeda-mcp-pro MCP server for EasyEDA Pro: PCB inspection, BOM, exports, and hardware review. ★ 36
  3. infra-lens-mcp SSH Linux metrics, baselines, anomaly detection, and plain-English infrastructure explanations. ★ 2
  4. MCP Debug Recorder Record debug sessions, commands, failed attempts, and successful fixes in local SQLite storage. ★ 2
  5. ssh-mcp-pro Secure MCP SSH automation server with policy controls, resources, prompts, stdio, and HTTP. ★ 2

05 · Facts

category
DevOps & monitoring - ranked #51 of 101 actively-maintained DevOps & monitoring servers as of 2026-08-25.
release cadence
8 releases in the last 90 days (latest 2026-07-22)
registry
io.github.oaslananka/health-monitor-mcp (active, first published 2026-07-06 · 8 versions)
packages
npm:health-monitor-mcp

06 · Health Monitor FAQ

Is Health Monitor still maintained?

Yes - as of 2026-08-25, its last commit was 2026-07-22 and it shipped 8 releases in the last 90 days. We re-verify nightly.

What can Health Monitor do?

With this server connected, an agent can run one MCP health check, check latest GitHub run and failed job/step diagnostics, check latest pipeline and bounded failed-job traces, and check response assertions and TLS expiry.

How do I install Health Monitor?

Run `npx -y health-monitor-mcp`. The README documents 9 environment variables (HEALTH_MONITOR_ALLOW_STDIO, HEALTH_MONITOR_STDIO_ALLOWLIST, GITHUB_TOKEN…) to set first. Set HEALTH_MONITOR_ALLOW_STDIO, HEALTH_MONITOR_GITLAB_BASE_URL_ALLOWLIST, HEALTH_MONITOR_HTTP_TARGET_ALLOWLIST, HEALTH_MONITOR_PROFILE, HEALTH_MONITOR_HTTP_TOKEN, HEALTH_MONITOR_HTTP_ORIGIN_ALLOWLIST before connecting. HEALTH_MONITOR_STDIO_ALLOWLIST, GITHUB_TOKEN, GITLAB_TOKEN are optional or environment-specific per the README. You can also paste the ready-made client config above.

Does Health Monitor run locally?

Yes - it's a stdio server: it runs on your machine (via npx) with your user's permissions. Your data stays local unless the server itself calls external APIs.

07 · Alternatives to Health Monitor

More DevOps & monitoring MCP servers · Infra Lens MCP · GitHub Actions · Console Automation · Actvt

More TypeScript MCP servers · SSH MCP Pro · Bun Uia · Umbriel · Octen MCP · see all