Mcpuptimeledger MCP vs MCP Uptime Kuma

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

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

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

Which MCP server should you choose?

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

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

Feature & specification comparison

Rows where the two servers differ are marked.

SpecMcpuptimeledger MCP logoMcpuptimeledger MCPMCP Uptime Kuma logoMCP Uptime Kuma
CategoryMonitoringMonitoring
Quality signal45/100 · Fair61/100 · Good
Install commandConfirmedConfirmed
TransportRemote HTTP/SSELocal subprocess (stdio)
AuthNot declaredother
PricingNot declaredFree
Required env varsNone listedUPTIME_KUMA_URLUPTIME_KUMA_USERNAMEUPTIME_KUMA_PASSWORDUPTIME_KUMA_2FA_TOKENUPTIME_KUMA_JWT_TOKENUPTIME_KUMA_HEADERS
Verified ownerCommunity listingCommunity listing
GitHub stars060
Directory activity 0 views 0 installs 0 upvotes 2 views 0 installs 0 upvotes
Tools526

Tools & capabilities

Mcpuptimeledger MCP tools 5

  • check_mcp_server_uptime
  • validate_tool_schema
  • detect_auth_failure
  • issue_sla_receipt
  • export_status_report

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

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.

Mcpuptimeledger MCP

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

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"
      }
    }
  }
}

Frequently asked questions

Mcpuptimeledger MCP is categorized under Monitoring and uses a remote HTTP/SSE transport. MCP Uptime Kuma belongs to Monitoring and uses a local stdio subprocess. Pick Mcpuptimeledger MCP for monitoring work and MCP Uptime Kuma 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.

Mcpuptimeledger MCP has no declared pricing — check the project's own site. MCP Uptime Kuma is listed as free. Auth: other. 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 mcpuptimeledger-mcp and mcp-uptime-kuma as separate keys in the same mcpServers object, and your assistant will call tools from either one.

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