Health Monitor MCP Server

Health monitoring for all your MCP servers

Remote serverstreamable-http

What is the Health Monitor MCP Server?

Health monitoring for all your MCP servers

What you get

MCP-native health monitoring that speaks the protocol, not just HTTP. Instead of pinging a port, it calls list_tools on each server — the same handshake your agent uses — so a green status means the server is actually ready to serve MCP requests. All health history stays local in SQLite; no external monitoring service required.

  • Auto-discovery — Reads your existing MCP config files (Claude Desktop, Cursor, VS Code) with no extra setup
  • Non-intrusive probing — Only calls list_tools on target servers — read-only, no side effects
  • Version drift detection — Compares tool schemas across checks to detect when a server has been updated
  • Historical trends — Stores latency history in SQLite; p50/p95 are computed on-demand from stored history to surface regressions before they become outages
  • HTML dashboard — Generates a self-contained health dashboard with uptime sparklines per server
  • Background polling — Runs as a daemon so health data is always fresh when you ask for it

Configuration and credentials

  • Node.js v20.19 or newer. - npm.

More MCP options

Compare MCP servers by category, or browse hosted MCP servers if you prefer an endpoint over a local process.

Maintainer setup documentation.

Recorded tools

Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.

ToolWhat it does
health_check_allprobes all configured servers in parallel via list_tools, measures latency, and stores results. Accepts an optional timeout_ms parameter (default: 5000).
get_server_statusreturns per-server detail including latency, last seen time, 24-hour error count, last error message, and p50/p95 latency percentiles. Requires server_name.
list_degradedfilters to servers that are offline or have latency above the threshold. Accepts an optional latency_threshold override.
configure_serverregisters a new MCP server to monitor. Servers added this way are stored in ~/.mcp/extra-servers.json and merged with auto-discovered servers. Required: name, command. Optional: args, env.
remove_serverremoves a manually registered server from monitoring. Only affects servers added via configure_server; auto-discovered servers are not affected. Requires name.

How to install the Health Monitor MCP Server

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

Configuration as documented by the project. Restart the client after saving.

Configuration

  • Node.js v20.19 or newer. - npm.

Example prompts to try

  • “Use Health Monitor to health check all.”
  • “Use Health Monitor to get server status.”
  • “Use Health Monitor to list degraded.”

Frequently asked questions

Health monitoring for all your MCP servers Confirm the tools offered by your installed version in the connected client. Tool availability and permissions depend on the server and account configuration.