Uptimepage by uptimepage.dev
MCP server · Observability & incidents · indexed, not reviewed
Hostedvendor's own
Not reviewed
No score, grade or rank. This listing is facts from the official MCP registry and our own checks, and it stays out of the rankings until the panel reviews it.
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- Website
- uptimepage.dev/mcp-server
- GitHub stars
- 37
- Registry entry
- updated 11 Aug 2026
From the official MCP registry, the package registries and our own checks. JSON · Markdown
Why it's listed
- It's published in the registry under uptimepage.dev, a namespace the registry only gives to whoever proves they control that domain.
Being indexed says nothing about quality, and nobody can pay for it. Is this yours? Ask for a review.
Tools it lists 37 · about 29,460 tokens of context · checked 1 hour ago
| Tool | What it does | Hint |
|---|---|---|
acknowledge_incidentAcknowledge incident | Acknowledge 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… | writes |
add_status_page_componentsAdd 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 understand, since the monitor's own name is operator-facing,… | writes |
cancel_maintenanceCancel 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 told about it are not sent a cancellation. To stop a running… | writes |
create_maintenanceSchedule 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, and unless suppress_alerts is false nobody is paged for… | writes |
create_monitorCreate 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 afterwards with set_monitor_state. The check is run once before… | writes |
create_monitorsCreate 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 are shown together, so a misconfigured endpoint is visible… | writes |
create_status_pageCreate 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 public address: it is first-come across the platform and moving… | writes |
get_flow_runsBrowser 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 page the browser saw. Use this to answer why a login check… | read-only |
get_flow_step_trendBrowser 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, their ratio, and how many runs passed or failed it. Use this to… | read-only |
get_incidentIncident details | One incident: affected monitor, severity, open/resolved times, error sample, the full operator-update timeline, and the status pages an incident with no monitor is posted to. Read-only. | read-only |
get_incident_metricsIncident 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 noisiest monitors. Read-only. | read-only |
get_maintenanceMaintenance window details | One maintenance window: title, description, start and end, phase, the monitors it covers, and whether it holds their paging. Read-only. | read-only |
get_monitorMonitor details | One 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,… | read-only |
get_monitor_historyMonitor 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 windows. Pass `region` to narrow it to one probe region and tell… | read-only |
get_org_healthOrg 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. | read-only |
get_org_usageUsage against plan | 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. Caps are pooled across every org the account owns, so the… | read-only |
get_status_pageStatus page details | One status page: name, public URL, enabled, and its components with each linked monitor's current state. Read-only. | read-only |
list_incidentsList incidents | List the org's incidents: incident id, affected monitor, severity, open/resolved times, and latest update phase. Defaults to currently-open ones; pass state="all" with an optional from/to window (default: last 30 days)… | read-only |
list_maintenanceList maintenance windows | List 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… | read-only |
list_monitorsList monitors | List monitors with optional state/type/tag filters and cursor pagination. Each item carries its current state and last-checked time. Read-only. | read-only |
list_notification_channelsList 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 channel is not working even where it reads as ready:… | read-only |
list_regionsList probe 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 plan reaches fewer regions than the catalog lists, so a set… | read-only |
list_status_pagesList status pages | List the org's status pages: slug, name, public URL, enabled. Cursor-paginated. Read-only. | read-only |
list_tagsList 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. | read-only |
list_variablesList 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 monitor's header or body as `{{ key }}`, which is resolved when… | read-only |
pause_monitorPause 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 where the client can show a prompt; otherwise runs on the… | writes |
post_incident_updatePost 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 for confirmation where the client can show a prompt;… | writes |
publish_incidentPublish incident | 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 monitor needs `status_page_ids` naming the pages to show it… | writes |
resolve_incidentResolve incident | 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 show a prompt; otherwise runs on the token's scope. Not… | writes |
resume_monitorResume monitor | 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; idempotent. | writes |
run_check_nowRun check now | 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 down result may fire the org's normal alerts. Heartbeat… | writes |
set_monitor_stateSet manual monitor state | 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 can judge, such as a SIP trunk, a carrier link or a partner's… | writes |
unpublish_incidentUnpublish incident | 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; otherwise runs on the token's scope. Not read-only; idempotent. | writes |
update_maintenanceEdit maintenance | 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 holds their paging. end_now ends a running window at once and… | writes |
update_monitorRetune monitor | Change 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… | writes |
update_status_pageUpdate status page | 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 existing links. Not read-only; idempotent. | writes |
update_status_page_componentUpdate status page component | 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; idempotent. | writes |
What https://mcp.uptimepage.dev/mcp answered to tools/list, asked without credentials over MCP 2025-11-25. The token figure is the size of the list as sent, divided by four; a model sees about that much before it calls anything. Full definitions, input schemas included, are in the listing's JSON under mcpTools.
How its tools read to an agent 0 errors · 13 warnings · 0 notes
- warnTC11create_monitor1 parameter without a description: check
- warnTC11set_monitor_state1 parameter without a description: state
- warnTC11update_status_page_component4 parameters without a description: public_description, public_group, public_name, sort_order
- warnTC15add_status_page_componentsinputSchema uses $ref/$defs
- warnTC15create_monitorinputSchema uses $ref/$defs
- warnTC15create_monitorsinputSchema uses $ref/$defs
- warnTC15list_maintenanceinputSchema uses $ref/$defs
- warnTC15set_monitor_stateinputSchema uses $ref/$defs
- warnTC15update_monitorinputSchema uses $ref/$defs
- warnTC22create_monitorthe definition is about 3,273 tokens
- warnTC22create_monitorsthe definition is about 3,123 tokens
- warnTC22get_monitorthe definition is about 3,879 tokens
- warnTC23server37 tools, about 29,472 tokens of definitions
The checks from /check and anchor check, run each day on the list above: about 29,460 tokens of definitions. Not part of the score yet. Check your own server.