# io.github.DavidFuchs/mcp-uptime-kuma (io.github.DavidFuchs/mcp-uptime-kuma@0.11.15) > Source: > Published: 2026-09-09 00:00:12+00:00 [← Index](/leaderboard) # io.github.DavidFuchs/mcp-uptime-kuma A Model Context Protocol (MCP) server for Uptime Kuma version 2. The current version, v0.11.15, was published to the official MCP registry on 2026-09-09. It is distributed as @davidfuchs/mcp-uptime-kuma on npm, filed under Other by this index, and declares 5 environment variables. Removals and unreachable sources are measured across every server this index tracks, contract drift across the servers that answer in consecutive snapshots; [the index's current counts](/stats) put this record in context. ## Using io.github.DavidFuchs/mcp-uptime-kuma in Claude, Cursor, Gemini CLI, Cline, or Zed? MCP tool contracts can change remotely with no version bump. The mcpindex gate pins each contract and **HOLDs the call** when it drifts-before your agent acts. Zero credentials. This is not the package install for this server itself (use **Install this server** for that). Rewrites your MCP host config so each server launches behind the gate. Inspect first: curl -fsSL https://mcpindex.ai/install.sh | less ``` uv tool install mcpindex-gate && mcpindex-config-wire ``` [method](/methodology) Semantic screen found no manipulation pattern in the description. Conformance probe not yet run. `mcpindex.integrity.description` passINFO evidence“No malicious instructions found”via static_description - - Semantic screen only - the deterministic conformance probe has not run on this server - - Confidence is reported but not yet calibrated (v1) - - Screen reads the tool description, not the live behavior - - advisory - - registry description only no input schema - - screen model 8b - - Still current: the description we screened is unchanged, re-checked against the registry - - The registry listing (version, packages, links) changed after this screen ran - the description we assessed did not Semantic screen: an LLM judge reads the tool description for hidden instructions (status PARTIAL). A pass means the description is not lying, not that the tool is safe: a high-capability tool with an honest description still warrants caution. The deterministic conformance probe has not been run on this server yet, so the screen here is semantic-only. Posture: advisory. Confidences are reported but not yet calibrated (calibrated=false at v1). Full verdict history is not shown on this page. Own this server? [Screen its description →](/screen) ## That verdict was true at screening time (snapshot 2026-09-09). Contracts can change after screening, with no version bump. The gate pins io.github.DavidFuchs/mcp-uptime-kuma’s tool contracts on first sight and holds any silent change before your agent acts - the check that keeps being true on Tuesday. [See your first HOLD in 2 minutes →](/guides/install-the-gate-first-hold) Related: [how to trust an MCP server](/guides/how-to-trust-an-mcp-server) · [screen before install](/guides/screen-mcp-server-before-install) · [silent contract drift](/guides/mcp-silent-contract-drift) People vet a server before wiring it in. One line on your project site or docs answers that with an independent record: screening verdict, registry provenance, contract drift history. It stays current as new screens and drift events land. ``` [Independent trust record for io.github.DavidFuchs/mcp-uptime-kuma](https://mcpindex.ai/server/io-github-davidfuchs-mcp-uptime-kuma) - screening verdict, registry provenance, and contract drift monitoring. Independent trust record for io.github.DavidFuchs/mcp-uptime-kuma - screening verdict, registry provenance, and contract drift monitoring. ``` A live verdict badge for your README or listing. It reflects the current screen, links back here, and updates when the verdict does. ``` [![mcpindex](https://mcpindex.ai/api/v1/badge/io-github-davidfuchs-mcp-uptime-kuma)](https://mcpindex.ai/server/io-github-davidfuchs-mcp-uptime-kuma) mcpindex verdict ``` `UPTIME_KUMA_URL` The URL of your Uptime Kuma instance `UPTIME_KUMA_USERNAME` Your Uptime Kuma username (not required if using JWT token authentication or if authentication is disabled) `UPTIME_KUMA_PASSWORD` Your Uptime Kuma password (not required if using JWT token authentication or if authentication is disabled) `UPTIME_KUMA_2FA_TOKEN` Your 2FA token (only required if two-factor authentication is enabled on your account) `UPTIME_KUMA_JWT_TOKEN` Your JWT token for authentication (takes precedence over username/password if provided) [methodology](/methodology) [AgentRoamai.agentroam/agentroam](/server/ai-agentroam-agentroam) Buy travel eSIMs, gift cards and mobile top-ups with crypto — user confirms before any order. [Authoryzeai.authoryze/authoryze](/server/ai-authoryze-authoryze) Give your AI agent a spending limit: approval controls and single-use virtual cards. [0xHumans Protocol MCPio.github.DavidOrpeli/0xhumans-mcp](/server/io-github-davidorpeli-0xhumans-mcp) MCP for AI agents: financing, skills, lending on Base