MCP Uptime Kuma vs Mcpuptimeledger MCP

A side-by-side look at the MCP Uptime Kuma and Mcpuptimeledger MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

MCP Uptime Kuma logoMCP Uptime KumaMonitoring · Local subprocess (stdio)A Model Context Protocol (MCP) server for Uptime Kuma version 2.61GoodAuth: otherMcpuptimeledger MCP logoMcpuptimeledger MCPMonitoring · Remote HTTP/SSEMCP uptime, schema, auth, and SLA receipt monitoring.45FairAuth: not declared

Verdict: choose MCP Uptime Kuma for monitoring work as a local process; choose Mcpuptimeledger MCP for monitoring over a hosted endpoint. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

MCP Uptime Kuma logoChoose MCP Uptime Kuma when

  • You need dedicated capabilities in the Monitoring domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: other.
  • You have the keys it needs: UPTIME_KUMA_URL, UPTIME_KUMA_USERNAME, UPTIME_KUMA_PASSWORD, UPTIME_KUMA_2FA_TOKEN, UPTIME_KUMA_JWT_TOKEN, UPTIME_KUMA_HEADERS.
  • You want tools like getMonitorSummary, listMonitors, listMonitorTypes.
Explore MCP Uptime Kuma

Mcpuptimeledger MCP logoChoose Mcpuptimeledger MCP when

  • You need dedicated capabilities in the Monitoring domain.
  • You prefer a remote HTTP/SSE transport.
  • You want tools like check_mcp_server_uptime, validate_tool_schema, detect_auth_failure.
Explore Mcpuptimeledger MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecMCP Uptime Kuma logoMCP Uptime KumaMcpuptimeledger MCP logoMcpuptimeledger MCP
CategoryMonitoringMonitoring
Quality signal61/100 · Good45/100 · Fair
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Remote HTTP/SSE
AuthotherNot declared
PricingFreeNot declared
Required env varsUPTIME_KUMA_URLUPTIME_KUMA_USERNAMEUPTIME_KUMA_PASSWORDUPTIME_KUMA_2FA_TOKENUPTIME_KUMA_JWT_TOKENUPTIME_KUMA_HEADERSNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars600
Directory activity 2 views 0 installs 0 upvotes 0 views 0 installs 0 upvotes
Tools265

Tools & capabilities

MCP Uptime Kuma tools 26

  • getMonitorSummaryGet a quick overview of all monitors with their current status. Supports filtering.
  • listMonitorsGet the full list of all monitors with configurations. Supports filtering.
  • listMonitorTypesGet all available monitor types supported by Uptime Kuma.
  • getMonitorGet detailed configuration for a specific monitor by ID.
  • createMonitorCreate a new monitor (requires name and type at minimum).
  • updateMonitorUpdate an existing monitor's configuration.
  • deleteMonitorPermanently delete a monitor and all its heartbeat history.
  • pauseMonitorPause a monitor to stop performing checks.
  • resumeMonitorResume a paused monitor to restart checks.
  • listHeartbeatsGet status check history for all monitors.
  • getHeartbeatsGet status check history for a specific monitor.
  • listNotificationsList all configured notification channels (Slack, Discord, email, webhooks, etc.).
  • +14 more on the listing page

Mcpuptimeledger MCP tools 5

  • check_mcp_server_uptime
  • validate_tool_schema
  • detect_auth_failure
  • issue_sla_receipt
  • export_status_report

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

MCP Uptime Kuma

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "mcp-uptime-kuma": {
      "command": "npx",
      "args": [
        "-y",
        "@davidfuchs/mcp-uptime-kuma@latest"
      ],
      "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"
      }
    }
  }
}

Mcpuptimeledger MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "mcpuptimeledger-mcp": {
      "url": "https://mcpuptimeledger.clauxel.com/mcp"
    }
  }
}

Frequently asked questions

MCP Uptime Kuma is categorized under Monitoring and uses a local stdio subprocess. Mcpuptimeledger MCP belongs to Monitoring and uses a remote HTTP/SSE transport. Pick MCP Uptime Kuma for monitoring work and Mcpuptimeledger MCP for monitoring.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

MCP Uptime Kuma is listed as free. Auth: other. Mcpuptimeledger MCP has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add mcp-uptime-kuma and mcpuptimeledger-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, MCP Uptime Kuma has a quality signal of 61/100 (Good) with 2 views, 0 installs and 60 GitHub stars. Mcpuptimeledger MCP has 45/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.