Health Monitor MCP

Name: Health Monitor MCP
Availability: InStock
Author: oaslananka

Health Monitor keeps local registries of MCP servers, GitHub Actions workflows, GitLab pipelines and plain HTTP or HTTPS endpoints. Your agent can run live checks, read uptime and latency history, set alert thresholds for MCP servers and ask for a cross-provider dashboard or Markdown report. Failed GitHub jobs and steps are reported, and private repositories need a token with Actions read access. It suits anyone who wants an AI assistant to keep watch over their services and builds.

Written by ooruby from the README of health-monitor-mcp 1.4.0.

Not claimed by its maker. Is this yours? Prove it and answer the findings

Why it's useful

Your agent can report on the state of MCP servers, pipelines and endpoints from recorded checks, with the history kept for later questions.

What you could do with it

Register a production MCP server and ask your agent for its uptime and latency over the last 24 hours.
Monitor a GitHub Actions workflow and ask which job and step failed in the latest run.
Add a public health endpoint and have your agent check its response content and TLS certificate expiry.

Written from its documentation: what it says it can do, not what our checks found.

Maintenance

Not measured

No release date is on record for this package yet. The nightly publisher check records one as it reaches each npm package, about once every ten nights.

Release activity only: it says nothing about quality or safety, and a finished small package can be fine without releases. How it is measured

Not yet tested

What this does not cover

Everything. Treat it as you would software from anywhere else.

Receipt history: every signed receipt for every version of this listing, and what changed between them.

In its maker's words

Monitor MCP servers, CI workflows, and HTTP endpoints with health history, TLS expiry, response assertions, and diagnostics

Compare with

Compare all 4

How far this has been checked

Static scanned

What it establishes: Its published package, or for a hosted server its source repository at a recorded commit, was read file by file, without running it, by every check in our current scan.
What it does not: How it behaves when it runs, or anything the scan does not read yet: several rubric checks, the repository's history, and compiled code in folders named dist or build. For a hosted server, that the endpoint runs the code that was read. The ooruby Index sets out exactly what was read.
Exactly what was read: Version 1.4.0, the file with digest sha512-MB9dFYvflwdSWTxfiTa2Sopv6/IcXLYZWLYUSe+MaERUC+QL7GNQDGCMnbRhFb78Y4oYmaL0iZp8P9tRJ7Ulyw==, as the registry publishes it. A published version cannot be replaced, so this names the same bytes for anyone who checks.
Authentication: Runs locally. No hosted endpoint is listed for this package. You run it on your own machine, so there is no endpoint of ours to authenticate against.

How the rungs work

Adding it

Paste this into your client's MCP configuration.

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

Or run it directly.

npx -y -p health-monitor-mcp@1.4.0 health-monitor-mcp

Pinned to 1.4.0, which is the version the findings above were found in. Drop the version to take whatever is newest, and the report on this page stops describing what you installed.

Where this came from

Registry: npm
Package: health-monitor-mcp
Version read: 1.4.0
Resolved: 2026-10-10

Open the source

Built from source, attested

npm publishes a signed statement that this exact package was built from the repository below, at this commit. It is verifiable without taking our word for it.

Repository: github.com/oaslananka/health-monitor-mcp
Commit: 49eafde9c2a7
Built by: github.com/actions/runner/github-hosted
Registry publish attestation: signed by npm · 2026-10-10
Checked: 2026-10-10

The badge, if this is your listing

It renders the current rung (static scanned) and links back here, where what that does and does not establish is one click away. It updates itself as the evidence deepens.

[![ooruby: static scanned](https://ooruby.com/api/badge/health-monitor-mcp)](https://ooruby.com/market/health-monitor-mcp)

About this listing

Kind: MCP server
Category: Infrastructure
Pricing: Free
Sandbox: No
Hosted: No
Updated: 2026-10-08

Similar MCP servers

All MCP servers

3 findingsStatic scanned

Azure MCP

azure

Free

Gives your agent tools across many Azure services, from Key Vault and App Service to AI Search.

544.8k installs/moMIT

1 findingStatic scanned

Azure Devops MCP

azure-devops

Free

Lets your agent work with Azure DevOps projects, work items, repos, builds, test plans and wikis.

389.8k installs/moMIT

4 findingsStatic scanned

Hostinger Api MCP

devs_hostinger

Free

Lets your agent query the Hostinger API for datacentres, domain name ideas and Reach plan features.

526.4k installs/moMIT

Verification records what our published tests found on a specific version at a specific date. It is not a warranty, and it does not certify that software is free of defects.

Sign inSell

Health Monitor MCP

oaslananka · MCP server

Written by ooruby from the README of health-monitor-mcp 1.4.0.

Not claimed by its maker. Is this yours? Prove it and answer the findings

Why it's useful

Your agent can report on the state of MCP servers, pipelines and endpoints from recorded checks, with the history kept for later questions.

What you could do with it

Register a production MCP server and ask your agent for its uptime and latency over the last 24 hours.
Monitor a GitHub Actions workflow and ask which job and step failed in the latest run.
Add a public health endpoint and have your agent check its response content and TLS certificate expiry.

Written from its documentation: what it says it can do, not what our checks found.

Maintenance

Not measured

No release date is on record for this package yet. The nightly publisher check records one as it reaches each npm package, about once every ten nights.

Release activity only: it says nothing about quality or safety, and a finished small package can be fine without releases. How it is measured

Not yet tested

What this does not cover

Everything. Treat it as you would software from anywhere else.

Receipt history: every signed receipt for every version of this listing, and what changed between them.

In its maker's words

Monitor MCP servers, CI workflows, and HTTP endpoints with health history, TLS expiry, response assertions, and diagnostics

Compare with

Compare all 4

How far this has been checked

Static scanned

What it establishes: Its published package, or for a hosted server its source repository at a recorded commit, was read file by file, without running it, by every check in our current scan.
What it does not: How it behaves when it runs, or anything the scan does not read yet: several rubric checks, the repository's history, and compiled code in folders named dist or build. For a hosted server, that the endpoint runs the code that was read. The ooruby Index sets out exactly what was read.
Exactly what was read: Version 1.4.0, the file with digest sha512-MB9dFYvflwdSWTxfiTa2Sopv6/IcXLYZWLYUSe+MaERUC+QL7GNQDGCMnbRhFb78Y4oYmaL0iZp8P9tRJ7Ulyw==, as the registry publishes it. A published version cannot be replaced, so this names the same bytes for anyone who checks.
Authentication: Runs locally. No hosted endpoint is listed for this package. You run it on your own machine, so there is no endpoint of ours to authenticate against.

How the rungs work

Adding it

Paste this into your client's MCP configuration.

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

Or run it directly.

npx -y -p health-monitor-mcp@1.4.0 health-monitor-mcp

Pinned to 1.4.0, which is the version the findings above were found in. Drop the version to take whatever is newest, and the report on this page stops describing what you installed.

Where this came from

Registry: npm
Package: health-monitor-mcp
Version read: 1.4.0
Resolved: 2026-10-10

Open the source

Built from source, attested

npm publishes a signed statement that this exact package was built from the repository below, at this commit. It is verifiable without taking our word for it.

Repository: github.com/oaslananka/health-monitor-mcp
Commit: 49eafde9c2a7
Built by: github.com/actions/runner/github-hosted
Registry publish attestation: signed by npm · 2026-10-10
Checked: 2026-10-10

The badge, if this is your listing

It renders the current rung (static scanned) and links back here, where what that does and does not establish is one click away. It updates itself as the evidence deepens.

[![ooruby: static scanned](https://ooruby.com/api/badge/health-monitor-mcp)](https://ooruby.com/market/health-monitor-mcp)

About this listing

Kind: MCP server
Category: Infrastructure
Pricing: Free
Sandbox: No
Hosted: No
Updated: 2026-10-08

Similar MCP servers

All MCP servers

3 findingsStatic scanned

Azure MCP

azure

Free

Gives your agent tools across many Azure services, from Key Vault and App Service to AI Search.

544.8k installs/moMIT

1 findingStatic scanned

Azure Devops MCP

azure-devops

Free

Lets your agent work with Azure DevOps projects, work items, repos, builds, test plans and wikis.

389.8k installs/moMIT

4 findingsStatic scanned

Hostinger Api MCP

devs_hostinger

Free

Lets your agent query the Hostinger API for datacentres, domain name ideas and Reach plan features.

526.4k installs/moMIT

Verification records what our published tests found on a specific version at a specific date. It is not a warranty, and it does not certify that software is free of defects.