MCP serverdev.uptimepage/uptimepage
Monitor uptime and incidents, run checks, and publish status updates from your Uptimepage org.
Overview
Score?
UNRATED 0.811
of what a free look can see, on 32 looks
Looks
36
last 2 hr ago
Tools
37
changed 21 hr ago
More info
URL
mcp.uptimepage.dev/mcp
streamable-http
Says it is
uptimepage 1.3.0
protocol 2025-06-18
In the record since
32 days ago
Among servers18,413 with a card
0median 0.606 · this server 0.811 · highest on record 0.8561
Toolsfrom sha256:39ac508abf…5c51b5 · +1 −0 21 hr ago
| Tool | Schema |
|---|---|
| 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_update for customer-fac |
input · output |
| 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 understand, since the mo |
input · output |
| 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 told about it are not |
input · output |
| 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, and unless suppress_ |
input · output |
| 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 afterwards with set_monitor_s |
input · output |
| 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 are shown together, |
input · output |
| 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 public address: it is fi |
input · output |
| 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 page the browser saw. |
input · output |
| 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, their ratio, and how man |
input · output |
| get_incident 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- |
input · output |
| 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 noisiest monitors. |
input · output |
| get_maintenance One maintenance window: title, description, start and end, phase, the monitors it covers, and whether it holds their paging. Read-only. |
input · output |
| 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 from, and how it ale |
input · output |
| 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 windows. Pass `region` to |
input · output |
| 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. |
input · output |
| get_org_usage 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 acro |
input · output |
| get_status_page One status page: name, public URL, enabled, and its components with each linked monitor's current state. Read-only. |
input · output |
| list_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 |
input · output |
| 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. status narrows to act |
input · output |
| 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. |
input · output |
| 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 channel is not workin |
input · output |
| 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 plan reaches fewer r |
input · output |
| list_status_pages List the org's status pages: slug, name, public URL, enabled. Cursor-paginated. Read-only. |
input · output |
| 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. |
input · output |
| 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 monitor's header or body |
input · output |
| 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 where the client can |
input · output |
| 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 for confirmation whe |
input · output |
| publish_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 |
input · output |
| resolve_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; otherw |
input · output |
| resume_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. |
input · output |
| run_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 th |
input · output |
| set_monitor_state added 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 S |
input · output |
| unpublish_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 to |
input · output |
| update_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. en |
input · output |
| update_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 notifica |
input · output |
| update_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 |
input · output |
| update_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. |
input · output |
Verify it yourself
npx teppi-check https://mcp.uptimepage.dev/mcpcurl -s https://api.teppi.xyz/v1/trust/mcp/mcs_01M1FZ2AGZYR2KSFW5EHKX8375