io.github.dbsectrainer/mcp-server-health-monitor
io.github.dbsectrainer/mcp-server-health-monitor
Is the io.github.dbsectrainer/mcp-server-health-monitor MCP server down? Yes. It has given no valid answer since 2026-10-18: crashed on start.
Health monitoring for all your MCP servers
crashed on start down since 2026-10-18 · probed 2026-11-15 · unchanged since 2026-11-08
MCP error -32000: Connection closed
'/work/node_modules/better-sqlite3/addon-build/default/install-root/better_sqlite3.node',
'/work/node_modules/better- Run it
- npx -y mcp-server-health-monitor@1.0.1 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Repository
- https://github.com/dbsectrainer/mcp-server-health-monitor
- Registry
- active, updated 2026-11-04 · registry entry
Compare this server with others.
More servers
Other registry entries on npmjs.com, the ones next to this name; all of them.
- io.github.dbsectrainer/mcp-cost-tracker-router · crashed on start
- io.github.dbsectrainer/mcp-data-pipeline-connector · alive
- io.github.dbsectrainer/mcp-eval-runner · alive
- io.github.dbsectrainer/mcp-legal-doc-analyzer · crashed on start
- The Poliety io.github.dburks-svg/poliety · alive
- io.github.dcd887/mc-changelog · alive
- io.github.dcd887/mc-mod-config · alive
- io.github.dcd887/mc-modpack · 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-18, in every probe since then.
- The process exited on start before it answered initialize. The error output is above.