Skills/npm/mcp-uptime-kuma

mcp-uptime-kuma@0.17.0

VERIFIED· startup only

Publisher claims: "A Model Context Protocol (MCP) server for Uptime Kuma version 2, supporting both stdio and streamable HTTP transports." Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry npm (MCP server)Publisher davidfuchs · publishing for 364 daysInstalls 4,716Last detonated 6 h ago
$claude mcp add mcp-uptime-kuma -- npx -y @davidfuchs/mcp-uptime-kuma
WatchReport an issue

Coverage

Startup only; authenticated tool behavior not tested.
Tested
server startup over stdio (initialize sent) · every file read, file written and host contacted by what ran
Not tested
the tool list (the server exited before answering) · what the tools do when called with real credentials

What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.

Before you give it your token

It will ask for
MCP_AUTH_TOKENUPTIME_KUMA_2FA_TOKENUPTIME_KUMA_INCLUDE_SECRETSUPTIME_KUMA_JWT_TOKENUPTIME_KUMA_PASSWORDConfiguration, not credentials: ALLOWED_ORIGIN, MCP_TEST_MODE, RATE_LIMIT_MAX, TRUST_PROXY, UPTIME_KUMA_DYNAMIC_TOOLSETS, UPTIME_KUMA_HEADERS, UPTIME_KUMA_READ_ONLY, UPTIME_KUMA_TOOLSETS, UPTIME_KUMA_URL, UPTIME_KUMA_USERNAME
Where it talks to
no vendor host named in the codeAlso ntfy.sh, telegram.org, matrix.org, pagerduty.com — not the publisher's domain; check what for before connecting.
What we saw when it ran
no credential files read · no network
What we could not test
the tool list (the server exited before answering) · what the tools do when called with real credentials

Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names ntfy.sh, telegram.org, matrix.org, pagerduty.com as well as its own vendor. The guard injects MCP_AUTH_TOKEN, UPTIME_KUMA_2FA_TOKEN, UPTIME_KUMA_INCLUDE_SECRETS, UPTIME_KUMA_JWT_TOKEN, UPTIME_KUMA_PASSWORD only into requests to the host you bind (and its subdomains) and refuses the rest.

$vet-skills run --net declared -- npx -y @davidfuchs/mcp-uptime-kuma

Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.

What changed since 0.16.0

vet-skills diff mcp-uptime-kuma 0.16.0 0.17.0

In the sandbox, this version reached for nothing 0.16.0 did not. Compared from the two recorded runs, not from source.

No longer contacted
slack.com

The guard can hold an update like this until someone approves it (runtime.on_change: hold). A change that only shows with a real credential, or on a path the run did not reach, is not in a trace and so not in this comparison.

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; startup only; authenticated tool behavior not tested) on 2026-11-19 and scored it 80/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 36 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
15sprocessdependency install exit 0
35sclaimedstartup only: exited (0) before answering · code: 'ERR_MODULE_NOT_FOUND', url: 'file:///tmp/ks-detonate-aoLqsO/task/home/work/acme-api/.claude/skills/mcp-uptime-kuma/dist/tools/dynamic-toolsets.js' } Node.js v22.23.5
35sprocessscript backend runs setup only
35sprocessno install scripts to re-run

Static findings

HIGH
URL with embedded credentialsdist/redact.d.ts:46 · URL with embedded credentials — may be phishing or credential leaking* monitor's own URL mid-sentence ("connect ETIMEDOUT to http://admin:s3cret@host"). OneFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST07
HIGH
URL with embedded credentialsdist/redact.js:90 · URL with embedded credentials — may be phishing or credential leaking* monitor's own URL mid-sentence ("connect ETIMEDOUT to http://admin:s3cret@host"). OneFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST07
HIGH
URL with embedded credentialsdist/monitors/rules.js:278 · URL with embedded credentials — may be phishing or credential leaking* `https://***:***@host`. `rehydrateSecrets` skips arrays and only recognises a bare "***"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST07
HIGH
URL with embedded credentialsdist/monitors/rules.js:277 · URL with embedded credentials — may be phishing or credential leaking* Each node is a URL, and `redactUrlCredentials` turns `https://user:pass@host` intoFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST07
HIGH
URL with embedded credentialsdist/redact.d.ts:126 · URL with embedded credentials — may be phishing or credential leaking* `redactUrlCredentials` turns `http://user:pass@host` into `http://***:***@host`, and thatFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST07
HIGH
URL with embedded credentialsdist/redact.d.ts:139 · URL with embedded credentials — may be phishing or credential leaking* nothing is restored. Otherwise `http://***:***@somewhere-else` would send a password theFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST07
HIGH
Access to sensitive file pathsdist/index.js:3 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files// This allows tests to pass environment variables directly without .env file interferenceFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsdist/index.js:2 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files// Load .env file only if not in test mode (when MCP_TEST_MODE is set)Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
URL with embedded credentialsdist/monitors/rules.d.ts:52 · URL with embedded credentials — may be phishing or credential leaking* Each node is a URL, and `redactUrlCredentials` turns `https://user:pass@host` intoFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST07
HIGH
URL with embedded credentialsdist/monitors/rules.d.ts:53 · URL with embedded credentials — may be phishing or credential leaking* `https://***:***@host`. `rehydrateSecrets` skips arrays and only recognises a bare "***"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST07
HIGH
URL with embedded credentialsdist/redact.js:318 · URL with embedded credentials — may be phishing or credential leaking* `redactUrlCredentials` turns `http://user:pass@host` into `http://***:***@host`, and thatFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST07
MEDIUM
npx invocation of non-well-known packagedist/index.js:130 · npx invocation of non-well-known package — may execute untrusted code// The client closing our stdin is the reliable signal here: a wrapper like npx can beFix: Pin versions and sources; vendor anything fetched at install time.
AST06
HIGH
URL with embedded credentialsdist/redact.js:331 · URL with embedded credentials — may be phishing or credential leaking* nothing is restored. Otherwise `http://***:***@somewhere-else` would send a password theFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST07
MEDIUM
Process kill commanddist/index.js:156 · Process kill command — agent can terminate processes// A startup auth failure must NOT kill the process. Uptime Kuma being brieflyFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.
AST05
HIGH
URL with embedded credentialsdist/tools/docker-hosts.js:26 · URL with embedded credentials — may be phishing or credential leaking// A TCP dockerDaemon can be http://user:pass@host:2375 — the field name gives noFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST07

Cost to the agent

Instructions loaded
≈70 tok
1 file · 81 in bundle
Tool list per prompt
≈0 tok
0 tools · 0 per tool
Handshake
no reply
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 0

Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.

Known vulnerabilities

No advisories in OSV for @davidfuchs/mcp-uptime-kuma@0.17.0 as of 6 h ago. This is the package itself, not its dependencies.