# Uptimepage [Health: Active]

**Category:** 📊 Monitoring  
**Repository:** https://github.com/uptimepage/uptimepage  
**GitHub Stars:** 41  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/uptimepage

## Description
Monitor uptime and incidents, run checks, and publish status updates from your Uptimepage org.

## Claude Desktop Quick Installation
Heuristic fallback — verify the package name and runner against the repository README before running it. Uses `npx` (confidence: low):

```json
"mcpServers": {
  "uptimepage": {
    "command": "npx",
    "args": ["-y","uptimepage"]
  }
}
```

## Documentation

## What Uptimepage MCP server does

Uptimepage MCP server gives LLM clients access to an Uptimepage organization. The supplied description identifies three core uses: monitoring uptime, running checks, and publishing status updates. These capabilities are aimed at teams that manage service health, incidents, and customer-facing availability information in Uptimepage.

Uptimepage combines monitoring with public status pages and operational response features. Its broader platform supports HTTP, TCP, ICMP ping, heartbeat, DNS, TLS certificate, domain expiry, browser-flow, and manual checks. It also includes incidents, maintenance windows, subscribers, alert channels, on-call rotations, and escalation policies. The available material does not map each of those platform functions to a named MCP tool, so the exact MCP tool list should be verified in the service documentation.

## How it works

The repository presents MCP as one of several ways to drive the same Uptimepage account, alongside the web interface, REST API, and Terraform provider. The MCP endpoint is represented by `mcp.uptimepage.dev` in the project’s live-service monitoring table. This indicates that the project operates an MCP surface as part of its hosted service, but the excerpt does not specify the transport details or request schema.

Operations are performed against an Uptimepage organization rather than against an isolated local monitor. That makes the server relevant for agents that need to inspect or change monitoring workflows within an existing account. Uptimepage can also be self-hosted as a single binary, although the provided material does not explain the MCP configuration for a self-hosted deployment.

## Setup and configuration

The documented hosted path is to create an account at `uptimepage.dev`; the service accepts GitHub, Google, or email sign-in and does not require a card. The README says the account can then be driven through MCP, but it does not provide an MCP client configuration example, authentication variable, token format, or installation command.

For that reason, setup details should be taken from the project’s MCP documentation or the hosted service. No required environment variables are specified in the supplied material. The project also offers REST API access with scoped API tokens and an official Terraform provider, which are alternatives when an MCP client is not appropriate.

## Tools and capabilities

Based on the supplied description, the Uptimepage MCP server can be used to:

- Monitor uptime from an Uptimepage organization.
- Run monitoring checks.
- Publish status updates.
- Work with an Uptimepage account that may also contain incidents and public status pages.

The README confirms that Uptimepage has an MCP server for LLM clients, but it does not publish tool names, parameter definitions, return schemas, or permission boundaries in the excerpt.

## Limitations and notes

Uptimepage MCP server should not be treated as fully documented from the available README excerpt alone. Client compatibility, transport type, authentication flow, installation steps, and the complete tool inventory are not stated. The repository does identify hosted and self-hosted deployment models, but it does not explain whether the same MCP configuration applies to both.

The underlying Uptimepage product supports many monitoring and incident-management functions, yet only uptime monitoring, checks, and status publishing are explicitly attributed to the MCP integration in the supplied description. Confirm the supported operations before relying on an agent to manage alerting, on-call schedules, subscribers, or escalation policies.

_Full upstream README: https://allmcps.com/mcp/uptimepage/readme_