uptime-kuma-mcp-server

Provides an MCP server that lets an MCP-capable agent manage Uptime Kuma monitors (batch add, list, and delete) by calling MCP tools that in turn use the Uptime Kuma API. Includes a simple way to run an SSE endpoint via FastMCP/uvicorn.

Evaluated Apr 04, 2026 (17d ago)

Homepage ↗ Repo ↗ Monitoring mcp uptime-kuma monitoring automation sse python

⚙ Agent Friendliness

/ 100

Can an agent use this?

🔒 Security

/ 100

Is it safe for agents?

⚡ Reliability

/ 100

Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality

Documentation

Error Messages

Auth Simplicity

Rate Limits

🔒 Security

TLS Enforcement

Auth Strength

Scope Granularity

Dep. Hygiene

Secret Handling

The service is configured with KUMA_USERNAME and KUMA_PASSWORD environment variables, which is better than hardcoding secrets, but the README does not describe whether the MCP/SSE endpoint is authenticated/authorized. No info is provided about TLS termination for inbound traffic. Batch actions (add/delete) imply high-impact operations; without MCP-side auth and rate limiting guidance, misuse risk is elevated.

⚡ Reliability

Uptime/SLA

Version Stability

Breaking Changes

Error Recovery

Best When

You want an agent-compatible interface to administer Uptime Kuma monitors and you can run the server in a controlled network while supplying Uptime Kuma credentials via environment variables.

Avoid When

Avoid when you cannot secure the MCP endpoint and secrets, or when you require documented retry/idempotency semantics and clear error-code contracts.

Use Cases

• Automating creation of Uptime Kuma monitors from an AI workflow
• Programmatically auditing and cleaning up monitors (list/delete) via MCP
• Batch operations on monitors as part of infrastructure management or CI tasks

Not For

• Direct public exposure of an MCP service without access controls
• Use cases requiring fine-grained authorization per tool/action
• Environments needing published SLAs or strong guarantees about API stability

Interface

REST API

GraphQL

gRPC

MCP Server

Yes

SDK

Webhooks

Authentication

Methods: KUMA_USERNAME / KUMA_PASSWORD via environment variables to authenticate to Uptime Kuma

OAuth: No Scopes: No

Authentication is described only as username/password for the upstream Uptime Kuma API. The MCP/SSE server itself does not show any auth mechanism in the provided README.

Pricing

Free tier: No

Requires CC: No

No pricing information provided; appears to be a self-hosted open-source package.

Agent Metadata

Pagination

none

Idempotent

False

Retry Guidance

Not documented

Known Gotchas

⚠ README does not describe idempotency or how duplicate URLs/monitor creation is handled when calling add_monitors repeatedly.
⚠ Upstream Uptime Kuma communication errors and MCP tool error mapping are not documented, so agents may need defensive retries with care.

Alternatives

Direct use of the Uptime Kuma HTTP API from your automation code Use a generic reverse-proxy + custom wrapper service exposing your own REST/GraphQL layer over Uptime Kuma Other community MCP servers (if available) that expose Uptime Kuma functionality

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for uptime-kuma-mcp-server.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

API endpoint ↗ Agent guide ↗ Report inaccuracy

Scores are editorial opinions as of 2026-04-04.