mcp-uptime-kuma@0.16.0
CAUTION· startup onlyPublisher 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.
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: Caution 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_HEADERS, UPTIME_KUMA_READ_ONLY, 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, slack.com — not the publisher's domain; check what for before connecting.
- What the honeypot saw
- 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, slack.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.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
What changed since 0.15.0
vet-skills diff mcp-uptime-kuma 0.15.0 0.16.0This version reaches for something 0.15.0 did not: 5 new hosts (matrix.org, ntfy.sh, pagerduty.com, slack.com, …). Compared from the two recorded runs, not from source.
- New hosts
- matrix.org, ntfy.sh, pagerduty.com, slack.com, telegram.org
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-16 and scored it 77/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Access to sensitive file paths; Slack webhook URL; URL with embedded credentials. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 38 s · 2 scenarios · 0 deviationsStatic findings
// 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..describe('The fields of this notification type, e.g. {"slackwebhookURL": "https://hooks.slack.com/…"} for slack. Call getNotificationTypeFields for the names.'),Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.* `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.* 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.// 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.* `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.* 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.// 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.* `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.* `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.* 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.// 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.* 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.* 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.* 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.// 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.Cost to the agent
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
Not checked against OSV yet; the weekly check has not reached this version.
What would make this Verified
3 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim davidfuchs: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- Access to sensitive file paths≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
- Slack webhook URL≈ +4 on the totalRemove the call, or declare the host in frontmatter and explain in the README what is sent and why.
- URL with embedded credentials≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
- npx invocation of non-well-known package≈ +2 on the totalPin versions and sources; vendor anything fetched at install time.
- Process kill command≈ +2 on the totalBuild commands from fixed arguments; do not interpolate untrusted strings into a shell.