List all uptime monitors in the workspace.

Get a single monitor by ID, including its full configuration.

Create a new uptime monitor.

Required fields: name, type (HTTP/DNS/TCP/ICMP/MCP/HEARTBEAT), config (type-specific), frequencySeconds (30-86400).

managedBy is set automatically to MCP server-side; callers cannot override it. Use the SDK or CLI directly if you need a different attribution.

Update an existing monitor's configuration.

Delete a monitor permanently.

Pause a monitor (stops checking until resumed).

Resume a paused monitor.

Trigger an ad-hoc test run for a monitor and return the result.

List recent check results for a monitor (cursor-paginated).

List version history for a monitor.

List all incidents in the workspace.

Get a single incident by ID with full details.

Create a manual incident.

Required fields: title, severity (DOWN/DEGRADED/MAINTENANCE). Optional: monitorId (UUID), body (detailed description).

Resolve an active incident, optionally with a resolution message.

Full forensic timeline for an incident.

Returns every recorded state transition for the incident, the rule evaluations that caused each triggering transition, and the policy snapshot in effect at the time.

Use this to explain why an incident was declared/confirmed/resolved, or to audit a past detection decision.

Everything the detection engine recorded for a single check.

Includes the rule evaluations produced for this check_id, the state transitions that fired (if any), and the policy snapshot active at evaluation time. Use when a user references a specific check execution ID (e.g. from a support ticket or webhook).

Fetch a policy snapshot by its content-addressed SHA-256 hash.

Useful for inspecting the exact detection policy that was active when a specific evaluation or transition happened — the hash is stable, so historical data keeps pointing at the right policy even if the monitor has been edited since.

List rule evaluations produced for a monitor (paginated).

Filters:

• rule_type: e.g. "consecutive_failures", "latency_threshold"

• region: probe region, e.g. "us-east"

• only_matched: if True, return only evaluations that fired

• from_/to: ISO-8601 datetime bounds

Use to answer "which rules fired on monitor X in the last hour?".

List state transitions recorded for a monitor (paginated).

A transition captures every WATCHING→TRIGGERED→CONFIRMED→RESOLVED edge the detection engine walked. Includes transitions that occurred before an incident was declared (incident_id = null).

Use to reconstruct the full reliability history of a monitor.

List all alert channels configured in the workspace.

Get an alert channel by ID.

Create a new alert channel.

Required: name, type, config (type-specific). Types: EMAIL, WEBHOOK, SLACK, PAGERDUTY, OPSGENIE, TEAMS, DISCORD, TELEGRAM, GOOGLE_CHAT, PUSHOVER, MATTERMOST, SPLUNK_ONCALL, PUSHBULLET, LINEAR, INCIDENT_IO, ROOTLY, ZAPIER, DATADOG, JIRA, GITLAB.

Update an existing alert channel.

Updatable fields: name, type, config (type-specific). See create_alert_channel for supported types.

Delete an alert channel.

Send a test notification to an alert channel to verify it works.

List all notification policies in the workspace.

Get a notification policy by ID.

Create a notification policy.

Required: name, matchRules (list of {type, value?, monitorIds?, regions?}), escalation ({steps: [{delayMinutes, channelIds}], onResolve?, onReopen?}), enabled (bool), priority (int, higher = evaluated first).

Update a notification policy.

Delete a notification policy.

Send a test dispatch to verify a notification policy's routing.

List all environments in the workspace.

Get an environment by slug (e.g. 'production', 'staging').

Create an environment.

Required fields: name, slug, color.

Update an environment by slug.

Delete an environment by slug.

List all secrets (metadata only, values are never returned).

Create an encrypted secret.

Required fields: key, value. The value is encrypted at rest and can be referenced in monitor auth configs as {{secrets.KEY}}.

Update a secret's value by key.

Delete a secret by key.

List all tags in the workspace.

Get a tag by ID.

Create a tag.

Required fields: name. Optional: color.

Update a tag.

Delete a tag.

List all resource groups in the workspace.

Get a resource group by ID.

Create a resource group.

Required fields: name. Optional: description.

Update a resource group.

Delete a resource group.

Add a monitor to a resource group.

Required fields: monitorId.

Remove a monitor from a resource group.

List all webhook endpoints in the workspace.

Get a webhook endpoint by ID.

Create a webhook endpoint.

Required fields: url, events (list of event types to subscribe to).

Update a webhook endpoint.

Delete a webhook endpoint.

Send a test event to a webhook endpoint to verify it works.

List all API keys in the workspace.

Get a single API key's metadata by id. The secret value is never returned.

Create a new API key. The key value is returned only once.

Required fields: name. Optional: expiresAt.

Revoke an API key (disables it without deleting).

Delete an API key permanently.

List all tracked service dependencies.

Get a tracked dependency by ID.

Start tracking a service dependency by its slug (e.g. 'github', 'aws').

Optionally track a single component via component_id (see list_service_components) and set alert_sensitivity: AWARENESS (silent tracking, default), INCIDENTS_ONLY, MAJOR_ONLY, or ALL.

Change how loudly a tracked dependency alerts you.

Levels: AWARENESS (silent tracking, default — status visible on the dashboard but no notifications), INCIDENTS_ONLY (notify on any incident), MAJOR_ONLY (notify only on major/critical incidents), and ALL (every status change, including maintenance).

Stop tracking a service dependency.

Search the catalog of third-party services (Stripe, GitHub, AWS, ...) that can be tracked as dependencies.

Use query for free-text search by name (e.g. 'stripe', 'cloudflare') and category to filter by catalog category (see list_service_categories). Results are paginated; raise limit (default 20) for broader sweeps.

Get a catalog service's summary by slug (e.g. 'github'), including its current status, categories, and component overview.

Get the live (real-time) operational status of a catalog service, fetched from its upstream status page. Use this when freshness matters more than latency — e.g. 'is Stripe down right now?'.

Get the global status summary across the entire service catalog — counts of operational / degraded / outage services. Use this for a quick 'is anything broken on the internet right now?' overview before drilling into a specific service.

List all service catalog categories (e.g. cloud, payments, devtools) usable as the category filter in search_services.

List a catalog service's components (e.g. 'API', 'Dashboard', 'Webhooks') with their individual statuses. Component IDs can be used to track a single component via track_dependency.

Get historical uptime stats for a catalog service over a period (e.g. '7d', '30d', '90d'; default '30d').

List incidents for a catalog service, or across all services when slug is omitted. Filter by status (e.g. 'active', 'resolved') to answer questions like 'which of my dependencies have open incidents?'.

Get one vendor incident in full detail, including the vendor's timeline of status updates (investigating → identified → resolved). Get incident IDs from list_service_incidents.

Get a one-day rollup for a catalog service on a UTC calendar day (ISO YYYY-MM-DD): aggregated uptime, per-component impact windows, and the incidents that overlapped that day. Use this to answer 'what happened to Stripe on 2026-06-01?'.

Get daily uptime history for a single component of a catalog service (e.g. just the 'API' component of Stripe) over a period ('7d', '30d', '90d', '1y'; default '30d'). Get component IDs from list_service_components.

Get daily uptime history for every leaf component of a catalog service in one call, keyed by component ID, over a period ('7d', '30d', '90d', '1y'; default '30d'). Prefer this over repeated get_component_uptime calls when comparing components.

List scheduled and past maintenance windows announced by a catalog service (e.g. upcoming AWS maintenance that could affect you).

Acquire a deploy lock to prevent concurrent deployments.

Required: lockedBy (identity of requester, e.g. hostname or CI job ID). Optional: ttlMinutes (default 30, max 60).

Get the currently active deploy lock, or null if unlocked.

Release a deploy lock by ID.

Force-release any active deploy lock (admin action).

List maintenance windows for the workspace.

Use this BEFORE creating a new window to check whether someone else (or an earlier agent run) already scheduled overlap, or AFTER a deploy to confirm the window you opened is still active.

Filters (all optional; combine freely):

• monitor_id: UUID of a monitor — only windows attached to that single monitor (org-wide windows are excluded).

• status: "active" for windows currently in progress, or "upcoming" for windows scheduled in the future. Past / cancelled windows are not returned by the API today; omit status for the broadest result.

Get a single maintenance window by ID with full details.

Schedule a maintenance window to suppress alerts during planned work.

Call this BEFORE running an operation that may legitimately cause monitors to fail — a deploy, a database migration, a third-party service's announced downtime — so the on-call rotation isn't paged for known-expected failures. Always pair every successful create with a follow-up cancel_maintenance_window once the operation finishes; if the operation runs long, call update_maintenance_window to push the end time back rather than letting the window lapse early.

Time fields use ISO 8601 / RFC 3339 timestamps with explicit timezone — UTC strongly preferred. Example: "2026-05-15T14:00:00Z". Naive timestamps (no timezone) are rejected by the API.

Body fields:

• startsAt (required): when the window opens.

• endsAt (required): when the window closes; must be strictly after startsAt.

• monitorId (optional): UUID of a single monitor to scope the window to. Omit (or set null) to make this an org-wide window that suppresses alerts on every monitor in the workspace — the right choice for a deploy or migration that touches the whole platform.

• reason (optional): human-readable explanation ("v0.7.3 deploy", "Postgres major upgrade"). Surfaces in the dashboard and on-call channel; keep it specific.

• repeatRule (optional): iCal RRULE string for recurring windows (max 100 chars), e.g. FREQ=WEEKLY;BYDAY=SU for weekly Sunday maintenance. Omit for one-time windows.

• suppressAlerts (optional): whether the window actually silences alerts. Default true; set false to record a maintenance window for audit without changing alerting behavior.

Update an in-flight or scheduled maintenance window.

The most common use is extending an active window when a deploy runs longer than expected — call this with the new endsAt to keep alerts suppressed past the original deadline. The endpoint is a full replacement (PUT, not PATCH): pass the complete intended state, not a delta. Any field omitted falls back to the underlying model's default rather than preserving the existing value.

Time fields use ISO 8601 / RFC 3339 timestamps with explicit timezone (UTC preferred), e.g. "2026-05-15T16:30:00Z".

Body fields (same schema as create):

• startsAt (required)

• endsAt (required)

• monitorId (optional; null = org-wide)

• reason (optional; null clears)

• repeatRule (optional; null clears the recurrence)

• suppressAlerts (optional)

Cancel a maintenance window — alerts resume immediately.

Call this AFTER a deploy or maintenance operation completes successfully so any new monitor failures surface as real incidents instead of being silently absorbed. If the window was scheduled but not yet started, this prevents it from ever opening.

The window record is removed; the audit log preserves the historical fact that the window existed. There is no "uncancel" — schedule a new window if you need to restore suppression.

Get the dashboard overview with monitor counts, incident summary, and uptime stats.

List all status pages in the workspace.

Get a status page by ID, including branding and overall status.

Create a new status page.

Required fields: name, slug. Optional: description, branding (brandColor, theme, headerStyle, etc.), visibility (PUBLIC/PASSWORD), enabled, incidentMode (MANUAL/REVIEW/AUTOMATIC).

Update a status page's name, slug, branding, visibility, or incident mode.

Delete a status page permanently.

Batch-reorder a status page's full layout.

Required: sections — top-level layout in their new order, where each entry is either {kind:"component", componentId} or {kind:"group", groupId}. Use groupOrders (optional) to also reorder components within specific groups; only include groups whose internal order changed. The full top-level set must be provided — partial reorders are rejected by the API.

Use this for "drag-and-drop" layout edits that touch both groups and ungrouped components. To reorder components within a single group only, prefer reorder_status_page_components.

List all components on a status page.

Add a component to a status page.

Required fields: name, type (STATIC or MONITOR). Optional: groupId (nest under a group), monitorId (for MONITOR type).

Update a status page component's name, group, or status.