MCP servercom.hyperping/hyperping

Mark an ongoing outage as being handled: repeat alerts stop. Escalation steps still fire on schedule; resolve it or fix the cause to stop them.

Post an update on a status page incident (investigating, identified, update, monitoring, resolved). Public, and sent to subscribers unless notify_subscribers is false.

Show monitors, components or servers on a status page, in the section you name (created at the end if the page has none by that name) or the first one. Services already on the page

Cancel a maintenance window that has not started: it is deleted and leaves the status pages. Subscribers already told about it are not told it is cancelled. To end one in progress,

End a maintenance window in progress now: checks and alerts resume on its monitors and the status pages show it as completed.

Creates a log dashboard from a ready-made template (overview, errors-patterns, http-access, app-otel, containers, host-syslog, databases, jobs, ingestion-cost, incident-war-room, v

Schedule a maintenance window: checks and alerts stop for its monitors during the window, and the status pages you pass announce it. Public once it has status pages: confirm with t

Create a new monitor. Requires name+url; add "port" for port checks, "dns_*" for DNS checks.

Declare an incident by hand, for a problem no monitor detects. It appears under Incident Management in the dashboard and, with an escalation policy, pages its on-call responders. I

Create a status page on a hyperping.app subdomain, with sections of monitors, components and servers. It is public as soon as it exists: confirm the name, address and services with

Publish an incident on status pages, with its first update. Public, and emailed to subscribers unless notify_subscribers is false: confirm the wording with the user first. To recor

Correct the text or stage of an update already posted, e.g. a typo. The page shows the correction; subscribers are not notified again and its date is kept.

Page the next step of the outage's escalation policy now instead of waiting for it. Each call moves one step further.

Other incidents of this project that started within ±window_minutes (default 10, max 60) of an outage (outage_uuid, or incident key) or of a moment (at), each with monitor (uuid, n

One policy by UUID. Reveals step sequence, linked schedules, and contact channels.

One healthcheck in detail: schedule, grace, state and timing, escalation policy, uptime and downtime over the last 30 days, its last 20 pings (pings are kept 15 days; "start" = a /

One integration by UUID, with its channel-specific config (channel name, webhook URL, routing, etc.).

One maintenance window with its updates and the state of its subscriber notification.

Fetch a single monitor by its UUID.

Anomaly-detection output for a single monitor (flapping, latency spikes, etc.).

Recent HTTP probe logs for a monitor, paginated. Useful to diagnose recent check failures.

Mean time to acknowledge (MTTA) per monitor over a date window, in seconds. Already per-monitor — pass all monitors at once in monitor_uuids rather than calling this once per monit

Mean time to resolve (MTTR) per monitor over a date window, in seconds. Already per-monitor — pass all monitors at once in monitor_uuids rather than calling this once per monitor.

Paginated list of outages scoped to one monitor. Convenience wrapper around list_outages.

Response time latency trend over a date window. Returns a per-monitor breakdown — pass all monitors at once in monitor_uuids rather than calling this once per monitor.

Uptime percentage over a date window, aggregated and optionally per day/hour/week/month.

Who is on call, per on-call schedule, right now or at the moment given in `at` (e.g. next Saturday 10:00), computed by the engine that pages people: names, emails and the rotation

One schedule by UUID with full rotation detail and the linked escalation policies.

Fetch a single outage by UUID, including acknowledgements, description, and root cause.

Who was notified for one outage, and how: every alert delivery attempt (time, channel email/sms/phonecall/slack/teams/webhook/pagerduty/opsgenie/…, recipient: user name and email,

Region-by-region evidence for one outage ("outage_…" or an incident key like "INC-12"): a verdict — "global" (every checked region failed), "partial" (some regions stayed healthy,

Logs around one outage (incident) of the project: from 15 min before it started to 5 min after it ended. Returns warnings and errors grouped by message pattern, the latest matching

Full activity timeline for an outage: detection, cross-region verification, alert dispatches, acknowledgement, resolution.

Uptime of every monitor of the project over a period, worst first, in one call: per monitor uptime_pct, downtime (seconds + text), outage count, longest outage and MTTR (mean time

What changed on a monitor before a moment (default: the outage start) and shortly after: audit-log changes to the monitor and to its escalation policies (regions, URL, timeout, pau

One server in detail: status, last seen, OS, agent version (and whether an update exists), hardware, group, tags, escalation policy; current memory and root disk usage; last 24 h o

One status page with its settings (languages, subscriptions, access) and the services it shows, section by section, with their UUIDs.

One status page incident with every update (newest first, with their UUIDs), its status pages and affected components.

Up/down/paused counts plus a list of currently down monitors with the timestamp they went down.

Who changed what in the project (the Audit Log page; owners and admins, Business plan): newest first, each event with its time, actor (user name and email, or the API key / MCP key

All escalation policies in the project. Use to find which monitors route alerts where.

Cron/heartbeat healthchecks of the project (jobs that ping Hyperping; monitors are list_monitors, servers list_servers): per healthcheck its hc_ uuid, name, schedule (cron + timezo

All notification integrations in the project (Slack, Telegram, Discord, PagerDuty, OpsGenie, Teams, webhook, etc.).

Log dashboards of the project: name, tags, widget count, template, last update. With `uuid`, one dashboard in detail: its time range, variables, sections and every widget with its

Maintenance windows, 20 per page, with their monitors, status pages, updates and status (upcoming, inprogress, completed).

Paginated monitors in the project. Optional status filter (up/down/paused/ssl_expiring).

All on-call schedules in the project. Each entry typically includes rotation config and current on-call.

Paginated list of outages in the project. Filter by status, type, or search term.

Alert notifications (up/down transitions) over a date range. Defaults to last 30 days.

Servers of the project (machines running the Hyperping agent, agt_ uuids; not monitors or healthchecks): per server its name, hostname, status (online, stale = heartbeat late, offl

Incidents published on status pages, newest first, each with its current stage and latest update. For downtime detected on monitors, use list_outages.

Status pages in the project, 20 per page: UUID, name, public URL, password protection.

Users on the project, with names and emails. Use to resolve user IDs from schedules/policies.

Pause a monitor — no checks run and no alerts fire. Same as update_monitor with paused=true.

Take monitors, components or servers off a status page, wherever they appear, groups included. Their settings on the page (display name, description) are lost.

Resolve an incident declared by hand or a server incident, and send the recovery to the channels it paged. An outage detected on a monitor resolves itself when its checks pass agai

Close a status page incident with a final "resolved" update. Same as add_status_page_incident_update with status "resolved"; refuses an incident that is already resolved.

Resume a paused monitor. Same as update_monitor with paused=false.

Run the monitor's check right now from each of its regions (20 at most) and return per region: ok, status, total ms, error, failure layer and phase timings in integer ms (dns, conn

Aggregates the project's logs into a chart and returns a compact summary: per series min/max/avg/last and up to `max_points` points, a table (up to 50 rows) or a single value. HPL

Search the project's logs, newest first. Logs search language (not SQL): free words are ANDed (whole words), "exact phrase", -word to exclude, service:api, host:web-1, env:prod, so

Case-insensitive substring search across monitor names and URLs.

Groups the project's errors (or warnings) of a time window by message pattern (numbers, ids and IPs normalized), most frequent first: count, share, trend (>1 = rising in the last q

Reschedule a maintenance window, rename it, change its monitors or status pages, or post a public update on it. The pages show the change; subscribers are not notified.

Patch a monitor. Pass only fields you want to change; others are preserved.

Change a status page's name, description, website, look or subscription button. Only the fields passed change. The page is public: confirm the change with the user first.

Change a status page incident's title, type, status pages or affected services. The pages show the change right away; subscribers are not notified. To tell them something, post an