What is the key difference between MCP Server Health Monitor and MCP Uptime Kuma?

MCP Server Health Monitor belongs to the Monitoring category with local stdio execution, while MCP Uptime Kuma belongs to the Monitoring category with local stdio execution.

How do I install MCP Server Health Monitor or MCP Uptime Kuma in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are MCP Server Health Monitor and MCP Uptime Kuma free or paid?

MCP Server Health Monitor operates under a Free / Open Source model (No auth required). MCP Uptime Kuma operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

MCP Server Health Monitor lists 8 tools with 0 views and 0 GitHub stars. MCP Uptime Kuma lists 22 tools with 1 views and 54 GitHub stars.

Can I use both MCP Server Health Monitor and MCP Uptime Kuma together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

MCP Server Health Monitor vs MCP Uptime Kuma

In-depth architectural comparison of the MCP Server Health Monitor and MCP Uptime Kuma MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

At a Glance & Executive Verdict

MCP Server Health Monitor

Monitoring · Local stdio

Quality: 49/100 (Fair) | Auth: No auth required

MCP Uptime Kuma

Monitoring · Local stdio

Quality: 60/100 (Good) | Auth: No auth required

Verdict Summary: Choose MCP Server Health Monitor if you need specialized Monitoring tools running via a local process. Choose MCP Uptime Kuma if your workspace requires Monitoring integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose MCP Server Health Monitor when:

You need dedicated capabilities in the Monitoring domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: health_check_all, get_server_status, list_degraded.

Explore MCP Server Health Monitor Details

Choose MCP Uptime Kuma when:

You need dedicated capabilities in the Monitoring domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
You have access to required keys: UPTIME_KUMA_URL, UPTIME_KUMA_USERNAME, UPTIME_KUMA_PASSWORD, UPTIME_KUMA_2FA_TOKEN, UPTIME_KUMA_JWT_TOKEN, UPTIME_KUMA_HEADERS.
Primary tools included: getMonitorSummary, listMonitors, listMonitorTypes.

Feature & Specification Comparison

Specification	MCP Server Health Monitor Monitoring	MCP Uptime Kuma Monitoring
Summary
Category & Scope	Monitoring	Monitoring
Quality signal

Tools & Capabilities Breakdown

MCP Server Health Monitor Tools (8)

health_check_all

probes all configured servers in parallel via `list_tools`, measures latency, and stores results. Accepts an optional `timeout_ms` parameter (default: 5000).

get_server_status

returns per-server detail including latency, last seen time, 24-hour error count, last error message, and p50/p95 latency percentiles. Requires `server_name`.

list_degraded

filters to servers that are offline or have latency above the threshold. Accepts an optional `latency_threshold` override.

get_history

returns raw health check history for a specific server, ordered most-recent first. Requires `server_name`; accepts optional `limit` (default: 50, max: 500).

configure_server

registers 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`.

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

MCP Server Health Monitor Configuration

mcpServers (Claude Desktop / Cursor)

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

MCP Uptime Kuma Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "mcp-uptime-kuma": {
      "command": "npx",
      "args": [
        "-y",
        "-p",
        "@davidfuchs/mcp-uptime-kuma",
        "mcp-uptime-kuma-get-jwt"
      ],
      "env": {
        "UPTIME_KUMA_URL": "YOUR_UPTIME_KUMA_URL_HERE",
        "UPTIME_KUMA_USERNAME": "YOUR_UPTIME_KUMA_USERNAME_HERE",
        "UPTIME_KUMA_PASSWORD": "YOUR_UPTIME_KUMA_PASSWORD_HERE",
        "UPTIME_KUMA_2FA_TOKEN": "YOUR_UPTIME_KUMA_2FA_TOKEN_HERE",
        "UPTIME_KUMA_JWT_TOKEN": "YOUR_UPTIME_KUMA_JWT_TOKEN_HERE",
        "UPTIME_KUMA_HEADERS": "YOUR_UPTIME_KUMA_HEADERS_HERE"
      }
    }
  }
}

Frequently Asked Questions

MCP Server Health Monitor is categorized under Monitoring and uses a local stdio subprocess. In contrast, MCP Uptime Kuma belongs to Monitoring using local stdio subprocess. Select MCP Server Health Monitor when you need capabilities focused on monitoring and MCP Uptime Kuma when you require tools for monitoring.

More alternatives to MCP Server Health Monitor More alternatives to MCP Uptime Kuma Monitoring category hub