MCP Health Monitor MCP server

by oaslananka·io.github.oaslananka/health-monitor-mcp·v1.4.0·2 stars

No reviews yet

Monitor MCP, CI, and HTTP targets with health history, TLS expiry, assertions, and diagnostics

B75/100grade B

Write a review Install

What users say

No reviews yet

Be the first

Safety scan

B75/100

full report

Adoption

Growing

2 stars258 downloads/wk

Reviews

Write one

Nobody has reviewed MCP Health Monitor yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

MCP Health Monitor tools (22, 4 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

check_all
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.
check_github_actions
Check the latest run for a registered GitHub Actions workflow and return failed job and step diagnostics.
check_gitlab_pipeline
Check the latest registered GitLab pipeline and return failed job, stage, ref, commit, URL, and bounded trace diagnostics.
check_http_target
Check a registered HTTP target with DNS-pinned SSRF protection, bounded redirects/body reads, response assertions, and TLS-expiry diagnostics.
check_server
Check the health of a registered MCP server, list tools, and measure response time.
get_dashboard
Get a dashboard overview of registered MCP servers, GitHub Actions workflows, GitLab pipelines, and HTTP targets with uptime and performance stats.
get_monitor_stats
Get statistics about the health monitor itself, including database activity.
get_report
Get a human-readable Markdown health report for MCP servers, GitHub Actions workflows, GitLab pipelines, and HTTP targets. Paste directly into chat or docs.
get_uptime
Get uptime history and statistics for a registered MCP server.
list_github_actions
List registered GitHub Actions workflow targets and their latest status.
list_gitlab_pipelines
List registered GitLab pipeline targets and their latest status.
list_http_targets
List registered HTTP targets and their latest status, response, and TLS summary.
list_servers
List all registered MCP servers with their current status.
register_github_actions
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.
register_gitlab_pipeline
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.
register_http_target
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.
register_server
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.
set_alert
Configure alert thresholds for response time, uptime, and consecutive failures.
unregister_github_actionswrite action
Remove a GitHub Actions workflow target and its stored check history.
unregister_gitlab_pipelinewrite action
Remove a GitLab pipeline target and its stored check history.
unregister_http_targetwrite action
Remove an HTTP target and its stored check history.
unregister_serverwrite action
Remove a server from monitoring.

Public scan report

scanner v0.1.9 · 2026-09-25 · same rubric, same numbers if you re-run it

no findings

Code scan65 source files scanned25/25
–Live reliabilityno gateway calls yet and no remote to proben/a
–Tool poisoningtools not inspected (local package is not executed); not countedn/a
Auth qualitystatic API keys via environment variables6/15
Maintenancelast push 65 days ago12/15
Maintainer identityregistry namespace matches repository owner6/10

Overall 75/100. Components that don't apply are left out of the denominator. Any critical finding is an F.Rubric Appeal a finding JSON

How MCP Health Monitor compares

Against every graded Developer tools MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score: 75/100; higher than 40% of 1,119 Developer tools servers
Tools: 22; the typical Developer tools server has 7
Tools that change things: 18%; typical: 5%. Fewer write tools means less an agent can break
GitHub stars: 2; more than 65% of 855 Developer tools servers
Downloads a week: 258; more than 75% of 436 Developer tools servers with a package

What its tools let an agent do: 13 read · 4 create · 5 change

Install MCP Health Monitor in Claude Code, Cursor or VS Code

Runs npx -y health-monitor-mcp on your machine. Read the scan report first; the gateway never runs local packages.

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

Add to Cursor

What the publisher says

From the MCP Health Monitor repository's README, as published. We do not edit it. Read it on GitHub

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.

Quick Start

Run the published package noninteractively with Node.js 24:

npx -y health-monitor-mcp --version

Example MCP client configuration:

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

Tools

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

MCP Health Monitor: common questions

Is MCP Health Monitor MCP server safe?: Mostly: it is graded B (75/100). Read the MCP Health Monitor safety report
How do I install MCP Health Monitor?: It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does MCP Health Monitor need an API key?: Yes. The registry entry asks for GITHUB_TOKEN, GITLAB_TOKEN.
Is MCP Health Monitor maintained?: The last commit was 105 days ago (2026-07-22). The latest release is v1.4.0.
What can I use instead of MCP Health Monitor?: Servers from other publishers that do the same job: Repowise MCP server, Scrapling MCP Server and maintenant MCP server.
How does MCP Health Monitor compare with other Developer tools MCP servers?: safety score 75/100 (higher than 40% of 1,119 Developer tools servers); tools 22 (the typical Developer tools server has 7); tools that change things 18% (typical: 5%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to MCP Health Monitor

Same job from other publishers: the closest match first, then the best rated.

Repowise
Codebase intelligence for AI coding agents — graph, git history, docs, decisions, code health.
not reviewed
Established
B
Scrapling MCP Server
Web scraping with stealth HTTP, real browsers, and Cloudflare bypass. CSS selectors supported.
not reviewed
Widely used
A
maintenant
Docker monitoring for AI agents: logs, history, alerts. Can ack alerts; never touches containers.
not reviewed
Established
C
Observatory
MCP security scanner. CI-native testing, attack simulation, health scoring, and SARIF.
not reviewed
Established
B
SoloMD
Read and search a folder of Markdown notes: search, backlinks, tags, tasks, outlines, git history.
not reviewed
Established
B

Run it through the gateway

Local package. It runs on your machine, not through the gateway.

Rating: —
Safety grade: B · 75/100
Stars: 2
Downloads/wk: 258
Price: Free
Licence: MIT
Transport: Local · npm
Version: 1.4.0
Category: Developer tools
Last release: 2026-07-22

Credentials it needs

HEALTH_MONITOR_DBCustom path for the SQLite database
HEALTH_MONITOR_AUTO_CHECKSet to '1' to enable background scheduled checks
HEALTH_MONITOR_RETENTION_DAYSNumber of days to retain health check history
HEALTH_MONITOR_MAX_CONCURRENCYMaximum concurrent scheduled and interactive server checks
GITHUB_TOKENsecretOptional GitHub token with Actions read access for private repositories and higher API rate limits
GITLAB_TOKENsecretOptional GitLab token with read access to private projects, pipelines, jobs, and traces
HEALTH_MONITOR_GITLAB_BASE_URL_ALLOWLISTComma-separated self-hosted GitLab HTTPS origins allowed for monitoring
HEALTH_MONITOR_HTTP_TARGET_ALLOWLISTComma-separated private HTTP(S) origins allowed only in the full runtime profile

Own this server?

Claim it to keep the listing current and reply to reviews. Claiming never changes the grade or hides a review.

Claim listing

Badge for your README

Shows the safety grade and links back to this page. It updates itself after every scan and review.

[![mcp.market](https://mcp.market/badge/oaslananka-health-monitor-mcp.svg)](https://mcp.market/server/oaslananka-health-monitor-mcp)

How the badge works