Once you've connected a client, these are the tools it can call. Every tool call is subject to the same 300-per-minute rate limit as REST — see Rate limits & errors.
All 17 tools below are available to every valid personal access token today — there's no tier-based restriction on which tools you can call.
list_monitorsList all monitors for the team, optionally filtered by status.
Parameters
status (string, optional) — filter by monitor status: up, down, paused, or pending.Behavior: Returns every monitor on the team, filtered by status if provided.
Example prompt: "Show me all my monitors that are currently down."
get_monitorGet details for a single monitor including its current status.
Parameters
id (string, uuid, required) — the monitor's ID.Behavior: Returns the monitor, or a not-found error if the ID doesn't match a monitor on your team.
Example prompt: "What's the status of my checkout API monitor?"
get_monitor_runsGet recent run history for a monitor.
Parameters
id (string, uuid, required) — the monitor's ID.limit (integer, optional) — number of runs to return, up to 100. Defaults to 20.Behavior: Returns recent check results for the monitor, newest first. The certificate fields (certNotAfter, certIssuer, certFingerprint) are set only on SSL monitor runs. For a domain monitor, expiresAt holds the expiry date the registry returned for a successful lookup (null for a failed one), its runs have region set to scheduler, and certNotAfter is always null; for every other monitor type expiresAt is null.
Example prompt: "Show me the last 10 runs for my checkout monitor."
create_monitorCreate a new HTTP, SSL or domain expiry monitor.
Roles: Member, Admin, or Owner
Parameters
type (string, required) — "http", "ssl" or "domain". Determines which fields below apply.name (string, required) — 1–200 characters.intervalSeconds (integer, required for HTTP and SSL; not accepted for domain) — 60–3600.timeoutSeconds (integer, required for HTTP and SSL; not accepted for domain) — 1–120.regions (array of strings, required for HTTP and SSL; not accepted for domain) — one or more of us-east, eu-west, asia.notificationPolicyId (string, uuid, optional, nullable) — which alert policy to notify on status change.url (string, required for HTTP) — the endpoint to check.method (string, required for HTTP) — one of GET, POST, PUT, DELETE, HEAD.expectedStatus (integer, required for HTTP) — 100–599.auth (object, optional, nullable, HTTP only) — type, secret, plus username or headerName depending on type.host (string, required for SSL) — 1–253 characters.port (integer, optional, SSL only) — 1–65535, defaults to 443.warningDays (integer, optional, nullable, SSL and domain) — days before the certificate or domain registration expires to warn.domain (string, required for domain) — the registered domain, for example example.com.Behavior: Creates the monitor and returns it. A domain monitor is looked up once a day over RDAP, so it works only for TLDs whose registry publishes an RDAP service; a domain under any other TLD, such as .io, .co, .me or .de, is rejected with an error that names the TLD. See Domain expiry monitoring.
Example prompt: "Create an HTTP monitor for https://example.com/health that checks every 5 minutes from US East and EU West."
update_monitorUpdate a monitor's name, URL, interval, or other config fields.
Roles: Member, Admin, or Owner
Parameters
id (string, uuid, required) — the monitor's ID.name (string, optional)intervalSeconds (integer, optional)timeoutSeconds (integer, optional)regions (array of strings, optional)notificationPolicyId (string, uuid, optional, nullable)url (string, optional, HTTP only)method (string, optional, HTTP only)expectedStatus (integer, optional, HTTP only)auth (object, optional, nullable, HTTP only)host (string, optional, SSL only)port (integer, optional, SSL only)warningDays (integer, optional, nullable, SSL and domain)domain (string, optional, domain only)Behavior: Updates only the fields you provide. For auth, notificationPolicyId, and warningDays, the same three-way rule applies as the REST API: omit to keep the current value, send null to clear it, or send a new value to replace it.
Example prompt: "Change my checkout monitor's check interval to every minute."
delete_monitorDelete a monitor (admin or owner only).
Roles: Admin or Owner
Parameters
id (string, uuid, required) — the monitor's ID.Behavior: Soft-deletes the monitor — it stops being checked and no longer appears in listings.
Example prompt: "Delete the old staging monitor, I don't need it anymore."
pause_monitorPause a monitor (stops check execution).
Roles: Member, Admin, or Owner
Parameters
id (string, uuid, required) — the monitor's ID.Behavior: Stops check execution for the monitor without deleting it.
Example prompt: "Pause my staging environment monitor while I do maintenance."
resume_monitorResume a paused monitor.
Roles: Member, Admin, or Owner
Parameters
id (string, uuid, required) — the monitor's ID.Behavior: Resumes checks for a paused monitor.
Example prompt: "Resume the staging monitor, maintenance is done."
trigger_checkImmediately trigger a check run for a monitor. Rate-limited to once per monitor per 60 seconds.
Roles: Member, Admin, or Owner
Parameters
id (string, uuid, required) — the monitor's ID.Behavior: Enqueues an immediate check outside the monitor's normal schedule. For a domain monitor it makes the lookup due now instead, and it runs within about a minute. Shares the same 60-second per-monitor lock as the REST /check endpoint.
Example prompt: "Run a check on my API monitor right now."
list_incidentsList incidents for the team, optionally filtered by status.
Parameters
status (string, optional) — open or resolved.Behavior: Returns incidents for the team, filtered by status if provided.
Example prompt: "What incidents are currently open?"
get_incidentGet a single incident with its timeline updates.
Parameters
id (string, uuid, required) — the incident's ID.Behavior: Returns the incident along with every update posted to its timeline.
Example prompt: "Give me the full timeline for that database incident."
create_incidentCreate a manual incident.
Roles: Member, Admin, or Owner
Parameters
title (string, required) — 1–200 characters.monitorId (string, uuid, optional) — links the incident to an existing monitor on your team.message (string, optional) — up to 4000 characters, posted as the incident's first timeline update.severity (string, optional) — minor, major, or critical. Defaults to major.Behavior: Creates the incident and returns it. Through the API and the MCP server you can read only your team's oldest status page, and incidents you create through them are posted to that page; to post an incident to another page, create it in the dashboard. If your team has no public status page, the incident is created but isn't shown on any page and nobody is emailed. Otherwise that page's verified subscribers get an email that the incident was opened; the first timeline update (message) is not emailed.
Example prompt: "Open an incident for elevated error rates on the checkout API, severity major."
post_incident_updatePost a status update to an open incident.
Roles: Member, Admin, or Owner
Parameters
id (string, uuid, required) — the incident's ID.message (string, required) — 1–4000 characters.status (string, optional) — investigating, identified, or monitoring. If omitted, the incident's current status is left unchanged.postedToStatusPage (boolean, optional) — whether this update appears on the status pages that show the incident. Defaults to true.Behavior: Posts the update and, if status is provided, changes the incident's status. Like the REST endpoint, when postedToStatusPage is true the incident's page's verified subscribers are emailed the update; an update with postedToStatusPage set to false sends no email.
Example prompt: "Post an update on the checkout incident saying we've identified the cause."
resolve_incidentResolve an open incident.
Roles: Admin or Owner
Parameters
id (string, uuid, required) — the incident's ID.message (string, optional) — closing note. Defaults to "Incident resolved." if omitted.Behavior: Marks the incident resolved and posts a closing update. The incident's page's verified subscribers are emailed that it was resolved.
Example prompt: "Resolve the checkout incident, the fix is deployed and verified."
get_status_pageGet the team's first (oldest) status page.
Parameters: none
Behavior: Returns your team's oldest status page, or a not-found error if your team has no status page. Through the API and the MCP server you can read only your team's oldest status page, and incidents you create through them are posted to that page; to post an incident to another page, create it in the dashboard. The oldest page is the first one in your Status Pages list.
Example prompt: "What does my public status page look like right now?"
get_current_teamGet the current team's name, slug, and creation date.
Parameters: none
Behavior: Returns your team's basic details.
Example prompt: "What team am I connected to?"
list_team_membersList all members of the current team with their roles.
Parameters: none
Behavior: Returns every member of your team along with their role.
Example prompt: "Who's on my team and what are their roles?"