OneUptime
REMOTE · ONEUPTIME.COM
Manage incidents, alerts, monitors, status pages, on-call and telemetry in OneUptime.
Available components
Last scanned (7 hours ago)
Scores higher than 57% of remote servers
Reachable. Last reached 23 Oct 2026.
Category Monitoring and Observability
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 Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (create_team). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 46160 tokens (~239/item across 193 items; 193 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 Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 27 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 193 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
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.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 0
- Server version: 14.0.81 → 14.0.84 functional
- 21 Oct 26 +1
- Server version: 14.0.80 → 14.0.81 functional
- Server version: 14.0.78 → 14.0.80 functional
- 20 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- Server version: 14.0.77 → 14.0.78 functional
- Server version: 14.0.75 → 14.0.77 functional
- 19 Oct 26 66
First indexed and scored.
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 23 Oct 2026 · Probed https://oneuptime.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=oneuptime.com | CN=WE1,O=Google Trust Services,C=US | 5 Oct 2026 | 3 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | b0e2565b80ba7ebc134ccc6465d30bed |
| SANs: oneuptime.com, *.oneuptime.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of oneuptime.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| oneuptime.com. | present | 2371 | 13 | Verified |
| oneuptime.com. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://oneuptime.com/mcp | Verified | 200 | |
| http (plaintext) | http://oneuptime.com/mcp | HTTPS enforced | 301 | https://oneuptime.com/mcp |
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 →
list_scheduled_maintenance_states List Scheduled Maintenance States ~311
List and search Scheduled Maintenance States from OneUptime with optional filtering, pagination, and sorting. Returns an array of Scheduled Maintenance State objects plus the total matching count.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum number of records to return. Default: 10, Maximum: 100. |
| query | object | – | Filter criteria for Scheduled Maintenance States. Each field accepts a direct value (exact match) or an operator object {"_type": "<Operator>", "value": ...}. Operators: EqualTo, NotEqual, IsNull, No… |
| select | array | – | Optional: field names to return for each Scheduled Maintenance State (e.g. ["_id", "name"]). Omit to get all readable fields. |
| skip | number | – | Number of records to skip for pagination. Default: 0. Example: skip=10 to start from the 11th record. |
| sort | object | – | Sort order for results. Use "ASC" for ascending or "DESC" for descending. Example: {"createdAt": "DESC"} to sort by newest first. |
No output schema declared.
No examples provided.
list_security_case_notes List Security Case Notes ~309
List and search Security Case Notes from OneUptime with optional filtering, pagination, and sorting. Returns an array of Security Case Note objects plus the total matching count.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum number of records to return. Default: 10, Maximum: 100. |
| query | object | – | Filter criteria for Security Case Notes. Each field accepts a direct value (exact match) or an operator object {"_type": "<Operator>", "value": ...}. Operators: EqualTo, NotEqual, IsNull, NotNull, Eq… |
| select | array | – | Optional: field names to return for each Security Case Note (e.g. ["_id", "name"]). Omit to get all readable fields. |
| skip | number | – | Number of records to skip for pagination. Default: 0. Example: skip=10 to start from the 11th record. |
| sort | object | – | Sort order for results. Use "ASC" for ascending or "DESC" for descending. Example: {"createdAt": "DESC"} to sort by newest first. |
No output schema declared.
No examples provided.
list_security_cases List Security Cases ~327
List and search Security Cases from OneUptime with optional filtering, pagination, and sorting. Returns an array of Security Case objects plus the total matching count.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum number of records to return. Default: 10, Maximum: 100. |
| query | object | – | Filter criteria for Security Cases. Each field accepts a direct value (exact match) or an operator object {"_type": "<Operator>", "value": ...}. Operators: EqualTo, NotEqual, IsNull, NotNull, EqualTo… |
| select | array | – | Optional: field names to return for each Security Case (e.g. ["_id", "name"]). Omit to get all readable fields. Large fields excluded by default (request explicitly if needed): entities, mitreTactics… |
| skip | number | – | Number of records to skip for pagination. Default: 0. Example: skip=10 to start from the 11th record. |
| sort | object | – | Sort order for results. Use "ASC" for ascending or "DESC" for descending. Example: {"createdAt": "DESC"} to sort by newest first. |
No output schema declared.
No examples provided.
list_security_detections List Security Detections ~336
List and search Security Detections from OneUptime with optional filtering, pagination, and sorting. Returns an array of Security Detection objects plus the total matching count.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum number of records to return. Default: 10, Maximum: 100. |
| query | object | – | Filter criteria for Security Detections. Each field accepts a direct value (exact match) or an operator object {"_type": "<Operator>", "value": ...}. Operators: EqualTo, NotEqual, IsNull, NotNull, Eq… |
| select | array | – | Optional: field names to return for each Security Detection (e.g. ["_id", "name"]). Omit to get all readable fields. Large fields excluded by default (request explicitly if needed): entities, mitreTa… |
| skip | number | – | Number of records to skip for pagination. Default: 0. Example: skip=10 to start from the 11th record. |
| sort | object | – | Sort order for results. Use "ASC" for ascending or "DESC" for descending. Example: {"createdAt": "DESC"} to sort by newest first. |
No output schema declared.
No examples provided.
list_security_events List Security Events ~429
Query Security Events telemetry data from OneUptime. IMPORTANT: telemetry tables are large — always filter by a time range and keep limits small (e.g. 10-50). Each field accepts a direct value (exact match) or an operator object {"_type": "<Operator>", "value": ...}. Operators: EqualTo, NotEqual, IsNull, NotNull, EqualToOrNull, GreaterThan, LessThan, GreaterThanOrEqual, LessThanOrEqual, InBetween (numbers/dates), Search (partial text), Includes (array of values). Example — items from the last 24 hours: {"createdAt": {"_type": "GreaterThan", "value": "2026-01-01T00:00:00.000Z"}}.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum number of records to return. Default: 10, Maximum: 100. Keep small for telemetry queries. |
| query | object | – | Filter criteria for Security Events. Always include a time-range filter. Each field accepts a direct value (exact match) or an operator object {"_type": "<Operator>", "value": ...}. Operators: EqualT… |
| select | object | – | Fields to return, as an object of field names to true (e.g. {"time": true, "body": true}). Select only the fields you need — telemetry rows can be large. |
| skip | number | – | Number of records to skip. Default: 0. |
| sort | object | – | Sort order. Use "ASC" or "DESC". Example: {"time": "DESC"} for most recent first. |
No output schema declared.
No examples provided.
list_security_playbooks List Security Playbooks ~326
List and search Security Playbooks from OneUptime with optional filtering, pagination, and sorting. Returns an array of Security Playbook objects plus the total matching count.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum number of records to return. Default: 10, Maximum: 100. |
| query | object | – | Filter criteria for Security Playbooks. Each field accepts a direct value (exact match) or an operator object {"_type": "<Operator>", "value": ...}. Operators: EqualTo, NotEqual, IsNull, NotNull, Equ… |
| select | array | – | Optional: field names to return for each Security Playbook (e.g. ["_id", "name"]). Omit to get all readable fields. Large fields excluded by default (request explicitly if needed): detectionRuleIds,… |
| skip | number | – | Number of records to skip for pagination. Default: 0. Example: skip=10 to start from the 11th record. |
| sort | object | – | Sort order for results. Use "ASC" for ascending or "DESC" for descending. Example: {"createdAt": "DESC"} to sort by newest first. |
No output schema declared.
No examples provided.
list_spans List Spans ~429
Query Spans telemetry data from OneUptime. IMPORTANT: telemetry tables are large — always filter by a time range and keep limits small (e.g. 10-50). Each field accepts a direct value (exact match) or an operator object {"_type": "<Operator>", "value": ...}. Operators: EqualTo, NotEqual, IsNull, NotNull, EqualToOrNull, GreaterThan, LessThan, GreaterThanOrEqual, LessThanOrEqual, InBetween (numbers/dates), Search (partial text), Includes (array of values). Example — items from the last 24 hours: {"createdAt": {"_type": "GreaterThan", "value": "2026-01-01T00:00:00.000Z"}}.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum number of records to return. Default: 10, Maximum: 100. Keep small for telemetry queries. |
| query | object | – | Filter criteria for Spans. Always include a time-range filter. Each field accepts a direct value (exact match) or an operator object {"_type": "<Operator>", "value": ...}. Operators: EqualTo, NotEqua… |
| select | object | – | Fields to return, as an object of field names to true (e.g. {"time": true, "body": true}). Select only the fields you need — telemetry rows can be large. |
| skip | number | – | Number of records to skip. Default: 0. |
| sort | object | – | Sort order. Use "ASC" or "DESC". Example: {"time": "DESC"} for most recent first. |
No output schema declared.
No examples provided.
list_status_page_announcements List Status Page Announcements ~336
List and search Status Page Announcements from OneUptime with optional filtering, pagination, and sorting. Returns an array of Status Page Announcement objects plus the total matching count.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum number of records to return. Default: 10, Maximum: 100. |
| query | object | – | Filter criteria for Status Page Announcements. Each field accepts a direct value (exact match) or an operator object {"_type": "<Operator>", "value": ...}. Operators: EqualTo, NotEqual, IsNull, NotNu… |
| select | array | – | Optional: field names to return for each Status Page Announcement (e.g. ["_id", "name"]). Omit to get all readable fields. Large fields excluded by default (request explicitly if needed): subscriberN… |
| skip | number | – | Number of records to skip for pagination. Default: 0. Example: skip=10 to start from the 11th record. |
| sort | object | – | Sort order for results. Use "ASC" for ascending or "DESC" for descending. Example: {"createdAt": "DESC"} to sort by newest first. |
No output schema declared.
No examples provided.
list_status_pages List Status Pages ~349
List and search Status Pages from OneUptime with optional filtering, pagination, and sorting. Returns an array of Status Page objects plus the total matching count.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum number of records to return. Default: 10, Maximum: 100. |
| query | object | – | Filter criteria for Status Pages. Each field accepts a direct value (exact match) or an operator object {"_type": "<Operator>", "value": ...}. Operators: EqualTo, NotEqual, IsNull, NotNull, EqualToOr… |
| select | array | – | Optional: field names to return for each Status Page (e.g. ["_id", "name"]). Omit to get all readable fields. Large fields excluded by default (request explicitly if needed): headerHTML, footerHTML,… |
| skip | number | – | Number of records to skip for pagination. Default: 0. Example: skip=10 to start from the 11th record. |
| sort | object | – | Sort order for results. Use "ASC" for ascending or "DESC" for descending. Example: {"createdAt": "DESC"} to sort by newest first. |
No output schema declared.
No examples provided.
list_teams List Teams ~314
List and search Teams from OneUptime with optional filtering, pagination, and sorting. Returns an array of Team objects plus the total matching count.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum number of records to return. Default: 10, Maximum: 100. |
| query | object | – | Filter criteria for Teams. Each field accepts a direct value (exact match) or an operator object {"_type": "<Operator>", "value": ...}. Operators: EqualTo, NotEqual, IsNull, NotNull, EqualToOrNull, G… |
| select | array | – | Optional: field names to return for each Team (e.g. ["_id", "name"]). Omit to get all readable fields. Large fields excluded by default (request explicitly if needed): customFields. |
| skip | number | – | Number of records to skip for pagination. Default: 0. Example: skip=10 to start from the 11th record. |
| sort | object | – | Sort order for results. Use "ASC" for ascending or "DESC" for descending. Example: {"createdAt": "DESC"} to sort by newest first. |
No output schema declared.
No examples provided.
list_threat_intel_indicators List Threat Intel Indicators ~435
Query Threat Intel Indicators telemetry data from OneUptime. IMPORTANT: telemetry tables are large — always filter by a time range and keep limits small (e.g. 10-50). Each field accepts a direct value (exact match) or an operator object {"_type": "<Operator>", "value": ...}. Operators: EqualTo, NotEqual, IsNull, NotNull, EqualToOrNull, GreaterThan, LessThan, GreaterThanOrEqual, LessThanOrEqual, InBetween (numbers/dates), Search (partial text), Includes (array of values). Example — items from the last 24 hours: {"createdAt": {"_type": "GreaterThan", "value": "2026-01-01T00:00:00.000Z"}}.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum number of records to return. Default: 10, Maximum: 100. Keep small for telemetry queries. |
| query | object | – | Filter criteria for Threat Intel Indicators. Always include a time-range filter. Each field accepts a direct value (exact match) or an operator object {"_type": "<Operator>", "value": ...}. Operators… |
| select | object | – | Fields to return, as an object of field names to true (e.g. {"time": true, "body": true}). Select only the fields you need — telemetry rows can be large. |
| skip | number | – | Number of records to skip. Default: 0. |
| sort | object | – | Sort order. Use "ASC" or "DESC". Example: {"time": "DESC"} for most recent first. |
No output schema declared.
No examples provided.
oneuptime_help OneUptime Help ~887
Get help and guidance for using the OneUptime MCP server. Returns information about available resources and common operations. Use this tool first to understand what you can do with OneUptime. AVAILABLE RESOURCES: - Teams: Groups of users with shared access to project resources. - Labels: Labels for organizing and filtering project resources. - Security Cases: Manages Security Case resources in OneUptime. - Security Case Notes: Manages Security Case Note resources in OneUptime. - Security Detections: Manages Security Detection resources in OneUptime. - Security Playbooks: Manages Security Playbook resources in OneUptime. - Status Pages: Public-facing page showing the status of your services to your customers. - On-Call Duty Policies: Defines escalation rules and schedules for incident response. - Monitors: Defines what to monitor (websites, APIs, servers) and how to check their health and availability. - Monitor Statuses: Represents the health states of monitors (e.g., Operational, Degraded, Offline). - Incident States: Represents the lifecycle states of incidents (e.g., Created, Acknowledged, Resolved). - Incidents: Represents service disruptions or issues affecting your systems. Track incident lifecycle from creation to resolution. - Incident State Timelines: History of state changes for incidents. Creating an entry changes the incident's state (this is how acknowledge/resolve work). - Incident Internal Notes: Internal team-only notes on incidents. - Incident Public Notes: Status-page-visible notes on incidents, seen by customers and subscribers. - Incident Severities: Severity levels for incidents (e.g., Critical, Major, Minor). List these to find the incidentSeverityId required by create_incident. - Alert States: Lifecycle states of alerts (e.g., Created, Acknowledged, Resolved). - Alerts: Notifications triggered when monitors detect issues. Configures who gets notified and how. - Alert State Timelines: History of state changes for alerts. Creating an entry ch…
| Name | Type | Req | Description |
|---|---|---|---|
| topic | string | – | Optional topic to get help on: 'resources', 'incidents', 'monitors', 'alerts', 'workflows', or 'examples' |
No output schema declared.
No examples provided.
oneuptime_list_resources List OneUptime Resources ~37
List all available OneUptime resources and their supported operations. Use this to discover what resources you can manage through the MCP server.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
oneuptime_whoami Who Am I ~73
Get the project your credentials belong to (ID and name), and - when signed in with OAuth - who you are signed in as and whether you may make changes. Call this first to understand your context. Note: create tools infer projectId from your credentials automatically, so you never need to pass it.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
resolve_alert Resolve Alert ~44
Resolve an alert: moves it to the project's 'Resolved' state.
| Name | Type | Req | Description |
|---|---|---|---|
| alertId | string | yes | UUID of the alert to resolve. Use list_alerts to find it. |
No output schema declared.
No examples provided.
resolve_incident Resolve Incident ~58
Resolve an incident: moves it to the project's 'Resolved' state. Equivalent to pressing 'Resolve' in the OneUptime dashboard.
| Name | Type | Req | Description |
|---|---|---|---|
| incidentId | string | yes | UUID of the incident to resolve. Use list_incidents to find it. |
No output schema declared.
No examples provided.
update_alert Update Alert ~693
Update an existing Alert in OneUptime. Only include the fields you want to change - unspecified fields will remain unchanged. Use get_alert afterwards to see the updated record.
| Name | Type | Req | Description |
|---|---|---|---|
| alertSeverityId | string | – | Alert Severity ID. |
| cephClusters | array | – | List of Ceph clusters affected by this alert. |
| currentAlertStateId | string | – | Current Alert State ID. |
| customFields | object | – | Custom Fields on this resource. |
| databaseServers | array | – | List of databases affected by this alert. |
| description | string | – | Short description of this alert. This will be visible on the status page. This is in markdown. |
| dockerHosts | array | – | List of Docker hosts affected by this alert. |
| dockerResources | array | – | List of Docker resources (containers, images, networks, volumes) affected by this alert. |
| dockerSwarmClusters | array | – | List of Docker Swarm clusters affected by this alert. |
| enableReminders | boolean | – | Should reminder notifications be sent to owners while this alert is still open? Reminders are sent based on the reminder rules configured for this project. |
| hosts | array | – | List of hosts affected by this alert. |
| id | string | yes | The unique identifier (UUID) of the Alert to update. Required. Use list_alerts to find IDs. |
| impactStartedAt | object | – | When customer impact actually began. Left blank until someone records it - never inferred, because a guessed value is worse than no value. |
| iotFleets | array | – | List of IoT fleets affected by this alert. |
| isPrivate | boolean | – | If true, this alert is only visible to its owners (users in 'owner users' and members of 'owner teams'), project admins, and project owners. |
| kubernetesClusters | array | – | List of Kubernetes clusters affected by this alert. |
| kubernetesContainers | array | – | List of Kubernetes containers affected by this alert. |
| kubernetesResources | array | – | List of Kubernetes resources (pods, deployments, nodes, etc.) affected by this alert. |
| labels | array | – | Relation to Labels Array where this object is categorized in. |
| monitorId | string | – | ID of the monitor this alert belongs to. |
| monitorStatusWhenThisAlertWasCreatedId | string | – | Monitor Status ID when this alert was created. |
| onCallDutyPolicies | array | – | List of on-call duty policies affected by this alert. |
| podmanHosts | array | – | List of Podman hosts affected by this alert. |
| podmanResources | array | – | List of Podman resources (containers, images, networks, volumes) affected by this alert. |
| proxmoxClusters | array | – | List of Proxmox clusters affected by this alert. |
| remediationNotes | string | – | Notes on how to remediate this alert. This is in markdown. |
| serviceLevelObjectives | array | – | List of Service Level Objectives (SLOs) affected by this alert. |
| services | array | – | List of services affected by this alert. |
| storageArrays | array | – | List of storage arrays affected by this alert. |
| telemetryQuery | object | – | Telemetry query for this alert. |
| title | string | – | Title of this alert. |
| vmwareVCenters | array | – | List of vCenters affected by this alert. |
No output schema declared.
No examples provided.
update_alert_internal_note Update Alert Internal Note ~144
Update an existing Alert Internal Note in OneUptime. Only include the fields you want to change - unspecified fields will remain unchanged. Use get_alert_internal_note afterwards to see the updated record.
| Name | Type | Req | Description |
|---|---|---|---|
| attachments | array | – | Files attached to this note. |
| id | string | yes | The unique identifier (UUID) of the Alert Internal Note to update. Required. Use list_alert_internal_notes to find IDs. |
| note | string | – | Notes in markdown. |
| postedAt | object | – | Date and time the note belongs to in the timeline: when it was written, or - for a note saved from a Slack or Microsoft Teams message - when that message was posted. |
No output schema declared.
No examples provided.
update_alert_severity Update Alert Severity ~192
Update an existing Alert Severity in OneUptime. Only include the fields you want to change - unspecified fields will remain unchanged. Use get_alert_severity afterwards to see the updated record.
| Name | Type | Req | Description |
|---|---|---|---|
| color | object | – | Color of this resource in Hex (#32a852 for example). |
| description | string | – | Friendly description that will help you remember. |
| id | string | yes | The unique identifier (UUID) of the Alert Severity to update. Required. Use list_alert_severities to find IDs. |
| name | string | – | Any friendly name of this object. |
| order | integer | – | Where this severity ranks among the project's alert severities: 1 is the most severe. A new severity without a number goes to the end of the list. Setting a number moves the severity to that place, a… |
No output schema declared.
No examples provided.
update_alert_state Update Alert State ~285
Update an existing Alert State in OneUptime. Only include the fields you want to change - unspecified fields will remain unchanged. Use get_alert_state afterwards to see the updated record.
| Name | Type | Req | Description |
|---|---|---|---|
| color | object | – | Color of this resource in Hex (#32a852 for example). |
| description | string | – | Friendly description that will help you remember. |
| id | string | yes | The unique identifier (UUID) of the Alert State to update. Required. Use list_alert_states to find IDs. |
| isAcknowledgedState | boolean | – | Is it the acknowledged state of the alert? |
| isCreatedState | boolean | – | Is it the created state of the alert? |
| isResolvedState | boolean | – | Is it the resolved state of the alert? |
| name | string | – | Any friendly name of this object. |
| order | integer | – | Where this state sits in the project's list of alert states: 1 is the top. Alerts only ever move down the list, and an alert in a state at or below the acknowledged (or resolved) state counts as ackn… |
No output schema declared.
No examples provided.
update_alert_state_timeline Update Alert State Timeline ~140
Update an existing Alert State Timeline in OneUptime. Only include the fields you want to change - unspecified fields will remain unchanged. Use get_alert_state_timeline afterwards to see the updated record.
| Name | Type | Req | Description |
|---|---|---|---|
| alertStateId | string | – | Alert State ID Relation. Which alert state does this alert change to? |
| id | string | yes | The unique identifier (UUID) of the Alert State Timeline to update. Required. Use list_alert_state_timelines to find IDs. |
| startsAt | object | – | When did this status change? Correct this when the recorded time is wrong - every measurement derived from this timeline is recomputed from the corrected value. |
No output schema declared.
No examples provided.
update_incident Update Incident ~1,050
Update an existing Incident in OneUptime. Only include the fields you want to change - unspecified fields will remain unchanged. Use get_incident afterwards to see the updated record.
| Name | Type | Req | Description |
|---|---|---|---|
| cephClusters | array | – | List of Ceph clusters affected by this incident. |
| changeMonitorStatusToId | string | – | Relation to Monitor Status Object ID. All monitors connected to this incident will be changed to this status when the incident is created. |
| currentIncidentStateId | string | – | Current Incident State ID. |
| customFields | object | – | The incident's custom field values, keyed by each incident custom field's name. When a user or an API key creates or updates an incident, each value it sets or changes must fit its field - a number f… |
| databaseServers | array | – | List of databases affected by this incident. |
| declaredAt | object | – | Date and time when this incident was declared. |
| description | string | – | Short description of this incident. This is in markdown and will be visible on the status page. |
| dockerHosts | array | – | List of Docker hosts affected by this incident. |
| dockerResources | array | – | List of Docker resources (containers, images, networks, volumes) affected by this incident. |
| dockerSwarmClusters | array | – | List of Docker Swarm clusters affected by this incident. |
| enableReminders | boolean | – | Should reminder notifications be sent to owners while this incident is still open? Reminders are sent based on the reminder rules configured for this project. |
| hosts | array | – | List of hosts affected by this incident. |
| id | string | yes | The unique identifier (UUID) of the Incident to update. Required. Use list_incidents to find IDs. |
| impactStartedAt | object | – | When customer impact actually began. Left blank until someone records it - never inferred, because a guessed value is worse than no value. |
| incidentSeverityId | string | – | Incident Severity ID. |
| iotFleets | array | – | List of IoT fleets affected by this incident. |
| isPrivate | boolean | – | If true, this incident is only visible to its owners (users in 'owner users' and members of 'owner teams'), project admins, and project owners. Private incidents are hidden from status pages. |
| isVisibleOnStatusPage | boolean | – | Should this incident be visible on the status page? |
| kubernetesClusters | array | – | List of Kubernetes clusters affected by this incident. |
| kubernetesContainers | array | – | List of Kubernetes containers affected by this incident. |
| kubernetesResources | array | – | List of Kubernetes resources (pods, deployments, nodes, etc.) affected by this incident. |
| labels | array | – | Relation to Labels Array where this object is categorized in. |
| monitors | array | – | List of monitors affected by this incident. |
| notifySubscribersOnPostmortemPublished | boolean | – | Should subscribers be notified when the postmortem is published? |
| onCallDutyPolicies | array | – | List of on-call duty policies affected by this incident. |
| podmanHosts | array | – | List of Podman hosts affected by this incident. |
| podmanResources | array | – | List of Podman resources (containers, images, networks, volumes) affected by this incident. |
| postmortemAttachments | array | – | Files that accompany the postmortem note and can be shared publicly when enabled. |
| postmortemNote | string | – | Document the postmortem summary for this incident. |
| postmortemPostedAt | object | – | Timestamp that will be shown alongside the published postmortem on the status page. |
| proxmoxClusters | array | – | List of Proxmox clusters affected by this incident. |
| remediationNotes | string | – | Notes on how to remediate this incident. This is in markdown. |
| rootCause | string | – | What is the root cause of this incident? |
| serviceLevelObjectives | array | – | List of Service Level Objectives (SLOs) affected by this incident. |
| services | array | – | List of services affected by this incident. |
| showPostmortemOnStatusPage | boolean | – | Should the postmortem note and attachments be visible on the status page once published? |
| statusPages | array | – | Limit this incident to these status pages. When set, the incident is shown on, and notifies the subscribers of, only these pages among the status pages that list its monitors. Leave empty to reach ev… |
| storageArrays | array | – | List of storage arrays affected by this incident. |
| telemetryQuery | object | – | Telemetry query for this incident. |
| title | string | – | Title of this incident. |
| vmwareVCenters | array | – | List of vCenters affected by this incident. |
No output schema declared.
No examples provided.
update_incident_alert Update Incident Alert ~78
Update an existing Incident Alert in OneUptime. Only include the fields you want to change - unspecified fields will remain unchanged. Use get_incident_alert afterwards to see the updated record.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier (UUID) of the Incident Alert to update. Required. Use list_incident_alerts to find IDs. |
No output schema declared.
No examples provided.
update_incident_internal_note Update Incident Internal Note ~147
Update an existing Incident Internal Note in OneUptime. Only include the fields you want to change - unspecified fields will remain unchanged. Use get_incident_internal_note afterwards to see the updated record.
| Name | Type | Req | Description |
|---|---|---|---|
| attachments | array | – | Files attached to this note. |
| id | string | yes | The unique identifier (UUID) of the Incident Internal Note to update. Required. Use list_incident_internal_notes to find IDs. |
| note | string | – | Notes in markdown. |
| postedAt | object | – | Date and time the note belongs to in the timeline: when it was written, or - for a note saved from a Slack or Microsoft Teams message - when that message was posted. |
No output schema declared.
No examples provided.
update_incident_public_note Update Incident Public Note ~120
Update an existing Incident Public Note in OneUptime. Only include the fields you want to change - unspecified fields will remain unchanged. Use get_incident_public_note afterwards to see the updated record.
| Name | Type | Req | Description |
|---|---|---|---|
| attachments | array | – | Files attached to this note. |
| id | string | yes | The unique identifier (UUID) of the Incident Public Note to update. Required. Use list_incident_public_notes to find IDs. |
| note | string | – | Notes in markdown. |
| postedAt | object | – | Date and time when the note was posted. |
No output schema declared.
No examples provided.
update_incident_severity Update Incident Severity ~195
Update an existing Incident Severity in OneUptime. Only include the fields you want to change - unspecified fields will remain unchanged. Use get_incident_severity afterwards to see the updated record.
| Name | Type | Req | Description |
|---|---|---|---|
| color | object | – | Color of this resource in Hex (#32a852 for example). |
| description | string | – | Friendly description that will help you remember. |
| id | string | yes | The unique identifier (UUID) of the Incident Severity to update. Required. Use list_incident_severities to find IDs. |
| name | string | – | Any friendly name of this object. |
| order | integer | – | Where this severity ranks among the project's incident severities: 1 is the most severe. A new severity without a number goes to the end of the list. Setting a number moves the severity to that place… |
No output schema declared.
No examples provided.
update_incident_state Update Incident State ~289
Update an existing Incident State in OneUptime. Only include the fields you want to change - unspecified fields will remain unchanged. Use get_incident_state afterwards to see the updated record.
| Name | Type | Req | Description |
|---|---|---|---|
| color | object | – | Color of this resource in Hex (#32a852 for example). |
| description | string | – | Friendly description that will help you remember. |
| id | string | yes | The unique identifier (UUID) of the Incident State to update. Required. Use list_incident_states to find IDs. |
| isAcknowledgedState | boolean | – | Is it the acknowledged state of the incident? |
| isCreatedState | boolean | – | Is it the created state of the incident? |
| isResolvedState | boolean | – | Is it the resolved state of the incident? |
| name | string | – | Any friendly name of this object. |
| order | integer | – | Where this state sits in the project's list of incident states: 1 is the top. Incidents only ever move down the list, and an incident in a state at or below the acknowledged (or resolved) state count… |
No output schema declared.
No examples provided.
update_incident_state_timeline Update Incident State Timeline ~143
Update an existing Incident State Timeline in OneUptime. Only include the fields you want to change - unspecified fields will remain unchanged. Use get_incident_state_timeline afterwards to see the updated record.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier (UUID) of the Incident State Timeline to update. Required. Use list_incident_state_timelines to find IDs. |
| incidentStateId | string | – | Incident State ID Relation. Which incident state does this incident change to? |
| startsAt | object | – | When did this status change? Correct this when the recorded time is wrong - every measurement derived from this timeline is recomputed from the corrected value. |
No output schema declared.
No examples provided.
update_label Update Label ~115
Update an existing Label in OneUptime. Only include the fields you want to change - unspecified fields will remain unchanged. Use get_label afterwards to see the updated record.
| Name | Type | Req | Description |
|---|---|---|---|
| color | object | – | Color of this resource in Hex (#32a852 for example). |
| description | string | – | Friendly description that will help you remember. |
| id | string | yes | The unique identifier (UUID) of the Label to update. Required. Use list_labels to find IDs. |
| name | string | – | Any friendly name of this object. |
No output schema declared.
No examples provided.
update_monitor Update Monitor ~934
Update an existing Monitor in OneUptime. Only include the fields you want to change - unspecified fields will remain unchanged. Use get_monitor afterwards to see the updated record.
| Name | Type | Req | Description |
|---|---|---|---|
| cephClusters | array | – | Ceph clusters this monitor watches. Incidents and alerts it creates are linked to them, so OneUptime AI can investigate and fix them there. |
| currentMonitorStatusId | string | – | Whats the current status ID of this monitor? |
| customFields | object | – | Custom Fields on this resource. |
| databaseServers | array | – | Databases this monitor watches. Incidents and alerts it creates are linked to them, so OneUptime AI can investigate and fix them there. |
| dependsOnMonitors | array | – | Parent monitors this monitor depends on. When a parent is offline (or in one of the configured suppression statuses), alerts and incidents from this monitor are suppressed at creation time — the moni… |
| description | string | – | Friendly description that will help you remember. |
| disableActiveMonitoring | boolean | – | Disable active monitoring for this resource? |
| dockerHosts | array | – | Docker hosts this monitor watches. Incidents and alerts it creates are linked to them, so OneUptime AI can investigate and fix them there. |
| dockerSwarmClusters | array | – | Docker Swarm clusters this monitor watches. Incidents and alerts it creates are linked to them, so OneUptime AI can investigate and fix them there. |
| hosts | array | – | Hosts this monitor watches. Incidents and alerts it creates are linked to them, so OneUptime AI can investigate and fix them there. |
| id | string | yes | The unique identifier (UUID) of the Monitor to update. Required. Use list_monitors to find IDs. |
| incomingEmailCustomLocalPart | string | – | This field is for Incoming Email Monitor only. A custom name for this monitor's inbound email address: the part before the @, on the server's inbound email domain. While set, it replaces the generate… |
| iotFleets | array | – | IoT fleets this monitor watches. Incidents and alerts it creates are linked to them, so OneUptime AI can investigate and fix them there. |
| isArchived | boolean | – | Archived monitors are hidden from monitor lists and status pages, are not checked, and open no incidents or alerts. Unarchiving resumes monitoring. |
| kubernetesClusters | array | – | Kubernetes clusters this monitor watches. Incidents and alerts it creates are linked to them, so OneUptime AI can investigate and fix them there. |
| labels | array | – | Relation to Labels Array where this object is categorized in. |
| minimumProbeAgreement | number | – | Minimum number of probes that must agree on a status before the monitor status changes. If null, all enabled and connected probes must agree. |
| monitorSteps | object | – | What would you like to monitor and what is the criteria? |
| monitorTemplateId | string | – | ID of the Monitor Template this monitor was created from. Null for monitors not created from a template. |
| monitoringInterval | string | – | How often would you like OneUptime to monitor this resource? A 5-field cron expression, not a label: "*/5 * * * *" is every five minutes. |
| name | string | – | Any friendly name for this monitor. |
| podmanHosts | array | – | Podman hosts this monitor watches. Incidents and alerts it creates are linked to them, so OneUptime AI can investigate and fix them there. |
| proxmoxClusters | array | – | Proxmox clusters this monitor watches. Incidents and alerts it creates are linked to them, so OneUptime AI can investigate and fix them there. |
| services | array | – | Services this monitor watches. Incidents and alerts it creates are linked to them, so OneUptime AI can investigate and fix them there. |
| storageArrays | array | – | Storage arrays this monitor watches. Incidents and alerts it creates are linked to them. |
| suppressAlertsWhenParentMonitorStatuses | array | – | Parent monitor statuses that suppress this monitor's alerts and incidents. When empty, statuses flagged as offline suppress (the default). Only used when Depends On Monitors is set. |
| vmwareVCenters | array | – | VMware vCenters this monitor watches. Incidents and alerts it creates are linked to them, so OneUptime AI can investigate and fix them there. |
No output schema declared.
No examples provided.
update_monitor_status Update Monitor Status ~251
Update an existing Monitor Status in OneUptime. Only include the fields you want to change - unspecified fields will remain unchanged. Use get_monitor_status afterwards to see the updated record.
| Name | Type | Req | Description |
|---|---|---|---|
| color | object | – | Color of this resource in Hex (#32a852 for example). |
| description | string | – | Friendly description that will help you remember. |
| id | string | yes | The unique identifier (UUID) of the Monitor Status to update. Required. Use list_monitor_statuses to find IDs. |
| isOfflineState | boolean | – | Is this monitor in offline state? |
| isOperationalState | boolean | – | Is this monitor in operational state? |
| name | string | – | Any friendly name of this object. |
| priority | number | – | Where this status sits in the project's list of monitor statuses, from the healthiest (the lowest number) down to the worst: where monitors are shown together, as on a status page or in a monitor gro… |
No output schema declared.
No examples provided.
update_monitor_status_event Update Monitor Status Event ~99
Update an existing Monitor Status Event in OneUptime. Only include the fields you want to change - unspecified fields will remain unchanged. Use get_monitor_status_event afterwards to see the updated record.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier (UUID) of the Monitor Status Event to update. Required. Use list_monitor_status_events to find IDs. |
| monitorStatusId | string | – | Relation to Monitor Status ID Resource in which this object belongs. |
No output schema declared.
No examples provided.
update_on_call_policy Update On-Call Policy ~235
Update an existing On-Call Policy in OneUptime. Only include the fields you want to change - unspecified fields will remain unchanged. Use get_on_call_policy afterwards to see the updated record.
| Name | Type | Req | Description |
|---|---|---|---|
| customFields | object | – | Custom Fields on this resource. |
| description | string | – | Friendly description that will help you remember. |
| id | string | yes | The unique identifier (UUID) of the On-Call Policy to update. Required. Use list_on_call_duty_policies to find IDs. |
| isArchived | boolean | – | Archived on-call policies are hidden from the On-Call Policies list and page no one: incidents and alerts that use them skip them. Unarchiving puts them back in service. |
| labels | array | – | Relation to Labels Array where this object is categorized in. |
| name | string | – | Any friendly name of this object. |
| repeatPolicyIfNoOneAcknowledges | boolean | – | Repeat the policy if no one acknowledges the alert. |
| repeatPolicyIfNoOneAcknowledgesNoOfTimes | number | – | Repeat the policy X number of times if no one acknowledges the alert. |
No output schema declared.
No examples provided.
update_scheduled_maintenance_event Update Scheduled Maintenance Event ~612
Update an existing Scheduled Maintenance Event in OneUptime. Only include the fields you want to change - unspecified fields will remain unchanged. Use get_scheduled_maintenance_event afterwards to see the updated record.
| Name | Type | Req | Description |
|---|---|---|---|
| cephClusters | array | – | List of Ceph clusters affected by this event. |
| changeMonitorStatusToId | string | – | Relation to Monitor Status Object ID. The monitors attached to this event change to this status when the event starts, and back to operational when it ends. It can be changed until the event starts. |
| currentScheduledMaintenanceStateId | string | – | Scheduled Maintenance State ID. The state the event currently is in. |
| customFields | object | – | Custom Fields on this resource. |
| databaseServers | array | – | List of databases affected by this event. |
| description | string | – | Description of this scheduled event that will show up on Status Page. This is in markdown. |
| dockerHosts | array | – | List of Docker hosts affected by this event. |
| dockerSwarmClusters | array | – | List of Docker Swarm clusters affected by this event. |
| enableReminders | boolean | – | Should reminder notifications be sent to owners while this scheduled maintenance event is still not complete? Reminders are sent based on the reminder rules configured for this project. |
| endsAt | object | – | When does this event end? |
| hosts | array | – | List of hosts affected by this event. |
| id | string | yes | The unique identifier (UUID) of the Scheduled Maintenance Event to update. Required. Use list_scheduled_maintenance_events to find IDs. |
| iotFleets | array | – | List of IoT fleets affected by this event. |
| isVisibleOnStatusPage | boolean | – | Should this incident be visible on the status page? |
| kubernetesClusters | array | – | List of Kubernetes clusters affected by this event. |
| labels | array | – | Relation to Labels Array where this object is categorized in. |
| monitors | array | – | List of monitors attached to this event. |
| networkSites | array | – | List of network sites affected by this event. Their descendants are covered too. |
| nextSubscriberNotificationBeforeTheEventAt | object | – | When will the next notification to subscribers be sent out? |
| podmanHosts | array | – | List of Podman hosts affected by this event. |
| proxmoxClusters | array | – | List of Proxmox clusters affected by this event. |
| sendSubscriberNotificationsOnBeforeTheEvent | object | – | Should subscribers be notified before the event? |
| services | array | – | List of services affected by this event. |
| startsAt | object | – | When does this event start? |
| statusPages | array | – | List of status pages to show this event on. |
| storageArrays | array | – | List of storage arrays affected by this event. |
| title | string | – | Title of this scheduled event. |
| vmwareVCenters | array | – | List of vCenters affected by this event. |
No output schema declared.
No examples provided.
update_scheduled_maintenance_state Update Scheduled Maintenance State ~285
Update an existing Scheduled Maintenance State in OneUptime. Only include the fields you want to change - unspecified fields will remain unchanged. Use get_scheduled_maintenance_state afterwards to see the updated record.
| Name | Type | Req | Description |
|---|---|---|---|
| color | object | – | Color of this resource in Hex (#32a852 for example). |
| description | string | – | Friendly description that will help you remember. |
| id | string | yes | The unique identifier (UUID) of the Scheduled Maintenance State to update. Required. Use list_scheduled_maintenance_states to find IDs. |
| isEndedState | boolean | – | Is this state a ended state? |
| isOngoingState | boolean | – | Is this state a ongoing state? |
| isResolvedState | boolean | – | Is this state a resolved state? |
| isScheduledState | boolean | – | Is this state a scheduled state? |
| name | string | – | Any friendly name of this object. |
| order | integer | – | Where this state sits in the project's list of scheduled maintenance states: 1 is the top. Events only ever move down the list, so the scheduled, ongoing, ended and completed states have to stay in t… |
No output schema declared.
No examples provided.
update_scheduled_maintenance_state_timeline Update Scheduled Maintenance State Timeline ~152
Update an existing Scheduled Maintenance State Timeline in OneUptime. Only include the fields you want to change - unspecified fields will remain unchanged. Use get_scheduled_maintenance_state_timeline afterwards to see the updated record.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier (UUID) of the Scheduled Maintenance State Timeline to update. Required. Use list_scheduled_maintenance_state_timelines to find IDs. |
| scheduledMaintenanceStateId | string | – | Scheduled Maintenance State ID. Which state does this event belongs to? |
| startsAt | object | – | When did this status change? Correct this when the recorded time is wrong - every measurement derived from this timeline is recomputed from the corrected value. |
No output schema declared.
No examples provided.
update_security_case Update Security Case ~394
Update an existing Security Case in OneUptime. Only include the fields you want to change - unspecified fields will remain unchanged. Use get_security_case afterwards to see the updated record.
| Name | Type | Req | Description |
|---|---|---|---|
| assignedToTeamId | string | – | ID of the team whose queue the case is in. |
| assignedToUserId | string | – | ID of the person working the case. |
| closingNote | string | – | Why the case was closed the way it was, in Markdown: what was found and what was done. |
| description | string | – | What is known about the threat, in Markdown. A case opened by a detection starts with the detection's description. |
| entities | object | – | The users, hosts, IP addresses, domains and files the case is about, each as { type, value }. Detections add theirs as they join the case. |
| id | string | yes | The unique identifier (UUID) of the Security Case to update. Required. Use list_security_cases to find IDs. |
| labels | array | – | Labels to filter and report on cases by. |
| mitreTactics | object | – | ATT&CK tactic ids (TA0006) the case's detections are tagged with. |
| mitreTechniques | object | – | ATT&CK technique ids (T1110) the case's detections are tagged with. |
| priority | string | – | Critical, High, Medium, Low or Informational. A case opened by a detection starts at the detection's severity and rises when a more severe one joins it. |
| status | string | – | New, Investigating, Contained or Closed. Every case starts New; closing it records a verdict. |
| title | string | – | What the case is about, in a line. |
| verdict | string | – | What the case turned out to be, set when it is closed: True Positive, Benign Positive, False Positive or Undetermined. |
No output schema declared.
No examples provided.
update_security_case_note Update Security Case Note ~91
Update an existing Security Case Note in OneUptime. Only include the fields you want to change - unspecified fields will remain unchanged. Use get_security_case_note afterwards to see the updated record.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier (UUID) of the Security Case Note to update. Required. Use list_security_case_notes to find IDs. |
| note | string | – | The note, in Markdown. |
No output schema declared.
No examples provided.
update_security_detection Update Security Detection ~76
Update an existing Security Detection in OneUptime. Only include the fields you want to change - unspecified fields will remain unchanged. Use get_security_detection afterwards to see the updated record.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier (UUID) of the Security Detection to update. Required. Use list_security_detections to find IDs. |
No output schema declared.
No examples provided.
update_security_playbook Update Security Playbook ~314
Update an existing Security Playbook in OneUptime. Only include the fields you want to change - unspecified fields will remain unchanged. Use get_security_playbook afterwards to see the updated record.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | When to use the playbook and what it is for. |
| detectionRuleIds | object | – | Run only on cases with a detection from one of these detection rules. Empty runs on cases from any rule. |
| detectionSource | string | – | Run only on cases raised by this source: a Detection Rule, Threat Intel or a Connected Product. Empty runs on every source. |
| id | string | yes | The unique identifier (UUID) of the Security Playbook to update. Required. Use list_security_playbooks to find IDs. |
| isEnabled | boolean | – | Whether the playbook runs on its own. A disabled playbook can still be run by hand from a case. |
| minimumPriority | string | – | Run only on cases at this priority or above. Empty runs on every priority. |
| name | object | – | What the playbook does, in a few words. |
| steps | object | – | The steps the playbook takes, in order. Each has an action, its settings, and whether it needs approval, may fail without stopping the run, or runs only when threat intel matched. |
| trigger | string | – | When the playbook runs on its own: Case Opened, Detection Added (a new detection joins an open case), or Manual (only when somebody runs it). |
No output schema declared.
No examples provided.
update_status_page Update Status Page ~2,049
Update an existing Status Page in OneUptime. Only include the fields you want to change - unspecified fields will remain unchanged. Use get_status_page afterwards to see the updated record.
| Name | Type | Req | Description |
|---|---|---|---|
| allowSubscribersToChooseEventTypes | boolean | – | Can subscribers choose which event type like Announcements, Incidents, Scheduled Events to subscribe to? |
| allowSubscribersToChooseResources | boolean | – | Can subscribers choose which resources to subscribe to? |
| allowedSubscriberEmailDomains | string | – | The domains an email subscriber's address may be at, one a line, such as acme.com. An address at a subdomain of one matches too. Sign-ups and additions at any other domain are refused, and an email s… |
| callSmsConfigId | string | – | ID of your Call/SMS Config Resource which is used to send SMS to subscribers. |
| copyrightText | string | – | Copyright Text. |
| coverImageAltText | string | – | Alternative text for the cover image, read by screen readers for accessibility. Leave blank if the cover image is purely decorative. |
| coverImageFileId | string | – | Status Page Cover Image ID. |
| customCSS | string | – | Status Page Custom CSS. Served only from a verified custom domain. |
| customFields | object | – | Custom Fields on this resource. |
| customJavaScript | string | – | Status Page Custom JavaScript. This runs when the status page is loaded from a verified custom domain. |
| defaultBarColor | object | – | Default color of the bar on the overview page. |
| defaultLanguage | string | – | Default language that the status page is shown in when a visitor arrives for the first time. |
| description | string | – | Friendly description that will help you remember. |
| embeddedOverallStatusToken | string | – | Security token required to access the embedded overall status badge. This token must be provided in the URL. |
| enableCustomSubscriberEmailNotificationFooterText | boolean | – | Enable custom footer text in subscriber email notifications. |
| enableEmailSubscribers | boolean | – | Can email subscribers subscribe to this Status Page? |
| enableEmbeddedOverallStatus | boolean | – | Enable embedded overall status badge that can be displayed on external websites? |
| enableMasterPassword | boolean | – | Require visitors to enter a master password before viewing a private status page. |
| enableMcpServer | boolean | – | Can AI agents read this status page over the public OneUptime MCP server? This does not affect the status page website, its RSS feed, or its public JSON API. |
| enableMicrosoftTeamsSubscribers | boolean | – | Can Microsoft Teams subscribers subscribe to this Status Page? |
| enableSearchEngineIndexing | boolean | – | Should search engines like Google and Bing be allowed to index this status page? Turn this off to keep the page reachable by link but out of search results. |
| enableSlackSubscribers | boolean | – | Can Slack subscribers subscribe to this Status Page? |
| enableSmsSubscribers | boolean | – | Can SMS subscribers subscribe to this Status Page? |
| enableWebhookSubscribers | boolean | – | Can Webhook subscribers subscribe to this Status Page? |
| enabledLanguages | object | – | Languages offered in the footer language switcher. Leave empty to offer all supported languages. |
| faviconFileId | string | – | Status Page Favicon File ID. |
| footerHTML | string | – | Status Page Custom HTML Footer. Served only from a verified custom domain. |
| headerHTML | string | – | Status Page Custom HTML Header. Served only from a verified custom domain. |
| hidePoweredByOneUptimeBranding | boolean | – | Hide Powered By OneUptime Branding? |
| id | string | yes | The unique identifier (UUID) of the Status Page to update. Required. Use list_status_pages to find IDs. |
| ipWhitelist | string | – | IP Whitelist for this Status Page. One IP per line. Only used if the status page is private. |
| isArchived | boolean | – | Archived status pages are hidden from the Status Pages list, are not served to visitors, and send nothing to their subscribers. Unarchiving puts them back online. |
| isPublicStatusPage | boolean | – | Is this status page public? |
| isReportEnabled | boolean | – | Whether this status page's email subscribers get reports. Turned on without a schedule, reports go out on the 1st of every month at 09:00 in the report timezone, each covering the calendar month befo… |
| labels | array | – | Relation to Labels Array where this object is categorized in. |
| limitSubscribersToPrivateUsers | boolean | – | Only people who can sign in to this status page can be its subscribers, each with the email address they sign in with: no other address, and no phone, Slack, Microsoft Teams or webhook. A subscriber… |
| logoAltText | string | – | Alternative text for the logo image, read by screen readers for accessibility. |
| logoFileId | string | – | Status Page Logo File ID. |
| masterPassword | string | – | Password required to unlock a private status page. This value is stored as a secure hash. |
| name | string | – | Any friendly name of this object. |
| onlyShowScopedIncidents | boolean | – | When on, this status page shows and notifies its subscribers about only the incidents limited to it. Incidents that are not limited to any status page never reach it. |
| overallUptimePercentPrecision | string | – | Overall Precision of uptime percent for this status page. |
| overviewPageDescription | string | – | Overview Page description for your status page. This is a markdown field. |
| pageDescription | string | – | Description of your Status Page. This is used for SEO. |
| pageTitle | string | – | Title of your Status Page. This is used for SEO. |
| privateUserSessionLengthInHours | number | – | How long, in hours, a private user stays signed in to this private status page after signing in, however active they are - with a password, SSO or OIDC. When the time is up they sign in again. Applie… |
| reportDataInDays | number | – | How many days of data should be included in the report? |
| reportPeriodType | string | – | Should the report cover a rolling number of days, or the previous whole calendar period? |
| reportRecurringInterval | object | – | How often a report goes out. Left out when reports are turned on, it is every month. |
| reportStartDateTime | object | – | When the first report goes out. Every later one follows it by the recurring interval, at the same time of day. Left out when reports are turned on, it is 09:00 in the report timezone at the start of… |
| reportTimezone | string | – | The timezone report periods and send times are resolved in. A monthly report in this timezone runs from the 1st at 00:00 to the last day at 23:59. |
| requireSsoForLogin | boolean | – | Should SSO be required to login to Private Status Page. |
| sendNextReportBy | object | – | When the next report goes out. The server works it out from the schedule. |
| sendSubscriberNotifications | boolean | – | Does this status page tell its subscribers anything? Off, it sends them nothing - no message about an incident, an episode, scheduled maintenance or an announcement, and no report - however the event… |
| showAnnouncementHistoryInDays | number | – | How many days of announcement history should be shown on the status page (in days)? |
| showAnnouncementsOnStatusPage | boolean | – | Show Announcements on Status Page? |
| showEpisodeHistoryInDays | number | – | How many days of episode history to show on the status page. |
| showEpisodeLabelsOnStatusPage | boolean | – | Show Episode Labels on Status Page? |
| showEpisodesOnStatusPage | boolean | – | Show Incident Episodes on Status Page? |
| showIncidentHistoryInDays | number | – | How many days of incident history should be shown on the status page (in days)? |
| showIncidentLabelsOnStatusPage | boolean | – | Show Incident Labels on Status Page? |
| showIncidentsOnStatusPage | boolean | – | Show Incidents on Status Page? |
| showOverallUptimePercentOnStatusPage | boolean | – | Show Overall Uptime Percent on Status Page? |
| showScheduledEventHistoryInDays | number | – | How many days of scheduled event history should be shown on the status page (in days)? |
| showScheduledEventLabelsOnStatusPage | boolean | – | Show Scheduled Event Labels on Status Page? |
| showScheduledMaintenanceEventsOnStatusPage | boolean | – | Show Scheduled Maintenance Events on Status Page? |
| showSubscriberPageOnStatusPage | boolean | – | Show Subscriber Page on Status Page? |
| showUptimeHistoryInDays | number | – | How many days of uptime history should be shown on the status page? Maximum is 90 days. |
| smtpConfigId | string | – | ID of your SMTP Config Resource which is used to send email to subscribers. |
| subscriberEmailNotificationFooterText | string | – | Text to send to subscribers in the footer of the email. |
| subscriberTimezones | object | – | Timezones of subscribers to this status page. |
| theme | string | – | How the status page looks to visitors: Light, Dark, or System (light or dark, as each visitor's device is set). A status page created without a theme starts with System. |
No output schema declared.
No examples provided.
How do I install the OneUptime MCP server?
OneUptime is a hosted endpoint at https://oneuptime.com/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 · oneuptime.com
claude mcp add --transport http com-oneuptime-mcp 'https://oneuptime.com/mcp'
What is the OneUptime MCP server?
OneUptime is an MCP server listed in the public MCP registry as com.oneuptime/mcp. Manage incidents, alerts, monitors, status pages, on-call and telemetry in OneUptime. This page covers its hosted endpoint (https://oneuptime.com/mcp).
Is the OneUptime MCP server safe to use?
OneUptime scores 68 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 OneUptime MCP server expose?
OneUptime exposes 193 tools: create_team, get_team, list_teams, update_team, delete_team, and 188 more. Their descriptions and schemas cost roughly 46,160 tokens of context every time the server is loaded.
Does the OneUptime MCP server require authentication?
No. We connected to OneUptime without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the OneUptime MCP server still maintained?
OneUptime is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.