Agents Index

Uptimepage

Online

Monitor uptime and incidents, run checks, and publish status updates from your Uptimepage org.

Visit publisherConnectJSON

What it can do: 42 tools

  • acknowledge_incidentAcknowledge an incident: take ownership and halt escalation. Internal/operational only — does NOT post anything to the public status page. Use post_incident_update for customer-facing updates. Asks for confirmation where
  • add_status_page_componentsAdd monitors to a status page as public components, in one confirmation where the client can show a prompt. Give each a public_name the page's readers will understand, since the monitor's own name is operator-facing, and
  • cancel_maintenanceCancel a maintenance window that has not ended. It leaves the status pages, stops holding paging, and stays listed under past as a record; subscribers already told about it are not sent a cancellation. To stop a running
  • create_maintenanceSchedule a maintenance window for planned work on some monitors. While it runs they show as under maintenance on every published status page that carries them, and unless suppress_alerts is false nobody is paged for them
  • create_monitorCreate a monitor for an http, tcp, ping, dns, tls_cert, domain_expiry, heartbeat or manual check. A manual monitor has nothing to probe; set its state afterwards with set_monitor_state. The check is run once before anyth
  • create_monitorsCreate several monitors at once, with one confirmation covering the batch where the client can show a prompt. Every check is run once first and all the results are shown together, so a misconfigured endpoint is visible b
  • create_status_pageCreate a status page. It is created unpublished unless you pass enabled, so its components can be curated before anyone can read it. The slug is the page's public address: it is first-come across the platform and moving
  • get_flow_runs read-onlyA 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 fai
  • get_flow_step_trend read-onlyHow 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
  • get_incident read-onlyOne incident: affected monitor, what opened it, severity, open/resolved times, error sample, the full operator-update timeline, and the status pages an incident with no monitor is posted to. For an incident another tool'
  • get_incident_metrics read-onlyIncident 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.
  • get_maintenance read-onlyOne maintenance window: title, description, start and end, phase, the monitors it covers, and whether it holds their paging. Read-only.
  • get_monitor read-onlyOne 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, whe
  • get_monitor_history read-onlyOne 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
  • get_org_health read-onlyOrg health summary: per-state monitor totals and the worst currently-failing monitors. The one-shot answer to 'what is broken right now?'. Read-only.
  • get_org_usage read-onlyWhich org this connector is bound to, and the account's resource usage against plan limits: monitors, status pages, members, components, channels, alert sources, and key policy values. Caps are pooled across every org th
  • get_status_page read-onlyOne status page: name, public URL, enabled, subscriber email time zone, its components with each linked monitor's current state, and the monitor groups it shows as sections with their members. Read-only.
  • list_alert_sources read-onlyThe org's alert sources: tools such as Prometheus Alertmanager, Grafana and Datadog, or a script, that send their alerts here so they open incidents and page through the org's rotations. Per source: id, operator-set name
  • list_incidents read-onlyList the org's incidents: incident id, affected monitor, what opened it (origin, with the alert source for an incident another tool's alert opened), severity, open/resolved times, and latest update phase. Defaults to cur
  • list_maintenance read-onlyList maintenance windows: title, start and end, phase (upcoming, active, completed or cancelled), the monitors each covers, and whether it holds their paging. status narrows to active, upcoming or past (ended or cancelle
  • list_monitor_groups read-onlyThe org's monitor groups, empty ones included: name, whether the group alerts as one (a member's failure opens one group incident that pages the group's channels, and the members' own stay quiet), member count, the group
  • list_monitors read-onlyList monitors with optional state/type/tag filters and cursor pagination. Each item carries its current state and last-checked time. Read-only.
  • list_notification_channels read-onlyThe 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
  • list_regions read-onlyThe fleet's probe regions: id, display name, city, country, continent, and whether each is on by default for a new monitor. Reports `max_regions` only when the plan reaches fewer regions than the catalog lists, so a set
  • list_status_page_viewers read-onlyList who signed in to a private status page: each viewer's address, first and last visit, saved passkeys, whether they subscribe by email, and whether they are blocked; and for the page password, which names nobody, the
  • list_status_pages read-onlyList the org's status pages: slug, name, public URL, enabled. Cursor-paginated. Read-only.
  • list_tags read-onlyEvery 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.
  • list_variables read-onlyThe org's reusable variables: key, and whether it is a secret. Values are never returned, and a secret's value is never even read. Write a variable into a monitor's header or body as `{{ key }}`, which is resolved when t
  • pause_monitorPause a monitor (stop its checks until resumed). For planned work, create_maintenance holds paging instead while the checks keep running. Asks for confirmation where the client can show a prompt; otherwise runs on the to
  • post_incident_updatePost a public, customer-facing update to an incident's status-page timeline (phase + message). This is what your subscribers and status-page visitors see. Asks for confirmation where the client can show a prompt; otherwi
  • post_maintenance_updatePost an update to a maintenance window: say the work is running late, that it finished, or what changed. Works on an upcoming, running or completed window (a completed window is read-only otherwise, so this is how to add
  • publish_incidentPublish an incident so it appears on every status page carrying the affected monitor, optionally seeding the public title and description. An incident with no monitor needs `status_page_ids` naming the pages to show it o
  • resolve_incidentResolve an incident (mark the operational state resolved). Internal only — does not post to the public status page. Asks for confirmation where the client can show a prompt; otherwise runs on the token's scope. Not read-
  • resume_monitorResume a paused monitor (restart its checks). Asks for confirmation where the client can show a prompt; otherwise runs on the token's scope. Not read-only; idempotent.
  • run_check_nowRun a check on a monitor immediately and record the result. Asks for confirmation where the client can show a prompt; otherwise runs on the token's scope. A down result may fire the org's normal alerts. Heartbeat monitor
  • set_monitor_stateSet the state of a manual monitor: up, degraded or down. A manual monitor has no probe; its state is whatever an operator last set, for a service only people can judge, such as a SIP trunk, a carrier link or a partner's
  • unpublish_incidentHide a published incident from the public status pages again. Its operator timeline is untouched. Asks for confirmation where the client can show a prompt; otherwise runs on the token's scope. Not read-only; idempotent.
  • update_maintenanceEdit an upcoming or running maintenance window: its title, description, start, end, the monitors it covers (monitor_ids replaces the whole set) or whether it holds their paging. end_now ends a running window at once and
  • update_monitorChange how loudly a monitor is watched: check interval, alert confirmations, recovery notices, reminder interval, tags, group, the multi-region detection quorum, and which notification channels it alerts (channel_ids rep
  • update_monitor_groupChange a monitor group: its name, whether it alerts as one (a member's failure opens one group incident that pages the group's channels, and the members' own stay quiet), which notification channels the group incident al

…and 2 more.

Connect it

Claude Code
claude mcp add --transport http uptimepage https://mcp.uptimepage.dev/mcp
Claude.ai / ChatGPT
Settings → Connectors → Add custom connector
URL: https://mcp.uptimepage.dev/mcp
Cursor (~/.cursor/mcp.json)
{
  "mcpServers": {
    "uptimepage": {
      "url": "https://mcp.uptimepage.dev/mcp"
    }
  }
}
VS Code (.vscode/mcp.json)
{
  "servers": {
    "uptimepage": {
      "type": "http",
      "url": "https://mcp.uptimepage.dev/mcp"
    }
  }
}

Questions

What does Uptimepage do?

Monitor uptime and incidents, run checks, and publish status updates from your Uptimepage org. It exposes 42 tools to AI assistants.

What tools does Uptimepage provide?

42 tools, including acknowledge_incident, add_status_page_components, cancel_maintenance, create_maintenance, create_monitor, create_monitors, create_status_page, get_flow_runs, get_flow_step_trend, get_incident, get_incident_metrics, get_maintenance….

How do I connect Uptimepage to Claude, ChatGPT or Cursor?

Add the remote MCP endpoint https://mcp.uptimepage.dev/mcp as a custom connector or MCP server. Copy-paste setup is on this page.

Does Uptimepage require an account or API key?

No sign-in was needed to list its tools. Individual tools may still need an account or API key.

Is Uptimepage online?

As of 2026-11-19 our probe found it online. It answered 100% of our last 3 checks.

Who publishes Uptimepage?

uptimepage.dev. The official MCP Registry verified that the publisher controls this domain before accepting the listing.

Similar in Cloud & DevOps