Categories › Cloud & DevOps › Monitoring, logs & incidents
Monitor uptime and incidents, run checks, and publish status updates from your Uptimepage org.
Remote server: your requests and data go to mcp.uptimepage.dev. Claude Code: claude mcp add --transport http uptimepage https://mcp.uptimepage.dev/mcp · Claude app: Settings → Connectors → Add custom connector.
The tools this server listed when we connected to it, in its own words.
acknowledge_incident — Acknowledge an incident: take ownership and halt escalation. Internal/operational only — does NOT post anything to the public status page. Uadd_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 pagecancel_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; screate_maintenance — Schedule a maintenance window for planned work on some monitors. While it runs they show as under maintenance on every published status pagecreate_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; setcreate_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 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 sluget_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 stget_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 latestget_incident — One incident: affected monitor, what opened it, severity, open/resolved times, error sample, the full operator-update timeline, and the statget_incident_metrics — Incident metrics over a trailing window (default 30 days): MTTA/MTTR in seconds, total incidents, counts by severity and state, auto- vs humget_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), thget_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 textget_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?'. Rget_org_usage — Which org this connector is bound to, and the account's resource usage against plan limits: monitors, status pages, members, components, chaget_status_page — One status page: name, public URL, enabled, subscriber email time zone, its components with each linked monitor's current state, and the monlist_alert_sources — The org's alert sources: tools such as Prometheus Alertmanager, Grafana and Datadog, or a script, that send their alerts here so they open ilist_incidents — List the org's incidents: incident id, affected monitor, what opened it (origin, with the alert source for an incident another tool's alert list_maintenance — List maintenance windows: title, start and end, phase (upcoming, active, completed or cancelled), the monitors each covers, and whether it hlist_monitor_groups — The org's monitor groups, empty ones included: name, whether the group alerts as one (a member's failure opens one group incident that pageslist_monitors — List monitors with optional state/type/tag filters and cursor pagination. Each item carries its current state and last-checked time. Read-onlist_notification_channels — The org's notification channels: id, operator-set name, kind (email, slack, telegram, webhook, and so on), and whether the channel is enablelist_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_reglist_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, alist_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_molist_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 vpause_monitor — Pause a monitor (stop its checks until resumed). For planned work, create_maintenance holds paging instead while the checks keep running. Aspost_incident_update — Post a public, customer-facing update to an incident's status-page timeline (phase + message). This is what your subscribers and status-pagepost_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 copublish_incident — Publish an incident so it appears on every status page carrying the affected monitor, optionally seeding the public title and description. Aresolve_incident — Resolve an incident (mark the operational state resolved). Internal only — does not post to the public status page. Asks for confirmation whresume_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.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 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 seunpublish_incident — Hide a published incident from the public status pages again. Its operator timeline is untouched. Asks for confirmation where the client canupdate_maintenance — Edit an upcoming or running maintenance window: its title, description, start, end, the monitors it covers (monitor_ids replaces the whole supdate_monitor — Change how loudly a monitor is watched: check interval, alert confirmations, recovery notices, reminder interval, tags, group, the multi-regupdate_monitor_group — Change a monitor group: its name, whether it alerts as one (a member's failure opens one group incident that pages the group's channels, andNot tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.