health-monitor-mcp
health-monitor-mcp lets you register, monitor, and report on MCP servers, GitHub Actions, GitLab pipelines, HTTP endpoints, and webhook alerts.
Register, list, check, and unregister MCP servers (Streamable HTTP, legacy SSE, opt-in stdio).
Register, list, check, and unregister GitHub Actions workflows, with failed job/step diagnostics and optional token env.
Register, list, check, and unregister GitLab CI/CD pipelines, with failed job/stage/ref/commit/URL and bounded trace diagnostics.
Register, list, check, and unregister GET-only HTTP/HTTPS targets, with status, header, body-substring, JSON, redirect, latency, and TLS-expiry assertions.
Register, list, test, and unregister webhook targets for alert delivery, with optional HMAC signing and encrypted secrets.
Check all targets with bounded concurrency and tag filtering.
Set alert thresholds for response time, uptime, and consecutive failures.
Get uptime statistics, cross-provider dashboards, Markdown reports, and monitor stats.
Store bounded health history in SQLite with retention, auto-check scheduling, and concurrency controls.
Run locally as an MCP server or via HTTP/Docker with bearer auth, origin allowlists, and remote-safe profiles.
Monitors GitHub Actions workflow runs, failed jobs, and failed steps for public or private repositories, with support for authentication via environment token.
Monitors GitLab CI/CD pipelines, failed jobs, stages, refs, commits, and URLs, with authentication via environment token and support for self-hosted instances.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@health-monitor-mcp Check all production targets"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
health-monitor-mcp
MCP server, CI workflow, and generic HTTP endpoint monitoring with health history, TLS expiry, assertions, diagnostics, and operational reports.
What This Does
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.
Supported target transports:
Streamable HTTP for current remote MCP servers.
SSE for legacy MCP servers.
stdio for trusted local executables after explicit opt-in.
GitHub Actions workflow runs, failed jobs, and failed steps for public or private repositories.
GitLab CI/CD pipelines, failed jobs, stages, refs, commits, URLs, and bounded trace excerpts for GitLab.com or allowlisted self-hosted instances.
Generic HTTP/HTTPS endpoints with status, header, body-substring, JSON-value, redirect, latency, and TLS-expiry checks.
Azure DevOps monitoring was retired in v1.1.0. GitHub Actions shipped in v1.2.0 and GitLab CI/CD in v1.3.0; generic HTTP/TLS monitoring completes the current multi-provider feature line.
Related MCP server: DevHelm MCP Server
Quick Start
Run the published package noninteractively with Node.js 24:
npx -y health-monitor-mcp --versionExample MCP client configuration:
{
"mcpServers": {
"health-monitor": {
"command": "npx",
"args": ["-y", "health-monitor-mcp"]
}
}
}Tools
Tool | Purpose | Typical prompt |
| Register an MCP target |
|
| Run one MCP health check |
|
| Register a GitHub workflow |
|
| Check latest GitHub run and failed job/step diagnostics |
|
| Register a GitLab project pipeline |
|
| Check latest pipeline and bounded failed-job traces |
|
| Register a GET-only HTTP/HTTPS endpoint |
|
| Check response assertions and TLS expiry |
|
| Register a webhook target for alert delivery |
|
| Send a test payload and return delivery diagnostics |
|
| Check all target kinds with bounded concurrency |
|
| Return MCP uptime and latency history |
|
| Return a cross-provider JSON dashboard |
|
| Return a cross-provider Markdown report |
|
| List registered MCP targets |
|
| List registered GitHub workflow targets |
|
| List registered GitLab pipeline targets |
|
| List registered HTTP targets |
|
| List registered webhook targets |
|
| Remove an MCP target |
|
| Remove a GitHub target and its history |
|
| Remove a GitLab target and its history |
|
| Remove an HTTP target and its history |
|
| Remove a webhook target and its history |
|
| Configure MCP health thresholds |
|
| Inspect cross-provider monitor activity |
|
Expected configuration mistakes return stable error codes and remediation hints, including SERVER_NOT_FOUND, GITHUB_ACTIONS_TARGET_NOT_FOUND, GITLAB_PIPELINE_TARGET_NOT_FOUND, GITLAB_BASE_URL_NOT_ALLOWED, HTTP_TARGET_NOT_FOUND, HTTP_TARGET_URL_NOT_ALLOWED, NO_SERVERS_REGISTERED, STDIO_DISABLED, STDIO_COMMAND_REJECTED, WEBHOOK_ENCRYPTION_KEY_REQUIRED, WEBHOOK_REGISTRATION_FAILED, and WEBHOOK_NOT_FOUND.
Register Targets
Streamable HTTP:
register_server name="inventory-prod" type="http" url="https://inventory.example.com/mcp" tags=["production","inventory"]Legacy SSE:
register_server name="legacy-search" type="sse" url="https://search.example.com/sse" tags=["legacy"]Trusted local stdio:
export HEALTH_MONITOR_ALLOW_STDIO=1
export HEALTH_MONITOR_STDIO_ALLOWLIST=npx,noderegister_server name="local-debugger" type="stdio" command="npx" args=["-y","mcp-debug-recorder"] tags=["local"]The command field must contain one executable only. Put package names and flags in args. Remote-safe runtime profiles always disable stdio.
Register GitHub Actions
Public repositories can be checked without authentication. Private repositories and higher API rate limits require a token with Actions read access:
export GITHUB_TOKEN=your-runtime-secretregister_github_actions name="repo-ci" owner="oaslananka" repository="health-monitor-mcp" workflow="ci.yml" branch="main" token_env="GITHUB_TOKEN" tags=["production","ci"]
check_github_actions name="repo-ci" timeout_ms=5000Only the environment-variable name in token_env is stored. The token value is read at check time and is never written to SQLite, logs, reports, or tool responses.
Register GitLab Pipelines
Public GitLab.com projects can be checked without authentication. Private projects require a token exposed only through the runtime environment:
export GITLAB_TOKEN=your-runtime-secretregister_gitlab_pipeline name="gitlab-ci" project="group/project" ref="main" token_env="GITLAB_TOKEN" tags=["production","ci"]
check_gitlab_pipeline name="gitlab-ci" timeout_ms=5000GitLab.com is allowed by default. A self-hosted instance must use an HTTPS origin and be explicitly allowed:
export HEALTH_MONITOR_GITLAB_BASE_URL_ALLOWLIST=https://gitlab.internal.exampleregister_gitlab_pipeline name="private-gitlab" base_url="https://gitlab.internal.example" project="platform/service" token_env="GITLAB_TOKEN"Only token_env is persisted. Token values, response bodies, and full traces are never stored or returned. Failed-job trace excerpts are range-requested, sanitized, and bounded.
Register HTTP Targets
Public HTTP and HTTPS endpoints are allowed by default. The provider sends GET requests only and supports bounded status, header, body-substring, JSON scalar, and TLS-expiry assertions:
register_http_target name="service-health" url="https://status.example.com/health" expected_statuses=[200] header_assertions=[{"name":"x-ready","equals":"yes"}] body_contains=["ready"] json_assertions=[{"path":"status","equals":"ready"}] tls_expiry_days=30 tags=["production","http"]
check_http_target name="service-health" timeout_ms=5000Private, loopback, link-local, and other non-public addresses are blocked. A trusted private origin is available only in the full runtime profile and must be explicitly listed:
export HEALTH_MONITOR_HTTP_TARGET_ALLOWLIST=https://status.internal.example:8443Every DNS answer and every redirect destination is revalidated. Responses are capped at 262144 bytes; full response bodies and certificate chains are never stored or returned.
Register Webhook Targets
Webhook targets receive alert notifications via HTTPS POST with optional HMAC-SHA256 signing. Secrets are encrypted at rest when HEALTH_MONITOR_WEBHOOK_ENCRYPTION_KEY is configured (32+ characters); otherwise secret registration is rejected.
register_webhook name="alert-webhook" url="https://hooks.example/alerts" secret="webhook-secret" events=["down","alert"] tags=["production","alerts"]
test_webhook name="alert-webhook"Secrets are never returned in listings or diagnostics—always redacted. Delivery diagnostics include status, latency, HTTP status code, and error message.
Health Checks and Reports
check_server name="inventory-prod" timeout_ms=5000
check_all timeout_ms=5000 tags=["production"]
get_uptime name="inventory-prod" hours=24
get_dashboard hours=24 include_tool_stats=true
get_report hours=24HEALTH_MONITOR_MAX_CONCURRENCY limits MCP, GitHub Actions, GitLab, and HTTP checks through one shared scheduled and interactive queue. Results preserve MCP-then-GitHub-then-GitLab-then-HTTP registration order even when checks complete out of order.
Alerts
set_alert name="inventory-prod" max_response_time_ms=500 min_uptime_percent=99 consecutive_failures_before_alert=2Alert findings are evaluated by check_server, check_all, and get_dashboard. Configure webhook targets with register_webhook to receive alert notifications.
Configuration
Variable | Default | Purpose |
|
| SQLite database path |
|
| Enable scheduled checks with |
|
| Health-history retention |
|
| Scheduled and interactive check concurrency |
| unset | Optional GitHub Actions read token |
| unset | Optional GitLab project/pipeline/job read token |
| unset | Allowed self-hosted GitLab HTTPS origins |
| unset | Private HTTP(S) origins allowed in full profile |
|
| Allow trusted local stdio checks |
| unset | Optional comma-separated executable allowlist |
| unset | Bearer token for |
| unset | Allowed remote client origins |
|
| Maximum inbound MCP body |
|
| Inbound body read timeout |
|
| Enable stateful Streamable HTTP sessions |
|
| Stateful session TTL |
|
| Stateful session cap |
| unset | 32+ char key for encrypting webhook secrets |
|
| Webhook delivery timeout in milliseconds |
HTTP Deployment
The server binds to 127.0.0.1 by default. A non-loopback bind requires a remote-safe profile, bearer token, and Origin allowlist.
HOST=0.0.0.0 \
HEALTH_MONITOR_PROFILE=remote-safe \
HEALTH_MONITOR_HTTP_TOKEN=change-me \
HEALTH_MONITOR_HTTP_ORIGIN_ALLOWLIST=https://client.example \
npx -y health-monitor-mcp-httpGET /health is unauthenticated and exposes only status and version. POST /mcp requires Authorization: Bearer <token>.
Docker
Persist /data; otherwise the SQLite database disappears with the container.
docker volume create health-monitor-data
docker run --rm \
-v health-monitor-data:/data \
-p 127.0.0.1:3000:3000 \
-e HOST=0.0.0.0 \
-e HEALTH_MONITOR_PROFILE=remote-safe \
-e HEALTH_MONITOR_HTTP_TOKEN=change-me \
-e HEALTH_MONITOR_HTTP_ORIGIN_ALLOWLIST=https://client.example \
ghcr.io/oaslananka/health-monitor-mcp:latestDevelopment
The repository pins Node.js 24.18.0 and pnpm 11.14.0 through .mise.toml.
mise trust
mise install
pnpm install --frozen-lockfile
pnpm run ciUseful gates:
pnpm run build
pnpm run typecheck
pnpm run lint
pnpm run lint:test
pnpm run test:coverage
pnpm run test:integration
pnpm run docs:api:check
pnpm run security:supply-chain
pnpm run check:metadata
pnpm run check:packageCoverage and Test Analytics
Jest remains the blocking coverage gate with repository-local thresholds. The CI validation job runs
all unit and integration tests once, writes coverage/lcov.info and
reports/junit/junit.xml, and uploads both reports to Codecov. Codecov project and patch statuses
start as informational with target: auto and a 1% tolerance, adding pull-request diff coverage,
file-level visibility, and failed-test analytics without duplicating the local merge gate.
Codecov Bundle Analysis is intentionally not enabled. This package ships Node.js entrypoints compiled
with tsc; it does not currently produce a Rollup, Vite, or Webpack application bundle whose download
size is a product metric.
Architecture and Roadmap
Agent Runtime Configuration
This repository owns its product-specific MCP configuration, plugin manifest, and skills:
File | Purpose |
| Claude Code plugin manifest |
| Project-local MCP configuration |
| Codex CLI example |
| VS Code / Copilot example |
| OpenCode example |
| Product-specific monitoring workflows |
| Runtime setup and validation |
Security and Contributing
Report vulnerabilities through GitHub Private Vulnerability Reporting. See SECURITY.md and docs/security.md.
Contribution setup and standards are documented in docs/contributing.md. Usage questions belong in GitHub Discussions; actionable work belongs in issues.
License
MIT
Available Tools
22 toolscheck_allCheck All TargetsARead-only
Check all registered MCP servers, GitHub Actions workflows, GitLab pipelines, and HTTP targets with one bounded concurrency limit. Results preserve MCP-then-GitHub-then-GitLab-then-HTTP registration order; optional tags filter all target kinds.
Inputs: tags, timeout_ms.
check_github_actionsCheck GitHub Actions WorkflowARead-only
Check the latest run for a registered GitHub Actions workflow and return failed job and step diagnostics.
Inputs: name (required), timeout_ms.
check_gitlab_pipelineCheck GitLab PipelineARead-only
Check the latest registered GitLab pipeline and return failed job, stage, ref, commit, URL, and bounded trace diagnostics.
Inputs: name (required), timeout_ms.
check_http_targetCheck HTTP TargetARead-only
Check a registered HTTP target with DNS-pinned SSRF protection, bounded redirects/body reads, response assertions, and TLS-expiry diagnostics.
Inputs: name (required), timeout_ms.
check_serverCheck Server HealthARead-only
Check the health of a registered MCP server, list tools, and measure response time.
Inputs: name (required), timeout_ms.
get_dashboardGet Health DashboardARead-only
Get a dashboard overview of registered MCP servers, GitHub Actions workflows, GitLab pipelines, and HTTP targets with uptime and performance stats.
Inputs: hours, include_tool_stats.
get_monitor_statsGet Monitor StatisticsARead-only
Get statistics about the health monitor itself, including database activity.
Inputs: no named parameters.
get_reportGet Health Report (Markdown)ARead-only
Get a human-readable Markdown health report for MCP servers, GitHub Actions workflows, GitLab pipelines, and HTTP targets. Paste directly into chat or docs.
Inputs: hours.
get_uptimeGet Uptime StatisticsBRead-only
Get uptime history and statistics for a registered MCP server.
Inputs: name (required), hours.
list_github_actionsList GitHub Actions WorkflowsARead-only
List registered GitHub Actions workflow targets and their latest status.
Inputs: tags, status.
list_gitlab_pipelinesList GitLab PipelinesBRead-only
List registered GitLab pipeline targets and their latest status.
Inputs: tags, status.
list_http_targetsList HTTP TargetsARead-only
List registered HTTP targets and their latest status, response, and TLS summary.
Inputs: tags, status.
list_serversList Registered ServersBRead-only
List all registered MCP servers with their current status.
Inputs: tags, status.
register_github_actionsRegister GitHub Actions WorkflowA
Register a GitHub Actions workflow by owner, repository, and workflow file or ID. Only the token environment-variable name is stored; token values remain in the runtime environment.
Inputs: name (required), owner (required), workflow (required), repository (required), +4 more.
register_gitlab_pipelineRegister GitLab PipelineA
Register a GitLab CI/CD project pipeline. GitLab.com is allowed by default; self-hosted HTTPS origins require HEALTH_MONITOR_GITLAB_BASE_URL_ALLOWLIST. Only the token environment-variable name is stored.
Inputs: name (required), project (required), ref, tags, +3 more.
register_http_targetRegister HTTP TargetA
Register a GET-only HTTP or HTTPS endpoint with status, header, body, JSON, and TLS-expiry assertions. Public networks are allowed by default; private origins require full profile and HEALTH_MONITOR_HTTP_TARGET_ALLOWLIST.
Inputs: no named parameters.
register_serverRegister MCP ServerA
Register an MCP server. Use http for a Streamable HTTP MCP endpoint, sse only for legacy Server-Sent Events servers, and stdio only for a local executable explicitly allowed by runtime policy.
Inputs: no named parameters.
set_alertSet Alert ThresholdsA
Configure alert thresholds for response time, uptime, and consecutive failures.
Inputs: name (required), min_uptime_percent, max_response_time_ms, consecutive_failures_before_alert.
unregister_github_actionsUnregister GitHub Actions WorkflowADestructive
Remove a GitHub Actions workflow target and its stored check history.
Inputs: name (required).
unregister_gitlab_pipelineUnregister GitLab PipelineADestructive
Remove a GitLab pipeline target and its stored check history.
Inputs: name (required).
unregister_http_targetUnregister HTTP TargetADestructive
Remove an HTTP target and its stored check history.
Inputs: name (required).
unregister_serverUnregister ServerBDestructive
Remove a server from monitoring.
Inputs: name (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 22 tools
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.
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.
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.
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
Related MCP Connectors
MCP server for Uptrack uptime monitoring. Manage monitors and incidents from AI agents.
Health checks for public MCP servers: status, latency, tools, and uptime.
Pingstack monitors cron jobs and scheduled tasks with heartbeat checks, and checks websites, TCP ports, DNS records, SSL certificates and domain expiry. This MCP server lets your agent create, update, pause and delete checks, build dashboards and publish them as status pages, manage notification groups, and read incidents with their causes, uptime, run history and latency. Pause, delete and unpublish stay off until you turn them on. Browser sign-in, no API key needed.
Uptime, SSL, DNS and domain monitoring you can talk to from Claude or any MCP client.
Related MCP Servers
- AlicenseAqualityBmaintenanceMonitor MCP server health, uptime, response times, and Azure DevOps pipeline status1412 npm1MIT

DevHelm MCP Serverofficial
AlicenseCqualityAmaintenanceMCP server for uptime monitoring, incidents, alerting, and dependency status.12954 PyPI1MIT- AlicenseAqualityDmaintenanceMCP 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.6MIT
- AlicenseNot gradedqualityCmaintenanceMCP-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.75 npmMIT