Der Uptimepage MCP-Server,
verbunden mit einem Klick.

“Nutze „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 st.”

“Nutze „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.”

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

“Nutze „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 hum.”

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 st

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

get_incident — One incident: affected monitor, severity, open/resolved times, error sample, and the full operator-update timeline. 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 hum

get_monitor — One monitor's full configuration — everything the check asserts (expected status, body match, headers, timeout, redirect and TLS policy), th

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

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?'. R

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