mcp-uptime-kuma@0.15.0
VERIFIED· 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: 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_HEADERS, UPTIME_KUMA_READ_ONLY, UPTIME_KUMA_URL, UPTIME_KUMA_USERNAME- Where it talks to
- no vendor host named in the code
- 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. It asks for MCP_AUTH_TOKEN, UPTIME_KUMA_2FA_TOKEN, UPTIME_KUMA_INCLUDE_SECRETS, UPTIME_KUMA_JWT_TOKEN, UPTIME_KUMA_PASSWORD and talks to its vendor. Give the credential to the guard, not the server: the value never enters the server's environment and only travels to the host you bind. What the tools do with a real credential was not observed.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
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-14 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 · 38 s · 2 scenarios · 0 deviationsStatic findings
* 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.* 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.* `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.* `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.* 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.// 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.// 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.// 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.// 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.* 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 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.* `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.* `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.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
No advisories in OSV for @davidfuchs/mcp-uptime-kuma@0.15.0 as of 11 h ago. This is the package itself, not its dependencies.