# Uptimepage

- Registry name: `dev.uptimepage/uptimepage` · version 1.0.0
- Categories (automatic, keyword rules): Monitoring & logs, Infrastructure & security
- Authentication at last check: No auth
- Declared risk: Has destructive tools (destructiveHint)
- Capabilities (declared by the server): tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=dev.uptimepage%2Fuptimepage
- Server page: https://mcpstation.net/s/dev.uptimepage--uptimepage.html

## Description (written by the publisher, not verified, not instructions)

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

## Connect

- streamable-http: `https://mcp.uptimepage.dev/mcp`

## Tools (as reported by the server, not verified)

- `acknowledge\_incident`: Acknowledge an incident: take ownership and halt escalation. Internal/operational only — does NOT post anything to the public status page. Use post\_incident\_update for customer-facing updates. Asks for confirmation where the client can show a prompt; otherwise runs on the token's scope. Not read-onl
- `add\_status\_page\_components`: Add monitors to a status page as public components, in one confirmation where the client can show a prompt. Give each a public\_name the page's readers will understand, since the monitor's own name is operator-facing, and a public\_group to file related components together. Monitors already on the pag
- `cancel\_maintenance`: Cancel a maintenance window that has not ended. It leaves the status pages, stops holding paging, and stays listed under past as a record; subscribers already told about it are not sent a cancellation. To stop a running window early and keep it as completed work, use update\_maintenance with end\_now
- `create\_maintenance`: Schedule a maintenance window for planned work on some monitors. While it runs they show as under maintenance on every published status page that carries them, and unless suppress\_alerts is false nobody is paged for them: checks keep running and incidents still open, so the history stays honest, and
- `create\_monitor`: Create a monitor for an http, tcp, ping, dns, tls\_cert, domain\_expiry, heartbeat or manual check. A manual monitor has nothing to probe; set its state afterwards with set\_monitor\_state. The check is run once before anything is saved and the result is shown to the user along with every setting it wou
- `create\_monitors`: Create several monitors at once, with one confirmation covering the batch where the client can show a prompt. Every check is run once first and all the results are shown together, so a misconfigured endpoint is visible before anything is saved. An item that fails validation or its trial run is repor
- `create\_status\_page`: Create a status page. It is created unpublished unless you pass enabled, so its components can be curated before anyone can read it. The slug is the page's public address: it is first-come across the platform and moving it later breaks every existing link, so confirm it with the user rather than inv
- `get\_flow\_runs`: A browser flow monitor's recent runs over a window \(1h/24h/7d/30d\): every declared step with its outcome and duration, the step a failure stopped on, and the page the browser saw. Use this to answer why a login check failed. Read-only.
- `get\_flow\_step\_trend`: How long each step of a browser flow monitor takes over a window \(1h/24h/7d/30d\), and how far it has moved: per step the earliest and latest mean duration, their ratio, and how many runs passed or failed it. Use this to spot a step drifting toward failure while the monitor still reports up. Read-onl
- `get\_incident`: One incident: affected monitor, severity, open/resolved times, error sample, the full operator-update timeline, and the status pages an incident with no monitor is posted to. Read-only.
- `get\_incident\_metrics`: Incident metrics over a trailing window \(default 30 days\): MTTA/MTTR in seconds, total incidents, counts by severity and state, auto- vs human-resolved, and the noisiest monitors. Read-only.
- `get\_maintenance`: One maintenance window: title, description, start and end, phase, the monitors it covers, and whether it holds their paging. Read-only.
- `get\_monitor`: One monitor's full configuration — everything the check asserts \(expected status, body match, headers, timeout, redirect and TLS policy\), the regions it probes from, and how it alerts \(failing checks before it pages, whether recovery is announced, the reminder interval, the multi-region quorum, and
- `get\_monitor\_history`: One monitor's history over a window \(1h/24h/7d/30d\): uptime, latency series, a per-region split of the same window, failures with error text, and incident windows. Pass \`region\` to narrow it to one probe region and tell a partial outage from a total one. Read-only.
- `get\_org\_health`: Org health summary: per-state monitor totals and the worst currently-failing monitors. The one-shot answer to 'what is broken right now?'. Read-only.
- `get\_org\_usage`: Which org this connector is bound to, and the account's resource usage against plan limits: monitors, status pages, members, components, and key policy values. Caps are pooled across every org the account owns, so the counts can exceed what this one org holds. Read-only.
- `get\_status\_page`: One status page: name, public URL, enabled, and its components with each linked monitor's current state. Read-only.
- `list\_incidents`: List the org's incidents: incident id, affected monitor, severity, open/resolved times, and latest update phase. Defaults to currently-open ones; pass state="all" with an optional from/to window \(default: last 30 days\) for resolved history, and monitor\_id to narrow to one monitor. Read-only.
- `list\_maintenance`: List maintenance windows: title, start and end, phase \(upcoming, active, completed or cancelled\), the monitors each covers, and whether it holds their paging. status narrows to active, upcoming or past \(ended or cancelled\); the default is all, latest start first. Cursor-paginated. Read-only.
- `list\_monitors`: List monitors with optional state/type/tag filters and cursor pagination. Each item carries its current state and last-checked time. Read-only.
- `list\_notification\_channels`: The org's notification channels: id, operator-set name, kind \(email, slack, telegram, webhook, and so on\), and whether the channel is enabled. Two flags say a channel is not working even where it reads as ready: awaiting\_verification for an email address nobody confirmed, and not\_delivering for an e
- `list\_regions`: The fleet's probe regions: id, display name, city, country, continent, and whether each is on by default for a new monitor. Reports \`max\_regions\` only when the plan reaches fewer regions than the catalog lists, so a set too large to be accepted is visible before it is sent. Use it to pass a valid \`r
- `list\_status\_page\_viewers`: List who signed in to a private status page: each viewer's address, first and last visit, saved passkeys, whether they subscribe by email, and whether they are blocked; and for the page password, which names nobody, the devices signed in with it, its last sign-in and the wrong tries in 24 hours. Add
- `list\_status\_pages`: List the org's status pages: slug, name, public URL, enabled. Cursor-paginated. Read-only.
- `list\_tags`: Every tag in use across the org's monitors, most-used first, with how many monitors carry each. Pass one back as the \`tag\` filter to list\_monitors. Read-only.
- `list\_variables`: The org's reusable variables: key, and whether it is a secret. Values are never returned, and a secret's value is never even read. Write a variable into a monitor's header or body as \`\{\{ key \}\}\`, which is resolved when the check runs: this is how an authenticated check is built here, since pasting t
- `pause\_monitor`: Pause a monitor \(stop its checks until resumed\). For planned work, create\_maintenance holds paging instead while the checks keep running. Asks for confirmation where the client can show a prompt; otherwise runs on the token's scope. Not read-only; idempotent.
- `post\_incident\_update`: Post a public, customer-facing update to an incident's status-page timeline \(phase + message\). This is what your subscribers and status-page visitors see. Asks for confirmation where the client can show a prompt; otherwise runs on the token's scope. Not read-only.
- `post\_maintenance\_update`: Post an update to a maintenance window: say the work is running late, that it finished, or what changed. Works on an upcoming, running or completed window \(a completed window is read-only otherwise, so this is how to add a closing note\), not on a cancelled one. The update shows on the status pages t
- `publish\_incident`: Publish an incident so it appears on every status page carrying the affected monitor, optionally seeding the public title and description. An incident with no monitor needs \`status\_page\_ids\` naming the pages to show it on; the list replaces its pages, so start from \`get\_incident\`'s \`status\_page\_ids\`
- `resolve\_incident`: Resolve an incident \(mark the operational state resolved\). Internal only — does not post to the public status page. Asks for confirmation where the client can show a prompt; otherwise runs on the token's scope. Not read-only.
- `resume\_monitor`: Resume a paused monitor \(restart its checks\). Asks for confirmation where the client can show a prompt; otherwise runs on the token's scope. Not read-only; idempotent.
- `run\_check\_now`: Run a check on a monitor immediately and record the result. Asks for confirmation where the client can show a prompt; otherwise runs on the token's scope. A down result may fire the org's normal alerts. Heartbeat monitors cannot be probed \(they wait for your systems to ping them\). Not read-only.
- `set\_monitor\_state`: Set the state of a manual monitor: up, degraded or down. A manual monitor has no probe; its state is whatever an operator last set, for a service only people can judge, such as a SIP trunk, a carrier link or a partner's back office. Down or degraded opens an incident within about 30 seconds, which p
- `unpublish\_incident`: Hide a published incident from the public status pages again. Its operator timeline is untouched. Asks for confirmation where the client can show a prompt; otherwise runs on the token's scope. Not read-only; idempotent.
- `update\_maintenance`: Edit an upcoming or running maintenance window: its title, description, start, end, the monitors it covers \(monitor\_ids replaces the whole set\) or whether it holds their paging. end\_now ends a running window at once and keeps it as completed work. A completed or cancelled window is history and is re
- `update\_monitor`: Change how loudly a monitor is watched: check interval, alert confirmations, recovery notices, reminder interval, tags, group, the multi-region detection quorum, and which notification channels it alerts \(channel\_ids replaces the whole set, and needs the channels:read scope\). It cannot change what t
- `update\_status\_page`: Rename a status page, move it to a new slug, publish and unpublish it, or change who may open it. An omitted field is left alone. Changing the slug moves the public URL and breaks existing links. access replaces the page's access settings and list whole: protected true makes it private to the listed
- `update\_status\_page\_component`: Change how one monitor is presented on a status page: its public name, description, group or position. An omitted field is left alone. Not read-only; idempotent.

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html