Uptime Kuma MCP Server for managing monitors
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"uptime-kuma-mcp-server","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# Uptime Kuma MCP Server A server for managing Uptime Kuma monitors via MCP protocol. ## Installation ```bash uvx uptime-kuma-mcp-server ``` ```json "mcpServers": { "uptime-kuma-mcp-server": { "command": "uvx", "args": ["uptime-kuma-mcp-server"], "env": { "KUMA_URL": "https://yourdomain.xyz", "KUMA_USERNAME": "username", "KUMA_PASSWORD": "passwd" } }, } ``` ## Available Tools - `add_monitors` - Batch add multiple monitors to Uptime Kuma, returns Uptime Kuma page URLs after completion - `urls` (list[str], required): List of monitor URLs (must be deduplicated and include full protocol, e.g. https://bing.com) - `get_monitors` - Get all monitors list, returns trimmed fields to prevent context overflow - `delete_monitors` - Batch delete multiple monitors - `ids` (list[int], required): List of monitor IDs to delete ## Run SSE ```python # run_sse.py from uptime_kuma_mcp_server import run_sse run_sse() # Uvicorn running on http://0.0.0.0:8000 ```
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.