io.github.oaslananka/mcp-health-monitor

MCPcommunity
v1.0.2io.github.oaslanankaUnknownUpdated 5mo agonpmGitHub

Monitor MCP server health, uptime, response times, and Azure DevOps pipeline status

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
5mo agoLast update
Package
Authorio.github.oaslananka
LicenseUnknown
Version1.0.2
Sourcemcp-registry
npmmcp-health-monitor
GitHuboaslananka/mcp-health-monitor
SBOMCycloneDX 1.6 ↓
Trust Status
F
10/100Untrusted
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
—CVE scan · not run+0/30
→ Our scan didn't complete — a retry is queued. Nothing to fix on your side.
—Static analysis · clean+0/20
→ Our scan didn't complete — a retry is queued. Nothing to fix on your side.
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
DependenciesNot audited
Tool surface—
Security scanScan failedvunknown · 1mo agoHow well does this scan work?
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

Source never read1mo ago

This entry has been scanned, but the run carries no source-extraction result — either it predates tool-surface extraction or it failed before reaching that stage. A rescan is what would fill this in; the blank says nothing about the package.

About

Monitor MCP server health, uptime, response times, and Azure DevOps pipeline status

Keywords
mcp
Alternatives
Comparing tool surfaces…

No dependency coverage

The last scan of this package failed, so no dependency tree was resolved.

Topics

Related in health & fitness