io.github.oaslananka/mcp-health-monitor
MCP Health Monitor
Is the MCP Health Monitor MCP server down? Yes. It has given no valid answer since 2026-10-16: not found.
Monitor MCP server health, uptime, response times, and Azure DevOps pipeline status
not found down since 2026-10-16 · probed 2026-11-15 · unchanged since 2026-10-30
npm error notarget In most cases you or one of your dependencies are requesting npm error notarget a package version that doesn't exist. npm error A complete lo
- Run it
- npx -y mcp-health-monitor@1.0.2 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Repository
- https://github.com/oaslananka/mcp-health-monitor
- Registry
- active, updated 2026-04-08 · registry entry
Compare this server with others.
More servers
Other registry entries on npmjs.com, the ones next to this name; all of them.
- MCP Health Monitor io.github.oaslananka/health-monitor-mcp · alive
- io.github.oaslananka/infra-lens-mcp · alive
- KiCad MCP Pro io.github.oaslananka/kicad-mcp-pro · needs env
- MCP Debug Recorder io.github.oaslananka/mcp-debug-recorder · not found
- io.github.oaslananka/mcp-infra-lens · not found
- SSH MCP Tool io.github.oaslananka/mcp-ssh-tool · not found
- MCP Sentinel io.github.oaslananka/sentinel · not found
- ssh-mcp-pro io.github.oaslananka/ssh-mcp-pro · alive
Servers that mention monitor.
- Agentic News ai.agentic-news/mcp · needs auth
- ASRM (AI Search Rank Monitor) ai.asrm/asrm · alive
- ai.getvda/dynamic-health-monitor · newer protocol
- ai.getvda/kafka-and-postgres-monitoring-stack · newer protocol
- Orq.ai ai.orq/orq · needs auth
- Patent Data ai.patentdata/patent-data · needs auth
- ai.openhelm/monitoring · needs auth
- smry Product ai.smry.r/smry-product · alive
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- No valid answer since 2026-10-16, in every probe since then.
- The endpoint answers HTTP 404. The registry entry points to a URL that is not an MCP endpoint any more. Publish a new version of the registry entry with the current URL.