Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Uptimepage

REMOTE · MCP.UPTIMEPAGE.DEV

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

0 this week 92 Trust /100

Last scanned (16 hours ago)

Scores higher than 98% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Monitoring and Observability

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security94
Transport & Reachability100
Schema Quality & AI Usability68
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 7868 tokens (~187/item across 42 items; 42 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management99
  • Stability check failed: schema churn in the 30 days we've observed: 0 tool removals, 1 breaking changes, 0 auth/transport breaks, 3 additions. See how to fix → Fail
Tool Coverage99
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 95% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 43 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Nov 26 0
    • Server version: 1.6.0 → 1.7.0 functional
  • 11 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 95 to 99.

  • 10 Nov 26 −1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “get_incident” rewrote its description, which is the text the model reads security
    • Tool “get_org_usage” rewrote its description, which is the text the model reads security
    • Tool “list_incidents” rewrote its description, which is the text the model reads security
    • New tool “list_alert_sources” functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 4 Nov 26 0
    • Tool “get_status_page” rewrote its description, which is the text the model reads security
    • Tool “update_status_page” rewrote its description, which is the text the model reads security
    • “update_status_page” added an optional parameter “timezone” cosmetic
  • 2 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 98 to 99.

  • 31 Oct 26 −1
    • “create_maintenance” reworded the description of “description” cosmetic
    • “post_incident_update” reworded the description of “message” cosmetic
    • “post_maintenance_update” reworded the description of “message” cosmetic
    • “update_maintenance” reworded the description of “description” cosmetic

    4 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.

  • 30 Oct 26 0
    • Stability: pass → fail ▼ security
    • A breaking change shipped without a version bump: still 1.6.0 ▼ security
    • New tool “update_monitor_group”, which the server declares destructive security
    • Tool “add_status_page_components” rewrote its description, which is the text the model reads security
    • Tool “get_status_page” rewrote its description, which is the text the model reads security
    • Tool “update_status_page_component” rewrote its description, which is the text the model reads security
    • “update_status_page_component” changed the type of “monitor_id”: string → string|null ▼ functional
    • New tool “list_monitor_groups” functional
    • “add_status_page_components” added an optional parameter “groups” cosmetic
    • “update_status_page_component” added an optional parameter “heading” cosmetic
    • “update_status_page_component” added an optional parameter “section_id” cosmetic
    • “update_status_page_component” reworded the description of “monitor_id” cosmetic
    • “update_status_page_component” reworded the description of “public_group” cosmetic
    • “add_status_page_components” made “components” optional cosmetic
    • “update_status_page_component” made “monitor_id” optional cosmetic
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://mcp.uptimepage.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.uptimepage.dev CN=YE2,O=Let's Encrypt,C=US 26 Sept 2026 25 Dec 2026 ECDSA 256 ECDSA-SHA384 6501e358767ecaf94e154f8e0b5a12c3b0b
SANs: *.uptimepage.dev
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.uptimepage.dev. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
dev. DS published 60074 8 Verified
uptimepage.dev. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer resource_metadata="https://mcp.uptimepage.dev/.well-known/oauth-protected-resource", scope="targets:read status_page:read incidents:read maintenance:read"

Bearer resource_metadata="https://mcp.uptimepage.dev/.well-known/oauth-protected-resource", scope="targets:read status_page:read incidents:read maintenance:read"
Header Value
strict-transport-security max-age=31536000; includeSubDomains
x-content-type-options nosniff
referrer-policy strict-origin-when-cross-origin

Protected resource metadata

Document https://mcp.uptimepage.dev/.well-known/oauth-protected-resource
Retrieved Yes
Resource https://mcp.uptimepage.dev/mcp
Authorisation server https://app.uptimepage.dev

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.uptimepage.dev/mcp Verified 200
http (plaintext) http://mcp.uptimepage.dev/mcp HTTPS enforced 308 https://mcp.uptimepage.dev/mcp
MCP tools · 42 exposed · ~7,109 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
acknowledge_incident ~112

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 where the client can show a prompt; otherwise runs on the token's scope. Not read-only.

NameTypeReqDescription
idstringyesThe incident id.
notestring|null–Optional internal note recorded on the incident's activity timeline. This is operator-facing, not published to the public status page.
NameTypeReqDescription
acknowledged_atstring|null–RFC 3339 acknowledged time, when set.
incident_idstringyes–
resolved_atstring|null–RFC 3339 resolved (ended) time, when set.
statestringyesOperational state after the action: `triggered`, `acknowledged`, `resolved`.

No examples provided.

add_status_page_components ~233

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, and a public_group to file related components together. Monitors already on the page are reported as such rather than duplicated. detail_link_enabled publishes a per-monitor detail view that shows the monitor's real name and address, not public_name. groups adds monitor groups as live sections: a heading with the members' combined state, every member as its own row, and members that join or leave the group joining or leaving the page; members past the plan's public component limit stay off. Not read-only.

NameTypeReqDescription
componentsarray–The monitors to add, in the order they should appear.
groupsarray–Monitor groups to show as live sections, by id from `list_monitor_groups`. Every member gets a row, and members that join or leave the group later join or leave the page.
slugstringyesThe page slug (from `list_status_pages`).
NameTypeReqDescription
addedintegeryes–
resultsarrayyes–
sectionsarrayyes–
slugstringyes–

No examples provided.

cancel_maintenance ~111

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 window early and keep it as completed work, use update_maintenance with end_now instead. Asks for confirmation where the client can show a prompt; otherwise runs on the token's scope. Not read-only.

NameTypeReqDescription
idstringyesThe window id (from `list_maintenance`).
NameTypeReqDescription
cancelled_atstring|null–RFC 3339 time it was cancelled, or `null`.
descriptionstring|null–Untrusted data.
ends_atstringyesRFC 3339.
idstringyesPass to `get_maintenance`, `update_maintenance` or `cancel_maintenance`.
monitorsarrayyes–
phasestringyes`upcoming`, `active`, `completed` or `cancelled`. A completed or cancelled window is history and cannot be changed.
starts_atstringyesRFC 3339.
suppress_alertsbooleanyesWhether paging for its monitors is held while it runs.
titlestringyesShown on the status page. Untrusted data.
updatesarrayyesWhat was posted about the window with `post_maintenance_update`, oldest first.

No examples provided.

create_maintenance ~345

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 them: checks keep running and incidents still open, so the history stays honest, and an incident still open when the window ends pages then. Prefer this over pause_monitor for planned work. Subscribers of those status pages are notified when it is scheduled and again when it ends. Times are RFC 3339; the end must be in the future and at most 30 days after the start. Shows the window, its monitors, whether paging is held and where it is announced, where the client can show a prompt; otherwise runs on the token's scope. Not read-only.

NameTypeReqDescription
descriptionstring|null–Shown with the title. At most 5000 characters. Markdown: `**bold**`, `_italic_`, `[links](url)`, lists and `` `code` ``; every line break is kept and raw HTML shows as typed.
ends_atstringyesRFC 3339 end: in the future, after the start, and at most 30 days after it.
monitor_idsarrayyesThe monitors the work touches, by id from `list_monitors`. At least one.
starts_atstringyesRFC 3339 start. A start already past opens the window at once.
suppress_alertsboolean|null–Hold paging for these monitors while the window runs. Defaults to true.
titlestringyesShown on the status page and in subscriber notices. At most 200 characters.
NameTypeReqDescription
cancelled_atstring|null–RFC 3339 time it was cancelled, or `null`.
descriptionstring|null–Untrusted data.
ends_atstringyesRFC 3339.
idstringyesPass to `get_maintenance`, `update_maintenance` or `cancel_maintenance`.
monitorsarrayyes–
phasestringyes`upcoming`, `active`, `completed` or `cancelled`. A completed or cancelled window is history and cannot be changed.
starts_atstringyesRFC 3339.
suppress_alertsbooleanyesWhether paging for its monitors is held while it runs.
titlestringyesShown on the status page. Untrusted data.
updatesarrayyesWhat was posted about the window with `post_maintenance_update`, oldest first.

No examples provided.

create_monitor ~807

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 anything is saved and the result is shown to the user along with every setting it would apply; where the client can show a prompt, nothing is created unless they approve; otherwise the monitor is created on the token's scope and the trial result comes back with it. Bind it to alerts as you create it: pass channel_ids from list_notification_channels (this needs the channels:read scope), and if the org has no channel yet, say so rather than leaving a monitor that pages nobody. Leave regions unset unless the user named where they want the check to run from — omitted, it probes from the operator's default set, which is already the intended coverage; naming more regions than the plan allows is refused outright. Request headers and a request body can be set, but a credential must be referenced rather than pasted: write `Bearer {{ my_key }}` and call list_variables for the keys this org has. A URL carrying a username or password is refused, and browser flows cannot be created here — add those in the app. Not read-only.

NameTypeReqDescription
alert_confirmationsinteger|null–Consecutive failing checks before the monitor alerts. Minimum 1, defaults to 2.
channel_idsarray|null–Channel ids from `list_notification_channels` to alert. Omitting them creates a monitor that pages nobody, which is worth saying out loud rather than leaving for an outage to reveal. The channels the…
check–yes–
group_namestring|null–Operator-side grouping label.
interval_secsinteger|null–Seconds between checks, held to the plan's floor and the check kind's own floor. Omit it to get the cadence the app's own picker opens this kind at, which is well above the hard minimum for the slow-…
namestringyesWhat the operator will see in lists and alerts.
notify_recoveryboolean|null–Whether recovery is announced. Defaults to true.
recovery_period_secsinteger|null–Seconds a recovered monitor must stay healthy before its incident closes; a failure confirmed inside the window keeps the incident open, so a flapping service reads as one outage. 0 to 1800; 0 closes…
region_policy––Detection quorum across probe regions.
regionsarray|null–Probe regions to run the check from, as ids from `list_regions`. Omit unless the user named the places they want covered: omitting takes the regions `list_regions` flags `default_selected`, which is…
renotify_interval_secsinteger|null–Seconds before the first reminder while an outage stays unacknowledged; each further reminder waits twice as long, up to a day. 0 turns reminders off; otherwise at least 60. Defaults to 3600.
tagsarray|null–At most 50, each at most 50 characters.
NameTypeReqDescription
addressstringyesWhat the check watches, as stored.
alertsstringyesThe channels this monitor will alert, by name, or `nobody` when nothing reaches it. One covered by a channel's tag rule rather than a binding is marked `by tag`. A channel that cannot deliver says so…
idstringyes–
interval_secsintegeryes–
namestringyes–
probe––The trial run's outcome, which the operator saw before approving. Absent for a heartbeat, which has nothing to probe.
regionsarrayyesProbe regions the monitor was assigned, which is the operator's default set when `regions` was omitted. Empty for a heartbeat.

No examples provided.

create_monitors ~144

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 before anything is saved. An item that fails validation or its trial run is reported in the results and the rest are still created. Prefer this over repeated create_monitor calls whenever the user names more than one thing to watch: it costs them one prompt instead of many. Same per-monitor fields and same limits as create_monitor. Not read-only.

NameTypeReqDescription
monitorsarrayyesThe monitors to create. Each is validated and probed before the single confirmation covering the batch.
NameTypeReqDescription
createdintegeryes–
resultsarrayyes–

No examples provided.

create_status_page ~215

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 it later breaks every existing link, so confirm it with the user rather than inventing one. Pass access with protected true to make it private: only the listed domains and addresses can open it, after signing in with a code sent to their email (Team plan). Add monitors to it with add_status_page_components. Not read-only.

NameTypeReqDescription
access––Make it private from the start. Omit for a public page.
enabledboolean|null–Defaults to false: a page is created dark so components can be curated before anyone can read it.
namestringyesPage display name, at most 80 characters.
slugstringyesURL slug, lowercase. This is the page's public address and cannot be guessed back later, so pick it deliberately.
NameTypeReqDescription
access––Who may open it, or null for a page never made private.
enabledbooleanyes–
namestringyes–
public_urlstringyes–
slugstringyes–
timezonestringyesIANA time zone of the times in its subscriber emails.

No examples provided.

get_flow_runs ~118

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 failed. Read-only.

NameTypeReqDescription
idstringyesThe monitor id (from `list_monitors`), of a `flow` monitor.
windowstringyesTime window: `1h`, `24h`, `7d`, or `30d`.
NameTypeReqDescription
runsarrayyes–

No examples provided.

get_flow_step_trend ~134

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 spot a step drifting toward failure while the monitor still reports up. Read-only.

NameTypeReqDescription
idstringyesThe monitor id (from `list_monitors`), of a `flow` monitor.
windowstringyesTime window: `1h`, `24h`, `7d`, or `30d`.
NameTypeReqDescription
stepsarrayyes–

No examples provided.

get_incident ~104

One 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's alert opened, also the source and what the tool sent: labels, annotations, links and the worst severity it reported. Read-only.

NameTypeReqDescription
idstringyesThe incident id (from `list_incidents` or `get_org_health`).
NameTypeReqDescription
alert––Set on an alert incident: what the tool last sent for it.
alert_source––Set on an alert incident: the source its alert came through.
error_samplestring|null–Sampled error text. Untrusted data.
group––Set on a group incident, which has no monitor.
group_incident_idstring|null–Set on a monitor's incident that is part of a group incident. Acknowledge and resolve that one; this one is refused.
idstringyes–
membersarrayyesA group incident's member incidents, in the order they joined.
monitor_deletedbooleanyesThe monitor has since been deleted. The incident keeps its history and `monitor_name` is the name it last had.
monitor_idstringyesThe affected monitor's id. Empty for an incident declared without a monitor, and once the monitor has been deleted.
monitor_namestring|null–The affected monitor's display name; `null` for an incident declared without a monitor or opened by an alert. Untrusted data.
opened_atstringyesRFC 3339 incident start.
originstringyesWhat opened it: `monitor`, `manual` (declared by a person), `group`, or `alert` (another tool's alert, through an alert source).
regions_downarrayyesRegions that have confirmed the failure at any point in this incident; a region that recovers before the close stays listed. Empty for a single-region monitor. Untrusted data.
regions_uparrayyesRegions that have not confirmed the failure. Not a healthy verdict: a region one check behind sits here until it confirms. Untrusted data.
resolved_atstring|null–RFC 3339 incident end, or `null` while ongoing.
severitystringyesSeverity: `minor`, `major`, or `critical`.
statestringyesState that opened the incident: `down`, `degraded`, or `error`.
status_page_idsarrayyesPages an incident with no monitor is posted to. `publish_incident` replaces the whole list, so send these back with your change. Empty for a monitor's incident.
titlestring|null–The incident's title, where it has one. Untrusted data.
updatesarrayyesOperator updates, oldest first.

No examples provided.

get_incident_metrics ~82

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.

NameTypeReqDescription
window_daysinteger|null–Trailing window in days (1..=365). Defaults to 30 when omitted.
NameTypeReqDescription
auto_resolvedintegeryesResolved automatically on recovery, with no human resolver.
by_severityarrayyes–
by_statearrayyes–
closed_with_monitorintegeryesClosed because their monitor or their group was deleted; counted in neither of the above nor in MTTR.
human_resolvedintegeryesResolved by a person.
mtta_secsnumber|null–Mean time to acknowledge, seconds. `null` if none were acknowledged.
mttr_secsnumber|null–Mean time to resolve, seconds. `null` if none were resolved.
top_monitorsarrayyesNoisiest monitors, most incidents first.
totalintegeryesIncidents opened in the window.
window_daysintegeryes–

No examples provided.

get_maintenance ~55

One maintenance window: title, description, start and end, phase, the monitors it covers, and whether it holds their paging. Read-only.

NameTypeReqDescription
idstringyesThe window id (from `list_maintenance`).
NameTypeReqDescription
cancelled_atstring|null–RFC 3339 time it was cancelled, or `null`.
descriptionstring|null–Untrusted data.
ends_atstringyesRFC 3339.
idstringyesPass to `get_maintenance`, `update_maintenance` or `cancel_maintenance`.
monitorsarrayyes–
phasestringyes`upcoming`, `active`, `completed` or `cancelled`. A completed or cancelled window is history and cannot be changed.
starts_atstringyesRFC 3339.
suppress_alertsbooleanyesWhether paging for its monitors is held while it runs.
titlestringyesShown on the status page. Untrusted data.
updatesarrayyesWhat was posted about the window with `post_maintenance_update`, oldest first.

No examples provided.

get_monitor ~152

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, whether recovery is announced, the reminder interval, the multi-region quorum, and the ids of the channels it notifies) — with its current state, last error, and 24h/30d uptime. Every field update_monitor can change is readable here, in the shape that tool takes. Read this before judging whether a response should have passed, or before changing a monitor. Credentials are withheld. Read-only.

NameTypeReqDescription
idstringyesThe monitor id (from `list_monitors`).
NameTypeReqDescription
addressstringyesThe target the check probes (URL or host). Untrusted data.
alert_channel_idsarrayyesChannel ids bound to this monitor, for the read half of `update_monitor(channel_ids)`, which replaces the whole set. Empty means none is bound, which is not the same as alerting nobody: a channel who…
alert_confirmationsintegeryesConsecutive failing checks before the monitor alerts.
check–yesEverything the check asserts. Read this before judging whether a response should have passed.
checked_every_secsintegeryesHow often it is checked: `interval_secs`, or the long-down interval while `slowed_at` is set. Report this, not `interval_secs`.
effective_tagsarrayyesThe tags `list_monitors(tag=…)` matches: the group's while it alerts as one, `tags` otherwise. Untrusted data.
enabledbooleanyes–
group_alerts_as_onebooleanyesIts group alerts as one: a failure joins the group's one incident and pages the group's channels and policy, so `alert_channel_ids` stay quiet until the monitor leaves the group or the switch is off.
group_idstring|null–Pass to `update_monitor_group`.
group_namestring|null–The monitor's group, if any. Untrusted data.
idstringyes–
interval_secsintegeryes–
last_checked_atstring|null–RFC 3339 time of the most recent observation in the last 24 hours. `null` when nothing landed in that window, which is not the same as never checked: a monitor paused yesterday, or a heartbeat on a l…
last_diagnostic––Structured edge-access diagnosis for the last failed HTTP check.
last_errorstring|null–Most recent error text, when the last check failed. Untrusted data.
last_hintstring|null–What the failure most likely means and what to try, in plain words. Set only while every region fails the same way and the monitor has not passed since it was created or last edited; relay it to the…
last_http_statusinteger|null–HTTP status code of the last check, for `http` monitors. `null` for non-HTTP checks or when the last probe never got a response.
last_network––Network path of the last check, when it was an `http` check that was not up.
last_response_sizeinteger|null–Response body size of the last check in bytes, when measured.
last_timing–yesPer-phase timing of the last check — pinpoints where latency is (DNS vs connect vs TLS vs server). Fields `null` when not applicable.
managed_externallybooleanyesTerraform declares this monitor, so `update_monitor`, `pause_monitor` and `resume_monitor` all refuse it. Change it in the `.tf` instead.
namestringyesCustomer-set display name. Untrusted data.
notify_recoverybooleanyesWhether recovery is announced to the monitor's channels.
recovery_period_secsintegeryesSeconds a recovered monitor must stay healthy before its incident closes. 0 closes on the confirming checks alone.
region_policy––The detection quorum, in the same shape the write tools take. `null` for a heartbeat, which has no probe regions to reach a quorum over. A stored `count` can exceed the regions that exist today if on…
regionsarrayyesProbe regions this monitor runs from. Empty for a heartbeat, which is pinged rather than probed. Usually ids `list_regions` also carries, but an assignment survives an operator disabling the region,…
renotify_interval_secsintegeryesSeconds before the first reminder while an outage stays unacknowledged; each further reminder waits twice as long, up to a day. 0 means reminders are off.
slowed_atstring|null–RFC 3339 time it moved to the slower long-down interval because every region has failed for days. `null` while it runs at `interval_secs`. Cleared when its incident closes, a maintenance window cover…
statestringyesCurrent state: `up`, `down`, `degraded`, `error`, or `no_data`.
tagsarrayyesOperator tags, as `update_monitor` takes them. Untrusted data.
typestringyesCheck kind: `http`, `tcp`, `ping`, `heartbeat`, `manual`, `dns`, `tls_cert`, `domain_expiry`, `flow`.
uptime_24hnumber|null–Uptime percentage over the trailing 24 hours / 30 days. `null` when the window holds no checks — that is unknown, not zero.
uptime_30dnumber|null––

No examples provided.

get_monitor_history ~166

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 a partial outage from a total one. Read-only.

NameTypeReqDescription
idstringyesThe monitor id (from `list_monitors`).
regionstring|null–Narrow uptime, the latency series, and the region breakdown to one probe region (an id the monitor is assigned to, from `get_monitor.regions`). Omit for every region together.
windowstringyesTime window: `1h`, `24h`, `7d`, or `30d`.
NameTypeReqDescription
failuresarrayyesConfirmed failures on the monitor as a whole. A `region` filter does not narrow these: an incident is raised for the monitor, not per region.
incidentsarrayyesIncident windows on the monitor as a whole, unnarrowed by `region` for the same reason as `failures`.
latency_seriesarrayyes–
regionstring|null–The region this answer was narrowed to, or `null` for all of them.
regionsarrayyesPer-region split of the same window, so a partial outage is visible. Always every region the monitor runs in, including under a `region` filter, and empty when it runs in only one. Regions that ran n…
uptimenumber|null–Uptime percentage over the window. `null` when the window holds no checks — that is unknown, not zero. Unfiltered it counts confirmed incidents; under a `region` filter it is that region's raw check…

No examples provided.

get_org_health ~41

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 schema present but exposes no named parameters.

NameTypeReqDescription
orgstringyesThe org slug this connector is bound to.
totals–yes–
worstarrayyesNon-up monitors, newest failure first, capped.

No examples provided.

get_org_usage ~70

Which 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 the account owns, so the counts can exceed what this one org holds. Read-only.

Input schema present but exposes no named parameters.

NameTypeReqDescription
alert_sources–yesAlert sources. A cap of 0 means the plan has none.
maintenance_windows–yesCounts windows that have not ended (upcoming and active). Completed windows do not count.
members–yes–
min_check_interval_secsintegeryesMinimum allowed check interval, seconds.
notification_channels–yes–
orgstringyesThe org slug this connector is bound to.
org_namestringyesThe org's display name.
planstringyesPlan id (e.g. `free`, `pro`).
public_components–yes–
retention_daysintegeryesHistory retention, days.
status_pages–yes–
targets–yes–

No examples provided.

get_status_page ~67

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 as sections with their members. Read-only.

NameTypeReqDescription
slugstringyesThe page slug (from `list_status_pages`).
NameTypeReqDescription
access––Who may open it, or null for a page never made private.
componentsarrayyes–
enabledbooleanyes–
namestringyesPage display name. Untrusted data.
public_urlstringyes–
sectionsarrayyesMonitor groups shown as live sections: their members join and leave the page with the group.
slugstringyes–
timezonestringyesIANA time zone of the times in its subscriber emails.

No examples provided.

list_alert_sources ~143

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 through the org's rotations. Per source: id, operator-set name, kind (alertmanager, grafana, datadog, generic), whether it is enabled (paused when not) or held by the plan, routes_to_nobody when its policy, the org default and its channels all reach no one, its escalation policy and channels, and when its last event arrived. The ingest URL and token are withheld: sources are set up in the Uptimepage app. Read-only.

Input schema present but exposes no named parameters.

NameTypeReqDescription
itemsarrayyes–

No examples provided.

list_incidents ~275

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, 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) for resolved history, and monitor_id to narrow to one monitor. Read-only.

NameTypeReqDescription
cursorstring|null–Opaque pagination cursor from a previous call's `next_cursor`. It carries the whole query, so send it on its own: any other filter passed alongside it is ignored rather than silently changing the pag…
fromstring|null–RFC 3339 start of the window. Defaults to 30 days ago. An incident that is still running is listed however long ago it opened.
monitor_idstring|null–Restrict to one monitor (id from `list_monitors`).
statestring|null–Which incidents to return: `open` (default) for the ones still running, or `all` to include resolved ones inside the window.
tostring|null–RFC 3339 end of the window. Defaults to now. Incidents that opened after it are excluded, running or not.
NameTypeReqDescription
fromstringyesRFC 3339 window actually read, after the defaults and the one-year cap. It bounds the *resolved* incidents only: one that is still running is listed however long ago it opened, so it can be older tha…
itemsarrayyes–
next_cursorstring|null––
tostringyes–

No examples provided.

list_maintenance ~117

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 cancelled); the default is all, latest start first. Cursor-paginated. Read-only.

NameTypeReqDescription
cursorstring|null–Opaque pagination cursor from a previous call's `next_cursor`. It carries the whole query, so send it on its own.
status––Defaults to `all`.
NameTypeReqDescription
itemsarrayyes–
next_cursorstring|null––

No examples provided.

list_monitor_groups ~80

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 channels, and the members' own stay quiet), member count, the group incident open now, its channels, reminder interval, whether another member going down sends a message, and tags. Read-only.

Input schema present but exposes no named parameters.

NameTypeReqDescription
itemsarrayyes–

No examples provided.

list_monitors ~142

List monitors with optional state/type/tag filters and cursor pagination. Each item carries its current state and last-checked time. Read-only.

NameTypeReqDescription
cursorstring|null–Opaque pagination cursor from a previous call's `next_cursor`.
statestring|null–Filter by current state: `up`, `down`, `degraded`, `error`, `no_data`.
tagstring|null–Filter to monitors carrying this exact tag.
typestring|null–Filter by check kind: `http`, `tcp`, `ping`, `heartbeat`, `manual`, `dns`, `tls_cert`, `domain_expiry`, `flow`.
NameTypeReqDescription
itemsarrayyes–
next_cursorstring|null––

No examples provided.

list_notification_channels ~145

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: awaiting_verification for an email address nobody confirmed, and not_delivering for an enabled channel whose recent alerts all failed to arrive. auto_bind_tags is the channel's tag rule: it also pages any monitor carrying one of those tags, so a monitor with no binding can still be covered. Channel settings are withheld, since they hold webhook URLs and bot tokens. Channels are created in the Uptimepage app, not here. Read-only.

Input schema present but exposes no named parameters.

NameTypeReqDescription
itemsarrayyes–

No examples provided.

list_regions ~125

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 too large to be accepted is visible before it is sent. Use it to pass a valid `region` to get_monitor_history, and to read where a check would run from. This is a catalog, not a menu to fill: leave `create_monitor.regions` unset unless the user named the places they want covered. Read-only.

Input schema present but exposes no named parameters.

NameTypeReqDescription
itemsarrayyes–
max_regionsinteger|null–How many of these regions one monitor may probe from, when the plan allows fewer than the catalog holds. A `create_monitor` naming more is refused outright, not trimmed to fit. Null when the plan rea…

No examples provided.

list_status_page_viewers ~102

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 blocked; and for the page password, which names nobody, the devices signed in with it, its last sign-in and the wrong tries in 24 hours. Addresses are customer data. Read-only.

NameTypeReqDescription
slugstringyesThe page slug (from `list_status_pages`).
NameTypeReqDescription
password––`null` for a page never made private.
viewersarrayyes–

No examples provided.

list_status_pages ~53

List the org's status pages: slug, name, public URL, enabled. Cursor-paginated. Read-only.

NameTypeReqDescription
cursorstring|null–Opaque pagination cursor from a previous call's `next_cursor`.
NameTypeReqDescription
itemsarrayyes–
next_cursorstring|null––

No examples provided.

list_tags ~46

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 schema present but exposes no named parameters.

NameTypeReqDescription
itemsarrayyes–
truncatedbooleanyesThe org has more tags than the cap returned here, so a tag missing from `items` is not proof it does not exist.

No examples provided.

list_variables ~96

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 the check runs: this is how an authenticated check is built here, since pasting the credential itself is refused. Variables are created and edited in the app, not here. Read-only.

Input schema present but exposes no named parameters.

NameTypeReqDescription
itemsarrayyes–

No examples provided.

pause_monitor ~79

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 token's scope. Not read-only; idempotent.

NameTypeReqDescription
idstringyesThe monitor id (from `list_monitors`).
NameTypeReqDescription
enabledbooleanyesThe monitor's enabled state after the change.
idstringyes–

No examples provided.

post_incident_update ~162

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; otherwise runs on the token's scope. Not read-only.

NameTypeReqDescription
idstringyesThe incident id.
messagestringyesPublic message shown on the status page. Markdown: `**bold**`, `_italic_`, `[links](url)`, lists and `` `code` ``; every line break is kept and raw HTML shows as typed.
phasestring|null–Optional phase: `investigating`, `identified`, `monitoring`, `resolved`, `postmortem`. Defaults to `investigating`.
NameTypeReqDescription
incident_idstringyes–
posted_atstringyesRFC 3339 time the update was posted.

No examples provided.

post_maintenance_update ~223

Post 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 a closing note), not on a cancelled one. The update shows on the status pages that show the window and goes to their email and webhook subscribers; it cannot be edited or removed. Asks for confirmation where the client can show a prompt; otherwise runs on the token's scope. Not read-only.

NameTypeReqDescription
idstringyesThe window id (from `list_maintenance`).
messagestringyesWhat readers should know now, up to 2000 characters: the work runs late, it finished, or what changed. Write it for the people reading the status page, and give any time with its zone. Markdown: `**b…
NameTypeReqDescription
cancelled_atstring|null–RFC 3339 time it was cancelled, or `null`.
descriptionstring|null–Untrusted data.
ends_atstringyesRFC 3339.
idstringyesPass to `get_maintenance`, `update_maintenance` or `cancel_maintenance`.
monitorsarrayyes–
phasestringyes`upcoming`, `active`, `completed` or `cancelled`. A completed or cancelled window is history and cannot be changed.
starts_atstringyesRFC 3339.
suppress_alertsbooleanyesWhether paging for its monitors is held while it runs.
titlestringyesShown on the status page. Untrusted data.
updatesarrayyesWhat was posted about the window with `post_maintenance_update`, oldest first.

No examples provided.

publish_incident ~219

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 on; the list replaces its pages, so start from `get_incident`'s `status_page_ids`. Status-page subscribers may be notified. Asks for confirmation where the client can show a prompt; otherwise runs on the token's scope. Not read-only; idempotent.

NameTypeReqDescription
idstringyesThe incident id.
public_descriptionstring|null–Public summary shown under the headline.
public_titlestring|null–Public headline shown on the status page.
status_page_idsarray|null–Status page ids (from `list_status_pages`) for an incident with no monitor; replaces its pages, so start from `get_incident`'s `status_page_ids` to add or drop one. Leave unset for a monitor's incide…
NameTypeReqDescription
incident_idstringyes–
visibilitystringyesVisibility after the change: `public` or `internal`.

No examples provided.

resolve_incident ~96

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 read-only.

NameTypeReqDescription
idstringyesThe incident id.
notestring|null–Optional internal note recorded on the incident's activity timeline. This is operator-facing, not published to the public status page.
NameTypeReqDescription
acknowledged_atstring|null–RFC 3339 acknowledged time, when set.
incident_idstringyes–
resolved_atstring|null–RFC 3339 resolved (ended) time, when set.
statestringyesOperational state after the action: `triggered`, `acknowledged`, `resolved`.

No examples provided.

resume_monitor ~62

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.

NameTypeReqDescription
idstringyesThe monitor id (from `list_monitors`).
NameTypeReqDescription
enabledbooleanyesThe monitor's enabled state after the change.
idstringyes–

No examples provided.

run_check_now ~90

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 monitors cannot be probed (they wait for your systems to ping them). Not read-only.

NameTypeReqDescription
idstringyesThe monitor id (from `list_monitors`).
NameTypeReqDescription
checked_atstringyesRFC 3339 time of the probe.
diagnostic––Structured edge-access diagnosis, when a supported signature matched.
duration_msintegeryes–
errorstring|null–Error text when the probe failed. Untrusted data.
http_statusinteger|null–HTTP status code, for `http` monitors. `null` for non-HTTP checks or when no response was received.
idstringyes–
network––Network path, when this was an `http` check that was not up.
response_sizeinteger|null–Response body size in bytes, when measured.
statestringyesObserved state: `up`, `down`, `degraded`, `error`.
timing–yesPer-phase timing of the probe (DNS / connect / TLS / first byte).

No examples provided.

set_monitor_state ~259

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 back office. Down or degraded opens an incident within about 30 seconds, which pages the monitor's channels unless a maintenance window holds it, and shows on its status pages as a major outage or degraded performance; up closes the incident. A paused monitor, or one the plan no longer covers, keeps the state and acts on it once it runs again. The note becomes the incident's cause, so make it a reason a responder can act on. Refused for any other kind of monitor. Asks for confirmation where the client can show a prompt; otherwise runs on the token's scope. Not read-only; idempotent.

NameTypeReqDescription
idstringyesThe id of a `manual` monitor (from `list_monitors`).
notestring|null–Why, in one line of at most 200 characters. It becomes the incident's cause and reaches whoever is paged. Omit for none; it replaces the previous note.
state–yes–
NameTypeReqDescription
changedbooleanyes`false` when the monitor already had this state and note.
idstringyes–
notestring|null–Untrusted data.
set_atstringyesRFC 3339 time the state was set.
statestringyes`up`, `degraded` or `down`.

No examples provided.

unpublish_incident ~78

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.

NameTypeReqDescription
idstringyesThe incident id (from `list_incidents` or `get_org_health`).
NameTypeReqDescription
incident_idstringyes–
visibilitystringyesVisibility after the change: `public` or `internal`.

No examples provided.

update_maintenance ~316

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 keeps it as completed work. A completed or cancelled window is history and is refused. Shows the old and new value of every field before it runs, where the client can show a prompt; otherwise runs on the token's scope. Not read-only.

NameTypeReqDescription
descriptionstring|null–At most 5000 characters. An empty string clears it. Markdown: `**bold**`, `_italic_`, `[links](url)`, lists and `` `code` ``; every line break is kept and raw HTML shows as typed.
end_nowboolean|null–End a running window now. Cannot be combined with `starts_at` or `ends_at`.
ends_atstring|null–RFC 3339, in the future. To stop a running window now, send `end_now` instead.
idstringyesThe window id (from `list_maintenance`).
monitor_idsarray|null–Replaces the whole set, by id from `list_monitors`. Read the window first: a monitor left out stops being covered.
starts_atstring|null–RFC 3339.
suppress_alertsboolean|null–Hold paging for its monitors while it runs.
titlestring|null–At most 200 characters.
NameTypeReqDescription
changesarrayyesWhat moved. Empty when every value sent already matched, in which case nothing was written and no confirmation was asked for.
window–yes–

No examples provided.

update_monitor ~472

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 replaces the whole set, and needs the channels:read scope). It cannot change what the check watches — name, address, assertions, expected status, headers, body, probe regions and owner are refused. A monitor managed by Terraform is refused outright. Shows the old and new value of every field before it runs, where the client can show a prompt; otherwise runs on the token's scope. Not read-only.

NameTypeReqDescription
alert_confirmationsinteger|null–Consecutive failing checks before the monitor alerts. Minimum 1. Raising it quietens a flapping monitor at the cost of alerting later.
channel_idsarray|null–Replaces the whole set of alerted channels, by id from `list_notification_channels`. Read the monitor first: a channel left out of this list stops being alerted. An empty list silences the monitor.
group_namestring|null–Operator-side grouping label. Send `null` to clear it; omit to keep it.
idstringyesThe monitor id (from `list_monitors`).
interval_secsinteger|null–Seconds between checks. Held to the plan's floor and the check kind's own floor, whichever is higher.
notify_recoveryboolean|null–Whether recovery is announced to the monitor's channels.
recovery_period_secsinteger|null–Seconds a recovered monitor must stay healthy before its incident closes, 0 to 1800. Raising it folds a flapping monitor's short outages into one incident, at the cost of announcing recovery later.
region_policy––Detection quorum across probe regions.
renotify_interval_secsinteger|null–Seconds before the first reminder while an outage stays unacknowledged; each further reminder waits twice as long, up to a day. 0 turns reminders off; otherwise at least 60.
tagsarray|null–Replaces the whole tag list. Read the monitor first: a tag left out of this list is removed. At most 50 tags, each at most 50 characters.
NameTypeReqDescription
changesarrayyesWhat moved. Empty when every value sent already matched the stored one, in which case nothing was written and no confirmation was asked for.
idstringyes–

No examples provided.

update_monitor_group ~310

Change 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 alerts (channel_ids replaces the whole set, and needs the channels:read scope), the reminder interval, and whether another member going down sends a message. Turning alert as one on or off changes only failures that start afterwards. A group managed by Terraform is refused outright. Shows the old and new value of every field before it runs, where the client can show a prompt; otherwise runs on the token's scope. Not read-only.

NameTypeReqDescription
alert_againboolean|null–Whether another member going down sends a message or only a timeline line.
alert_as_oneboolean|null–Turns alerting as one on or off. Only failures that start afterwards follow the new setting; an incident open now ends the way it started.
channel_idsarray|null–Replaces the whole set of channels the group incident alerts, by id from `list_notification_channels`. Read the group first.
idstringyesThe group id (from `list_monitor_groups`).
namestring|null–New name, at most 50 characters. Members keep their group.
renotify_interval_secsinteger|null–Seconds before the first reminder while the group incident stays unacknowledged; 0 turns reminders off, otherwise at least 60.
NameTypeReqDescription
changesarrayyesWhat moved. Empty when every value sent already matched the stored one, in which case nothing was written and no confirmation was asked for.
idstringyes–

No examples provided.

update_status_page ~244

Rename a status page, move it to a new slug, publish and unpublish it, change who may open it, or set the IANA time zone of its subscriber emails. An omitted field is left alone. Changing the slug moves the public URL and breaks existing links. access replaces the page's access settings and list whole: protected true makes it private to the listed domains and addresses (Team plan), and removes subscribers the list does not cover; protected false makes it public again and keeps the list. Not read-only; idempotent.

NameTypeReqDescription
access––Replace who may open it: make it private, change its list, or make it public again.
enabledboolean|null–Publish or unpublish the page.
namestring|null–New display name.
new_slugstring|null–New slug. Changing it moves the public URL and breaks existing links.
slugstringyesThe page to change, by its current slug.
timezonestring|null–IANA time zone for the times in its subscriber emails, such as `Europe/Berlin`. The page itself shows each visitor their own time.
NameTypeReqDescription
access––Who may open it, or null for a page never made private.
enabledbooleanyes–
namestringyes–
public_urlstringyes–
slugstringyes–
timezonestringyesIANA time zone of the times in its subscriber emails.

No examples provided.

update_status_page_component ~219

Change how one monitor is presented on a status page: its public name, description, group or position; or, with section_id, a group section's heading. An omitted field is left alone. A section member's heading is its section's, so its public_group does nothing. Not read-only; idempotent.

NameTypeReqDescription
headingstring|null–The section's public heading, at most 50 characters; blank shows the group's name.
monitor_idstring|null–The monitor id whose curation is being changed. Send this or `section_id`.
public_descriptionstring|null––
public_groupstring|null–Ignored on a section member, whose heading is the section's.
public_namestring|null––
section_idstring|null–A section (from `get_status_page`) whose `heading` is being changed.
slugstringyesThe page slug (from `list_status_pages`).
sort_orderinteger|null––
NameTypeReqDescription
monitor_idstring|null––
section_idstring|null––
slugstringyes–

No examples provided.

Install

How do I install the Uptimepage MCP server?

Uptimepage is a hosted endpoint at https://mcp.uptimepage.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · mcp.uptimepage.dev

# add to Claude Code
claude mcp add --transport http dev-uptimepage-uptimepage 'https://mcp.uptimepage.dev/mcp'
Common questions

What is the Uptimepage MCP server?

Uptimepage is an MCP server listed in the public MCP registry as dev.uptimepage/uptimepage. Monitor uptime and incidents, run checks, and publish status updates from your Uptimepage org. This page covers its hosted endpoint (https://mcp.uptimepage.dev/mcp).

Is the Uptimepage MCP server safe to use?

Uptimepage scores 92 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Uptimepage MCP server expose?

Uptimepage exposes 42 tools: acknowledge_incident, add_status_page_components, cancel_maintenance, create_maintenance, create_monitor, and 37 more. Their descriptions and schemas cost roughly 7,109 tokens of context every time the server is loaded.

Does the Uptimepage MCP server require authentication?

Yes. Uptimepage asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the Uptimepage MCP server still maintained?

Uptimepage is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Uptimepage MCP server?

VerifyMCP ran 13 checks on Uptimepage, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.