dev.uptimepage/uptimepage

up checked 2026-11-11T10:38:02.882Z

Unclaimed · Unverified

Agent searches it appeared in, last 30 days: 0. Run this server? Claim the listing: verified label, uptime alerts and analytics.

Publisher-provided title

Uptimepage

Publisher-provided description

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

Summary by lookupd

Lets an agent check monitor uptime, review incidents and history, manage maintenance windows, and publish status page updates.

Install

Claude Code, remote (streamable-http)

claude mcp add --transport http uptimepage https://mcp.uptimepage.dev/mcp

Codex, remote (streamable-http)

codex mcp add uptimepage --url https://mcp.uptimepage.dev/mcp

Cursor, remote (streamable-http) → .cursor/mcp.json

{
  "mcpServers": {
    "uptimepage": {
      "url": "https://mcp.uptimepage.dev/mcp"
    }
  }
}

Other clients: docs. Or tell your agent: Set up lookupd for me: read https://lookupd.com/agent.md and follow it.

Tools (showing 30 of 42)

Publisher-provided text

• acknowledge_incident Acknowledge an incident: take ownership and halt escalation. Internal/operational only — does NOT post anything to the public status page. Use post_incident_upd
• add_status_page_components Add 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 unde
• cancel_maintenance Cancel 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 t
• create_maintenance Schedule 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,
• create_monitor Create 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 afterward
• create_monitors Create 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
• create_status_page Create 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 publ
• 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 stopped on, and the pa
• 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 mean duration, thei
• get_incident One incident: affected monitor, what opened it, severity, open/resolved times, error sample, the full operator-update timeline, and the status pages an incident
• 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 human-resolved, and the
• get_maintenance One maintenance window: title, description, start and end, phase, the monitors it covers, and whether it holds their paging. Read-only.
• get_monitor One monitor's full configuration — everything the check asserts (expected status, body match, headers, timeout, redirect and TLS policy), the regions it probes
• 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, and incident windo
• 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?'. Read-only.
• get_org_usage Which org this connector is bound to, and the account's resource usage against plan limits: monitors, status pages, members, components, channels, alert sources
• get_status_page One 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
• list_alert_sources The 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 th
• list_incidents List 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, o
• list_maintenance List maintenance windows: title, start and end, phase (upcoming, active, completed or cancelled), the monitors each covers, and whether it holds their paging. s
• list_monitor_groups The 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 channel
• list_monitors List 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 The 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 c
• list_regions The 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
• list_status_page_viewers List 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
• list_status_pages List the org's status pages: slug, name, public URL, enabled. Cursor-paginated. Read-only.
• list_tags Every 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 The 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 monit
• pause_monitor Pause a monitor (stop its checks until resumed). For planned work, create_maintenance holds paging instead while the checks keep running. Asks for confirmation
• post_incident_update Post 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

Details

• Version: 1.6.0
• Transports: streamable-http
• Uptime (7 days): 100%
• Median latency: 1366 ms
• First indexed: 2026-11-01T09:01:45.608Z
• Last seen in registry: 2026-11-01T09:01:45.618Z
• Repository: https://github.com/uptimepage/uptimepage
• Website: https://uptimepage.dev/mcp-server

Badge for your README

Shows this live status and links here; updates hourly.

[![lookupd status](https://lookupd.com/badge/dev.uptimepage/uptimepage.svg)](https://lookupd.com/servers/dev.uptimepage/uptimepage)

• 62033 servers
• Last crawl: 2026-11-11T15:38:39.561Z
• API base: https://api.lookupd.com
• MCP URL: https://api.lookupd.com/mcp