dev.uptimepage/uptimepage

Tools

• 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.

  shallow
• 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-only.

  shallow
• get_incident

  One incident: affected monitor, severity, open/resolved times, error sample, and the full operator-update timeline. Read-only.

  shallow
• 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.

  shallow
• 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 the ids of the channels it notifies) — with its current state, last error, and 24h/30d uptime. Every field update_monitor can change is readable here, in the shape that tool takes. Read this before judging whether a response should have passed, or before changing a monitor. Credentials are withheld. Read-only.

  shallow
• 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.

  shallow
• 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.

  shallow
• get_org_usage

  Org resource usage against plan limits: monitors, status pages, members, components, and key policy values. Read-only.

  shallow
• get_status_page

  One status page: name, public URL, enabled, and its components with each linked monitor's current state. Read-only.

  shallow
• 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.

  shallow
• 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.

  shallow
• 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 enabled channel whose recent alerts all failed to arrive. auto_bind_tags is the channel's tag rule: it also pages any monitor carrying one of those tags, so a monitor with no binding can still be covered. Channel settings are withheld, since they hold webhook URLs and bot tokens. Channels are created in the Uptimepage app, not here. Read-only.

  shallow
• list_regions

  The fleet's probe regions: id, display name, city, country, continent. Use it to name where a check runs from and to pass a valid `region` to get_monitor_history. Read-only.

  shallow
• list_status_pages

  List the org's status pages: slug, name, public URL, enabled. Cursor-paginated. Read-only.

  shallow
• 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.

  shallow

Embed this server’s score

Tool count and median score across every tool in this server’s corpus — honest in a way a single cherry-picked tool’s badge wouldn’t be.

[![Vouch score](https://vouch.tools/api/servers/3e186d22-33f7-4882-83f3-cd40ebec7910/badge.svg)](https://vouch.tools/servers/3e186d22-33f7-4882-83f3-cd40ebec7910)