MCP Uptime Kuma vs NotWorking
A side-by-side look at the MCP Uptime Kuma and NotWorking MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
N
NotWorkingMonitoringDowndetector for AI agents: is a site, MCP server or skill failing for everyone? Check and report.53GoodAuth: no auth requiredVerdict: choose MCP Uptime Kuma for monitoring work as a local process; choose NotWorking for monitoring. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose MCP Uptime Kuma when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a local stdio subprocess transport.
- 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.
NChoose NotWorking when
- You need dedicated capabilities in the Monitoring domain.
- Its auth model fits you: No auth required.
- You want tools like
check_status, report.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | N NotWorking | |
|---|---|---|
| Category | Monitoring | Monitoring |
| Quality signal | 60/100 · Good | 53/100 · Good |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | UPTIME_KUMA_URLUPTIME_KUMA_USERNAMEUPTIME_KUMA_PASSWORDUPTIME_KUMA_2FA_TOKEN |
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
NotWorking tools 2
check_statusIs it down or blocking agents for everyone, or just you? Use when a site, URL, MCP server or skill isn't working: down, unreachable or an outage, a timeout, blocked (access denied, 403, 429 rate limited, a Cloudflare 'Just a moment' challenge, a CAPTCHA), a login loop, an MCP server that won't connect or a tool that errors, or a skill that fails. Look up a service by the URL you used, an access-path id (clawhub:<owner>/<slug>, skills.sh:<owner>/<repo>/<skill>, an MCP Registry name like io.github.<owner>/<server>) or a service name. Returns a one-sentence summary, the service, every listed access path with a description and failure reports from the last hour (and the last 24 hours as context), the what_failed values and how to report. Unlisted targets return their own counts and status, with listed: false.
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": {
"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"
}
}
}
}
NotWorking
No confirmed install command for NotWorking yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
MCP Uptime Kuma is categorized under Monitoring and uses a local stdio subprocess. NotWorking belongs to Monitoring and uses an install path we have not confirmed yet. Pick MCP Uptime Kuma for monitoring work and NotWorking 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. NotWorking has no confirmed install command yet — follow its own setup instructions.
MCP Uptime Kuma has no declared pricing — check the project's own site. NotWorking is listed as free. Auth: no auth required. 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 notworking 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 60/100 (Good) with 1 views, 0 installs and 55 GitHub stars. NotWorking has 53/100 (Good) with 0 views, 0 installs and 2 GitHub stars.
