What is the key difference between Healthchecks IO MCP and MCP Uptime Kuma?

Healthchecks IO MCP 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 Healthchecks IO MCP 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 Healthchecks IO MCP and MCP Uptime Kuma free or paid?

Healthchecks IO MCP 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?

Healthchecks IO MCP lists 6 tools with 1 views and 0 GitHub stars. MCP Uptime Kuma lists 22 tools with 1 views and 54 GitHub stars.

Can I use both Healthchecks IO MCP 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

Healthchecks IO MCP vs MCP Uptime Kuma

In-depth architectural comparison of the Healthchecks IO MCP 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

Healthchecks IO MCP

Monitoring · Local stdio

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

MCP Uptime Kuma

Monitoring · Local stdio

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

Verdict Summary: Choose Healthchecks IO MCP 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 Healthchecks IO MCP 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: HEALTHCHECKS_API_KEY, HEALTHCHECKS_BASE_URL.
Primary tools included: List and inspect Healthchecks.io checks, Review ping history and status flips, Manage notification integrations and badge URLs.

Explore Healthchecks IO MCP 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.

Feature & Specification Comparison

Specification	Healthchecks IO MCP Monitoring	MCP Uptime Kuma Monitoring
Summary	Unofficial MCP server for managing Healthchecks.io checks via the Management API	A Model Context Protocol (MCP) server for Uptime Kuma version 2.
Category & Scope	Monitoring	Monitoring
Quality signal

Tools & Capabilities Breakdown

Healthchecks IO MCP Tools (6)

List and inspect Healthchecks.io checks

Review ping history and status flips

Manage notification integrations and badge URLs

Create and update checks

Pause, resume, or permanently delete checks

Connect to hosted or self-hosted API endpoints

MCP Uptime Kuma Tools (22)

getMonitorSummary

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).

Healthchecks IO MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "healthchecks-io-mcp": {
      "command": "npx",
      "args": [
        "@digitalronin/healthchecks-io-mcp"
      ],
      "env": {
        "HEALTHCHECKS_API_KEY": "YOUR_HEALTHCHECKS_API_KEY_HERE",
        "HEALTHCHECKS_BASE_URL": "YOUR_HEALTHCHECKS_BASE_URL_HERE"
      }
    }
  }
}

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

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

More alternatives to Healthchecks IO MCP More alternatives to MCP Uptime Kuma Monitoring category hub