MCP Health Monitor
NPM · HEALTH-MONITOR-MCP
Monitor MCP, CI, and HTTP targets with health history, TLS expiry, assertions, and diagnostics
Available components
Last scanned (2 hours ago)
Scores higher than 90% of npm servers
Category Monitoring and Observability
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security80
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects @modelcontextprotocol/sdk 1.29.0, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 51 of 128 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to oaslananka/health-monitor-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 105 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability62
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 1182 tokens (~53/item across 22 items; 22 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage83
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 48% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 4 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 22 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 29 Oct 26 0
- CVE-2026-118663 affects this package: high ▼ security
- 28 Oct 26 +1
- GHSA-f897-62hf-6gxq affects this package: high ▼ security
- Stability: 0.97 → pass security
- 26 Oct 26 −1
- Stability: pass → 0.93 functional
- 24 Oct 26 0
- CVE-2023-54404 affects this package: high ▼ security
- 21 Oct 26 0
- CVE-2026-111771 affects this package: high ▼ security
- CVE-2026-111768 affects this package: high ▼ security
- CVE-2026-111769 affects this package: high ▼ security
- CVE-2026-111767 affects this package: high ▼ security
- 20 Oct 26 +1
- Stability: 0.97 → pass security
- Security disclosure: unverified → pass ▲ functional
- 19 Oct 26 0
- Stability: pass → 0.97 functional
- 18 Oct 26 −1
- Security disclosure: pass → unverified ▼ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/health-monitor-mcp@1.4.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | oaslananka/health-monitor-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/oaslananka/health-monitor-mcp/.github/workflows/publish-npm.yml@refs/tags/health-monitor-mcp-v1.4.0 |
| Rekor log index | 2220604836 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:301f5d158bdf970752593c5f8936b64a8a6febf21c5cb61958b61449ef8c6844540be40bec63500c608c9db46115befc638a1899a2f4899a7c3fdb512 |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 8 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-rmxm-3fg6-px4f | CVE-2026-118663 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N | yes |
| GHSA-22jm-h49p-29qw | CVE-2026-111767 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L | yes |
| GHSA-46jr-4wx8-v453 | CVE-2026-111768 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-6prh-2h8m-c8cw | CVE-2026-111769 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N | yes |
| GHSA-6qxp-vccf-f47h | CVE-2026-104850 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N | yes |
| GHSA-f897-62hf-6gxq | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes | |
| GHSA-rvq5-wwqv-78pq | CVE-2026-111771 | medium | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N | yes |
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 128 packages
| Packages resolved | 128 |
|---|---|
| Deprecated | 1 |
| Stale | 50 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_all Check All Targets ~80
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.
| Name | Type | Req | Description |
|---|---|---|---|
| tags | array | – | Filter targets by registered server tags |
| timeout_ms | integer | – | – |
No output schema declared.
No examples provided.
check_github_actions Check GitHub Actions Workflow ~51
Check the latest run for a registered GitHub Actions workflow and return failed job and step diagnostics.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | GitHub Actions target name to check |
| timeout_ms | integer | – | – |
No output schema declared.
No examples provided.
check_gitlab_pipeline Check GitLab Pipeline ~57
Check the latest registered GitLab pipeline and return failed job, stage, ref, commit, URL, and bounded trace diagnostics.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | GitLab pipeline target name to check |
| timeout_ms | integer | – | – |
No output schema declared.
No examples provided.
check_http_target Check HTTP Target ~56
Check a registered HTTP target with DNS-pinned SSRF protection, bounded redirects/body reads, response assertions, and TLS-expiry diagnostics.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | HTTP target name to check |
| timeout_ms | integer | – | – |
No output schema declared.
No examples provided.
check_server Check Server Health ~44
Check the health of a registered MCP server, list tools, and measure response time.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Server name to check |
| timeout_ms | integer | – | – |
No output schema declared.
No examples provided.
get_dashboard Get Health Dashboard ~51
Get a dashboard overview of registered MCP servers, GitHub Actions workflows, GitLab pipelines, and HTTP targets with uptime and performance stats.
| Name | Type | Req | Description |
|---|---|---|---|
| hours | integer | – | – |
| include_tool_stats | boolean | – | – |
No output schema declared.
No examples provided.
get_monitor_stats Get Monitor Statistics ~21
Get statistics about the health monitor itself, including database activity.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_report Get Health Report (Markdown) ~46
Get a human-readable Markdown health report for MCP servers, GitHub Actions workflows, GitLab pipelines, and HTTP targets. Paste directly into chat or docs.
| Name | Type | Req | Description |
|---|---|---|---|
| hours | integer | – | – |
No output schema declared.
No examples provided.
get_uptime Get Uptime Statistics ~36
Get uptime history and statistics for a registered MCP server.
| Name | Type | Req | Description |
|---|---|---|---|
| hours | integer | – | – |
| name | string | yes | Server name |
No output schema declared.
No examples provided.
list_github_actions List GitHub Actions Workflows ~36
List registered GitHub Actions workflow targets and their latest status.
| Name | Type | Req | Description |
|---|---|---|---|
| status | string | – | – |
| tags | array | – | – |
No output schema declared.
No examples provided.
list_gitlab_pipelines List GitLab Pipelines ~36
List registered GitLab pipeline targets and their latest status.
| Name | Type | Req | Description |
|---|---|---|---|
| status | string | – | – |
| tags | array | – | – |
No output schema declared.
No examples provided.
list_http_targets List HTTP Targets ~38
List registered HTTP targets and their latest status, response, and TLS summary.
| Name | Type | Req | Description |
|---|---|---|---|
| status | string | – | – |
| tags | array | – | – |
No output schema declared.
No examples provided.
list_servers List Registered Servers ~32
List all registered MCP servers with their current status.
| Name | Type | Req | Description |
|---|---|---|---|
| status | string | – | – |
| tags | array | – | – |
No output schema declared.
No examples provided.
register_github_actions Register GitHub Actions Workflow ~154
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.
| Name | Type | Req | Description |
|---|---|---|---|
| branch | string | – | Optional branch filter for workflow runs |
| check_interval_minutes | integer | – | – |
| name | string | yes | Unique local name for this GitHub Actions target |
| owner | string | yes | GitHub user or organization |
| repository | string | yes | GitHub repository name |
| tags | array | – | Tags for grouping |
| token_env | string | – | Environment variable containing a GitHub token; the token value is never persisted |
| workflow | string | yes | Workflow numeric ID or .yml/.yaml filename |
No output schema declared.
No examples provided.
register_gitlab_pipeline Register GitLab Pipeline ~164
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.
| Name | Type | Req | Description |
|---|---|---|---|
| base_url | string | – | GitLab HTTPS origin; self-hosted origins require HEALTH_MONITOR_GITLAB_BASE_URL_ALLOWLIST |
| check_interval_minutes | integer | – | – |
| name | string | yes | Unique local name for this GitLab pipeline target |
| project | string | yes | Numeric project ID or namespace/project path |
| ref | string | – | Optional branch or tag filter |
| tags | array | – | Tags for grouping |
| token_env | string | – | Environment variable containing a GitLab token; the token value is never persisted |
No output schema declared.
No examples provided.
register_http_target Register HTTP Target ~53
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
register_server Register MCP Server ~48
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
set_alert Set Alert Thresholds ~73
Configure alert thresholds for response time, uptime, and consecutive failures.
| Name | Type | Req | Description |
|---|---|---|---|
| consecutive_failures_before_alert | integer | – | – |
| max_response_time_ms | integer | – | Alert if response time exceeds this |
| min_uptime_percent | number | – | Alert if uptime drops below this |
| name | string | yes | Server name |
No output schema declared.
No examples provided.
unregister_github_actions Unregister GitHub Actions Workflow ~30
Remove a GitHub Actions workflow target and its stored check history.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
No output schema declared.
No examples provided.
unregister_gitlab_pipeline Unregister GitLab Pipeline ~29
Remove a GitLab pipeline target and its stored check history.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
No output schema declared.
No examples provided.
unregister_http_target Unregister HTTP Target ~26
Remove an HTTP target and its stored check history.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
No output schema declared.
No examples provided.
unregister_server Unregister Server ~21
Remove a server from monitoring.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
No output schema declared.
No examples provided.
How do I install the MCP Health Monitor server?
MCP Health Monitor runs locally as an npm package, launched with npx -y health-monitor-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · health-monitor-mcp
claude mcp add oaslananka-health-monitor-mcp -- npx -y health-monitor-mcp
What is the MCP Health Monitor server?
MCP Health Monitor is listed in the public MCP registry as io.github.oaslananka/health-monitor-mcp. Monitor MCP, CI, and HTTP targets with health history, TLS expiry, assertions, and diagnostics. This page covers its npm package (health-monitor-mcp).
Is the MCP Health Monitor server safe to use?
MCP Health Monitor scores 86 out of 100 on VerifyMCP. We recorded 8 known advisories against it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the MCP Health Monitor server expose?
MCP Health Monitor exposes 22 tools: register_github_actions, check_github_actions, list_github_actions, unregister_github_actions, register_gitlab_pipeline, and 17 more. Their descriptions and schemas cost roughly 1,182 tokens of context every time the server is loaded.
Is the MCP Health Monitor server still maintained?
MCP Health Monitor is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the MCP Health Monitor server under?
MCP Health Monitor declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.