# Uptimepage (slim) > Uptimepage, an MCP server by uptimepage.dev, listed from the official MCP registry. Indexed, not reviewed: facts and our own checks, no score or ranking. Monitor uptime and incidents, run checks, and publish status updates from your Uptimepage org. - Full: https://www.anchorterminal.com/tools/uptimepage.md (~2,550 tokens) · this version ~2,480 tokens · JSON https://www.anchorterminal.com/tools/uptimepage.json · canonical https://www.anchorterminal.com/tools/uptimepage - Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · Updated: 2026-10-05 # Uptimepage > Indexed, not reviewed: facts from the official MCP registry and our own checks. No score, grade or rank, and not in the rankings until the panel reviews it. How the index works: https://www.anchorterminal.com/indexed/ - Kind: MCP server, by uptimepage.dev (https://uptimepage.dev/mcp-server) - Category: Observability & incidents (https://www.anchorterminal.com/categories/observability.md) - Listed because: It's published in the registry under uptimepage.dev, a namespace the registry only gives to whoever proves they control that domain. - What the official MCP registry says: Monitor uptime and incidents, run checks, and publish status updates from your Uptimepage org. ## Facts - MCP registry: `dev.uptimepage/uptimepage` 1.0.0 - Endpoint: https://mcp.uptimepage.dev/mcp (streamable HTTP) - Source: https://github.com/uptimepage/uptimepage - Website: https://uptimepage.dev/mcp-server - GitHub stars: 37 - Registry entry updated: 2026-08-11 ## Tools - Tools it lists (37, about 29,460 tokens of context, `tools/list` without credentials over MCP 2025-11-25, checked 2026-10-04 22:25 UTC): - `acknowledge_incident` (writes): Acknowledge an incident: take ownership and halt escalation. Internal/operational only — does NOT post anything to the public status page. Use… - `add_status_page_components` (writes): 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… - `cancel_maintenance` (writes): 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… - `create_maintenance` (writes): 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` (writes): 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… - `create_monitors` (writes): 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` (writes): 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… - `get_flow_runs` (read-only): 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… - `get_flow_step_trend` (read-only): 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,… - `get_incident` (read-only): One incident: affected monitor, severity, open/resolved times, error sample, the full operator-update timeline, and the status pages an incident with no… - `get_incident_metrics` (read-only): 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… - `get_maintenance` (read-only): One maintenance window: title, description, start and end, phase, the monitors it covers, and whether it holds their paging. Read-only. - `get_monitor` (read-only): 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` (read-only): 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… - `get_org_health` (read-only): 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` (read-only): Which org this connector is bound to, and the account's resource usage against plan limits: monitors, status pages, members, components, and key policy values.… - `get_status_page` (read-only): One status page: name, public URL, enabled, and its components with each linked monitor's current state. Read-only. - `list_incidents` (read-only): List the org's incidents: incident id, affected monitor, severity, open/resolved times, and latest update phase. Defaults to currently-open ones; pass… - `list_maintenance` (read-only): List maintenance windows: title, start and end, phase (upcoming, active, completed or cancelled), the monitors each covers, and whether it holds their paging.… - `list_monitors` (read-only): 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` (read-only): 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… - `list_regions` (read-only): 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_pages` (read-only): List the org's status pages: slug, name, public URL, enabled. Cursor-paginated. Read-only. - `list_tags` (read-only): 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` (read-only): 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… - `pause_monitor` (writes): 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` (writes): 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… - `publish_incident` (writes): Publish an incident so it appears on every status page carrying the affected monitor, optionally seeding the public title and description. An incident with no… - `resolve_incident` (writes): Resolve an incident (mark the operational state resolved). Internal only — does not post to the public status page. Asks for confirmation where the client can… - `resume_monitor` (writes): Resume 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;… - `run_check_now` (writes): Run 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… - `set_monitor_state` (writes): Set 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… - `unpublish_incident` (writes): Hide a published incident from the public status pages again. Its operator timeline is untouched. Asks for confirmation where the client can show a prompt;… - `update_maintenance` (writes): Edit an upcoming or running maintenance window: its title, description, start, end, the monitors it covers (monitor_ids replaces the whole set) or whether it… - `update_monitor` (writes): Change how loudly a monitor is watched: check interval, alert confirmations, recovery notices, reminder interval, tags, group, the multi-region detection… - `update_status_page` (writes): Rename a status page, move it to a new slug, or publish and unpublish it. An omitted field is left alone. Changing the slug moves the public URL and breaks… - `update_status_page_component` (writes): Change how one monitor is presented on a status page: its public name, description, group or position. An omitted field is left alone. Not read-only;… - How its tools read to an agent (0 errors, 13 warnings, 0 notes, about 29,460 tokens; rules at https://www.anchorterminal.com/check.md; not part of the score): - warn TC11 create_monitor: 1 parameter without a description: check - warn TC11 set_monitor_state: 1 parameter without a description: state - warn TC11 update_status_page_component: 4 parameters without a description: public_description, public_group, public_name, sort_order - warn TC15 add_status_page_components: inputSchema uses $ref/$defs - warn TC15 create_monitor: inputSchema uses $ref/$defs - warn TC15 create_monitors: inputSchema uses $ref/$defs - warn TC15 list_maintenance: inputSchema uses $ref/$defs - warn TC15 set_monitor_state: inputSchema uses $ref/$defs - warn TC15 update_monitor: inputSchema uses $ref/$defs - warn TC22 create_monitor: the definition is about 3,273 tokens - warn TC22 create_monitors: the definition is about 3,123 tokens - warn TC22 get_monitor: the definition is about 3,879 tokens - warn TC23 server: 37 tools, about 29,472 tokens of definitions - JSON: https://www.anchorterminal.com/api/v1/tools/uptimepage.json - Being indexed says nothing about quality, and nobody can pay for it. Ask for a review: https://www.anchorterminal.com/builders/#claiming