# OneUptime (remote · oneuptime.com) Manage incidents, alerts, monitors, status pages, on-call and telemetry in OneUptime. - Trust score: 68/100 (medium) - Registry status: active - Liveness: live - Owner verified: no - Last scored: 2026-10-23 ## Components - remote · `oneuptime.com`: 68/100 (this document), [markdown](https://verifymcp.io/servers/com-oneuptime-mcp/oneuptime.md), [page](https://verifymcp.io/servers/com-oneuptime-mcp/oneuptime) ## Channel facts - Endpoint: `https://oneuptime.com/mcp` - Transports: `streamable-http` - Auth: `none` - Version: `14.0.85` ## Trust breakdown 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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog) Scored 2026-10-23. - **Endpoint Security**: 66/100 - The endpoint's TLS certificate is valid, in date, and uses a strong key. - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (create_team). - HTTPS is enforced; there's no plaintext access path. - The HSTS (Strict-Transport-Security) header is present. - DNSSEC is configured correctly; the domain's records validate against the full chain to the root. - **Transport & Reachability**: 100/100 - Verified streamable-http transport via a live MCP handshake. - **Schema Quality & AI Usability**: 63/100 - AI-judged instruction clarity (excellent). - 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. - Usage-examples check failed: none of the tools include examples. - **Stability & Change Management**: 13/100 - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses. - **Tool Coverage**: 100/100 - 100% of tools have a non-trivial description (not blank, and not just the tool's name). - 100% of tool parameters carry a description. - **Tool Safety**: 100/100 - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured. - All 27 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation. - An AI judge read all 193 captured unit(s) of tool text and found none that tries to manipulate the model reading it. - **Capabilities**: 100/100 - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28. ## Install ### 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. ### Claude ```bash claude mcp add --transport http com-oneuptime-mcp 'https://oneuptime.com/mcp' ``` ### Cursor ```json { "mcpServers": { "com-oneuptime-mcp": { "url": "https://oneuptime.com/mcp" } } } ``` ### VS Code ```json { "servers": { "com-oneuptime-mcp": { "type": "http", "url": "https://oneuptime.com/mcp" } } } ``` ### Codex ```toml [mcp_servers.com-oneuptime-mcp] url = "https://oneuptime.com/mcp" ``` ### opencode ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "com-oneuptime-mcp": { "type": "remote", "url": "https://oneuptime.com/mcp", "enabled": true } } } ``` ### OpenClaw ```bash openclaw mcp add com-oneuptime-mcp --url 'https://oneuptime.com/mcp' --transport streamable-http ``` ### Hermes ```yaml mcp_servers: com-oneuptime-mcp: url: "https://oneuptime.com/mcp" ``` ### Netclaw ```json { "McpServers": { "com-oneuptime-mcp": { "Transport": "http", "Url": "https://oneuptime.com/mcp" } } } ``` ### Vellum ```bash assistant mcp add com-oneuptime-mcp -t streamable-http -u 'https://oneuptime.com/mcp' ``` ### Other ```json { "mcpServers": { "com-oneuptime-mcp": { "type": "http", "url": "https://oneuptime.com/mcp" } } } ``` The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs. ## Changelog Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims. ### 2026-10-23 (score 68, +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. ### 2026-10-22 (score 67, 0) - [functional] Server version: 14.0.81 → 14.0.84 ### 2026-10-21 (score 67, +1) - [functional] Server version: 14.0.80 → 14.0.81 - [functional] Server version: 14.0.78 → 14.0.80 ### 2026-10-20 (score 66, 0) - [functional improvement] Stability: unverified → 0.03 - [functional] Server version: 14.0.77 → 14.0.78 - [functional] Server version: 14.0.75 → 14.0.77 ### 2026-10-19 (score 66) First indexed and scored. ## MCP tools (193) ### `create_team` (~115 tokens) Create Team Create a new Team in OneUptime. Returns the created Team object with its ID. Use this to add new Teams to your project. Note: projectId is inferred from your API key — you do not need to provide it. Input parameters: - `customFields` (object): Custom Fields on this resource. - `description` (string): Friendly description that will help you remember. - `name` (string, required): Any friendly name of this object. - `projectId` (string): ID of your OneUptime Project in which this object belongs. ### `get_team` (~122 tokens) Get Team Retrieve a single Team by its unique ID from OneUptime. Use list_teams first if you need to find the ID. Input parameters: - `id` (string, required): The unique identifier (UUID) of the Team to retrieve. Example: "550e8400-e29b-41d4-a716-446655440000" - `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. ### `list_teams` (~314 tokens) List Teams List and search Teams from OneUptime with optional filtering, pagination, and sorting. Returns an array of Team objects plus the total matching count. Input parameters: - `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": "", "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. ### `update_team` (~110 tokens) Update Team Update an existing Team in OneUptime. Only include the fields you want to change - unspecified fields will remain unchanged. Use get_team afterwards to see the updated record. Input parameters: - `customFields` (object): Custom Fields on this resource. - `description` (string): Friendly description that will help you remember. - `id` (string, required): The unique identifier (UUID) of the Team to update. Required. Use list_teams to find IDs. - `name` (string): Any friendly name of this object. ### `delete_team` (~55 tokens) Delete Team Permanently delete a Team from OneUptime. This action cannot be undone. Returns a confirmation message upon successful deletion. Input parameters: - `id` (string, required): The unique identifier (UUID) of the Team to delete. This action is irreversible. ### `count_teams` (~184 tokens) Count Teams Count the total number of Teams in OneUptime, optionally filtered by query criteria. Returns a single number. Useful for dashboards, reports, or checking if records exist before listing. Input parameters: - `query` (object): Optional filter criteria. If omitted, counts all Teams. Each field accepts a direct value (exact match) or an operator object {"_type": "", "value": ...}. Operators: EqualTo, NotEqual, IsNu… ### `create_label` (~121 tokens) Create Label Create a new Label in OneUptime. Returns the created Label object with its ID. Use this to add new Labels to your project. Note: projectId is inferred from your API key — you do not need to provide it. Input parameters: - `color` (object, required): Color of this resource in Hex (#32a852 for example). - `description` (string): Friendly description that will help you remember. - `name` (string, required): Any friendly name of this object. - `projectId` (string): ID of your OneUptime Project in which this object belongs. ### `get_label` (~107 tokens) Get Label Retrieve a single Label by its unique ID from OneUptime. Use list_labels first if you need to find the ID. Input parameters: - `id` (string, required): The unique identifier (UUID) of the Label to retrieve. Example: "550e8400-e29b-41d4-a716-446655440000" - `select` (array): Optional: field names to return for each Label (e.g. ["_id", "name"]). Omit to get all readable fields. ### `list_labels` (~299 tokens) List Labels List and search Labels from OneUptime with optional filtering, pagination, and sorting. Returns an array of Label objects plus the total matching count. Input parameters: - `limit` (number): Maximum number of records to return. Default: 10, Maximum: 100. - `query` (object): Filter criteria for Labels. Each field accepts a direct value (exact match) or an operator object {"_type": "", "value": ...}. Operators: EqualTo, NotEqual, IsNull, NotNull, EqualToOrNull,… - `select` (array): Optional: field names to return for each Label (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. ### `update_label` (~115 tokens) Update Label 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. Input parameters: - `color` (object): Color of this resource in Hex (#32a852 for example). - `description` (string): Friendly description that will help you remember. - `id` (string, required): The unique identifier (UUID) of the Label to update. Required. Use list_labels to find IDs. - `name` (string): Any friendly name of this object. ### `delete_label` (~55 tokens) Delete Label Permanently delete a Label from OneUptime. This action cannot be undone. Returns a confirmation message upon successful deletion. Input parameters: - `id` (string, required): The unique identifier (UUID) of the Label to delete. This action is irreversible. ### `count_labels` (~183 tokens) Count Labels Count the total number of Labels in OneUptime, optionally filtered by query criteria. Returns a single number. Useful for dashboards, reports, or checking if records exist before listing. Input parameters: - `query` (object): Optional filter criteria. If omitted, counts all Labels. Each field accepts a direct value (exact match) or an operator object {"_type": "", "value": ...}. Operators: EqualTo, NotEqual, IsN… ### `create_security_case` (~395 tokens) Create Security Case Create a new Security Case in OneUptime. Returns the created Security Case object with its ID. Use this to add new Security Cases to your project. Note: projectId is inferred from your API key — you do not need to provide it. Input parameters: - `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. - `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. - `projectId` (string): ID of the project this case belongs to. - `status` (string): New, Investigating, Contained or Closed. Every case starts New; closing it records a verdict. - `title` (string, required): 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. ### `get_security_case` (~135 tokens) Get Security Case Retrieve a single Security Case by its unique ID from OneUptime. Use list_security_cases first if you need to find the ID. Input parameters: - `id` (string, required): The unique identifier (UUID) of the Security Case to retrieve. Example: "550e8400-e29b-41d4-a716-446655440000" - `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… ### `list_security_cases` (~327 tokens) List Security Cases 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. Input parameters: - `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": "", "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. ### `update_security_case` (~394 tokens) Update Security Case 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. Input parameters: - `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, required): 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. ### `delete_security_case` (~58 tokens) Delete Security Case Permanently delete a Security Case from OneUptime. This action cannot be undone. Returns a confirmation message upon successful deletion. Input parameters: - `id` (string, required): The unique identifier (UUID) of the Security Case to delete. This action is irreversible. ### `count_security_cases` (~186 tokens) Count Security Cases Count the total number of Security Cases in OneUptime, optionally filtered by query criteria. Returns a single number. Useful for dashboards, reports, or checking if records exist before listing. Input parameters: - `query` (object): Optional filter criteria. If omitted, counts all Security Cases. Each field accepts a direct value (exact match) or an operator object {"_type": "", "value": ...}. Operators: EqualTo, NotEq… ### `create_security_case_note` (~108 tokens) Create Security Case Note Create a new Security Case Note in OneUptime. Returns the created Security Case Note object with its ID. Use this to add new Security Case Notes to your project. Note: projectId is inferred from your API key — you do not need to provide it. Input parameters: - `note` (string, required): The note, in Markdown. - `projectId` (string): ID of the project this note belongs to. - `securityCaseId` (string, required): ID of the case this note is on. ### `get_security_case_note` (~117 tokens) Get Security Case Note Retrieve a single Security Case Note by its unique ID from OneUptime. Use list_security_case_notes first if you need to find the ID. Input parameters: - `id` (string, required): The unique identifier (UUID) of the Security Case Note to retrieve. Example: "550e8400-e29b-41d4-a716-446655440000" - `select` (array): Optional: field names to return for each Security Case Note (e.g. ["_id", "name"]). Omit to get all readable fields. ### `list_security_case_notes` (~309 tokens) List Security Case Notes 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. Input parameters: - `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": "", "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. ### `update_security_case_note` (~91 tokens) Update Security Case Note 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. Input parameters: - `id` (string, required): 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. ### `delete_security_case_note` (~61 tokens) Delete Security Case Note Permanently delete a Security Case Note from OneUptime. This action cannot be undone. Returns a confirmation message upon successful deletion. Input parameters: - `id` (string, required): The unique identifier (UUID) of the Security Case Note to delete. This action is irreversible. ### `count_security_case_notes` (~189 tokens) Count Security Case Notes Count the total number of Security Case Notes in OneUptime, optionally filtered by query criteria. Returns a single number. Useful for dashboards, reports, or checking if records exist before listing. Input parameters: - `query` (object): Optional filter criteria. If omitted, counts all Security Case Notes. Each field accepts a direct value (exact match) or an operator object {"_type": "", "value": ...}. Operators: EqualTo,… ### `create_security_detection` (~61 tokens) Create Security Detection Create a new Security Detection in OneUptime. Returns the created Security Detection object with its ID. Use this to add new Security Detections to your project. Note: projectId is inferred from your API key — you do not need to provide it. ### `get_security_detection` (~140 tokens) Get Security Detection Retrieve a single Security Detection by its unique ID from OneUptime. Use list_security_detections first if you need to find the ID. Input parameters: - `id` (string, required): The unique identifier (UUID) of the Security Detection to retrieve. Example: "550e8400-e29b-41d4-a716-446655440000" - `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… ### `list_security_detections` (~336 tokens) List Security Detections 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. Input parameters: - `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": "", "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. ### `update_security_detection` (~76 tokens) Update Security Detection 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. Input parameters: - `id` (string, required): The unique identifier (UUID) of the Security Detection to update. Required. Use list_security_detections to find IDs. ### `delete_security_detection` (~58 tokens) Delete Security Detection Permanently delete a Security Detection from OneUptime. This action cannot be undone. Returns a confirmation message upon successful deletion. Input parameters: - `id` (string, required): The unique identifier (UUID) of the Security Detection to delete. This action is irreversible. ### `count_security_detections` (~192 tokens) Count Security Detections Count the total number of Security Detections in OneUptime, optionally filtered by query criteria. Returns a single number. Useful for dashboards, reports, or checking if records exist before listing. Input parameters: - `query` (object): Optional filter criteria. If omitted, counts all Security Detections. Each field accepts a direct value (exact match) or an operator object {"_type": "", "value": ...}. Operators: EqualTo,… ### `create_security_playbook` (~315 tokens) Create Security Playbook Create a new Security Playbook in OneUptime. Returns the created Security Playbook object with its ID. Use this to add new Security Playbooks to your project. Note: projectId is inferred from your API key — you do not need to provide it. Input parameters: - `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. - `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, required): What the playbook does, in a few words. - `projectId` (string): ID of the project this playbook belongs to. - `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). ### `get_security_playbook` (~134 tokens) Get Security Playbook Retrieve a single Security Playbook by its unique ID from OneUptime. Use list_security_playbooks first if you need to find the ID. Input parameters: - `id` (string, required): The unique identifier (UUID) of the Security Playbook to retrieve. Example: "550e8400-e29b-41d4-a716-446655440000" - `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,… ### `list_security_playbooks` (~326 tokens) List Security Playbooks 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. Input parameters: - `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": "", "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. ### `update_security_playbook` (~314 tokens) Update Security Playbook 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. Input parameters: - `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, required): 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). ### `delete_security_playbook` (~61 tokens) Delete Security Playbook Permanently delete a Security Playbook from OneUptime. This action cannot be undone. Returns a confirmation message upon successful deletion. Input parameters: - `id` (string, required): The unique identifier (UUID) of the Security Playbook to delete. This action is irreversible. ### `count_security_playbooks` (~189 tokens) Count Security Playbooks Count the total number of Security Playbooks in OneUptime, optionally filtered by query criteria. Returns a single number. Useful for dashboards, reports, or checking if records exist before listing. Input parameters: - `query` (object): Optional filter criteria. If omitted, counts all Security Playbooks. Each field accepts a direct value (exact match) or an operator object {"_type": "", "value": ...}. Operators: EqualTo, N… ### `create_status_page` (~2054 tokens) Create Status Page Create a new Status Page in OneUptime. Returns the created Status Page object with its ID. Use this to add new Status Pages to your project. Note: projectId is inferred from your API key — you do not need to provide it. Input parameters: - `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? - `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, required): 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… - `projectId` (string): ID of your OneUptime Project in which this object belongs. - `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. ### `get_status_page` (~157 tokens) Get Status Page Retrieve a single Status Page by its unique ID from OneUptime. Use list_status_pages first if you need to find the ID. Input parameters: - `id` (string, required): The unique identifier (UUID) of the Status Page to retrieve. Example: "550e8400-e29b-41d4-a716-446655440000" - `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,… ### `list_status_pages` (~349 tokens) List Status Pages 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. Input parameters: - `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": "", "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. ### `update_status_page` (~2049 tokens) Update Status Page 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. Input parameters: - `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, required): 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. ### `delete_status_page` (~58 tokens) Delete Status Page Permanently delete a Status Page from OneUptime. This action cannot be undone. Returns a confirmation message upon successful deletion. Input parameters: - `id` (string, required): The unique identifier (UUID) of the Status Page to delete. This action is irreversible. ### `count_status_pages` (~186 tokens) Count Status Pages Count the total number of Status Pages in OneUptime, optionally filtered by query criteria. Returns a single number. Useful for dashboards, reports, or checking if records exist before listing. Input parameters: - `query` (object): Optional filter criteria. If omitted, counts all Status Pages. Each field accepts a direct value (exact match) or an operator object {"_type": "", "value": ...}. Operators: EqualTo, NotEqua… ### `create_on_call_policy` (~238 tokens) Create On-Call Policy Create a new On-Call Policy in OneUptime. Returns the created On-Call Policy object with its ID. Use this to add new On-Call Duty Policies to your project. Note: projectId is inferred from your API key — you do not need to provide it. Input parameters: - `customFields` (object): Custom Fields on this resource. - `description` (string): Friendly description that will help you remember. - `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, required): Any friendly name of this object. - `projectId` (string): ID of your OneUptime Project in which this object belongs. - `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. ### `get_on_call_policy` (~137 tokens) Get On-Call Policy Retrieve a single On-Call Policy by its unique ID from OneUptime. Use list_on_call_duty_policies first if you need to find the ID. Input parameters: - `id` (string, required): The unique identifier (UUID) of the On-Call Policy to retrieve. Example: "550e8400-e29b-41d4-a716-446655440000" - `select` (array): Optional: field names to return for each On-Call Policy (e.g. ["_id", "name"]). Omit to get all readable fields. Large fields excluded by default (request explicitly if needed): customFields. ### `list_on_call_duty_policies` (~332 tokens) List On-Call Duty Policies List and search On-Call Duty Policies from OneUptime with optional filtering, pagination, and sorting. Returns an array of On-Call Policy objects plus the total matching count. Input parameters: - `limit` (number): Maximum number of records to return. Default: 10, Maximum: 100. - `query` (object): Filter criteria for On-Call Duty Policies. Each field accepts a direct value (exact match) or an operator object {"_type": "", "value": ...}. Operators: EqualTo, NotEqual, IsNull, NotNull,… - `select` (array): Optional: field names to return for each On-Call Policy (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. ### `update_on_call_policy` (~235 tokens) Update On-Call Policy 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. Input parameters: - `customFields` (object): Custom Fields on this resource. - `description` (string): Friendly description that will help you remember. - `id` (string, required): 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. ### `delete_on_call_policy` (~63 tokens) Delete On-Call Policy Permanently delete a On-Call Policy from OneUptime. This action cannot be undone. Returns a confirmation message upon successful deletion. Input parameters: - `id` (string, required): The unique identifier (UUID) of the On-Call Policy to delete. This action is irreversible. ### `count_on_call_duty_policies` (~196 tokens) Count On-Call Duty Policies Count the total number of On-Call Duty Policies in OneUptime, optionally filtered by query criteria. Returns a single number. Useful for dashboards, reports, or checking if records exist before listing. Input parameters: - `query` (object): Optional filter criteria. If omitted, counts all On-Call Duty Policies. Each field accepts a direct value (exact match) or an operator object {"_type": "", "value": ...}. Operators: EqualTo… ### `create_monitor` (~1029 tokens) Create Monitor Create a new Monitor in OneUptime. Returns the created Monitor object with its ID. Use this to add new Monitors to your project. Note: projectId is inferred from your API key — you do not need to provide it. Input parameters: - `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. - `incomingMonitorRequest` (object): Incoming Monitor Request for Incoming Request Monitor. - `incomingRequestMonitorHeartbeatCheckedAt` (object): This field is for Incoming Request monitor only. When was the last time we checked the heartbeat? - `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. - `monitorType` (string, required): What is the type of this monitor? Website? API? etc. - `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, required): 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. - `projectId` (string): ID of your OneUptime Project in which this object belongs. - `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. - `serverMonitorRequestReceivedAt` (object): This field is for Server Monitor only. When was the last time we received a request? - `serverMonitorResponse` (object): Server Monitor Response for Server Monitor. - `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. - `telemetryMonitorLastMonitorAt` (object): This field is for Telemetry Monitor only. When was the last time we monitored? - `telemetryMonitorNextMonitorAt` (object): This field is for Telemetry Monitor only. When is the next time we should monitor? - `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. ### `get_monitor` (~137 tokens) Get Monitor Retrieve a single Monitor by its unique ID from OneUptime. Use list_monitors first if you need to find the ID. Input parameters: - `id` (string, required): The unique identifier (UUID) of the Monitor to retrieve. Example: "550e8400-e29b-41d4-a716-446655440000" - `select` (array): Optional: field names to return for each Monitor (e.g. ["_id", "name"]). Omit to get all readable fields. Large fields excluded by default (request explicitly if needed): description, customFields, i… ### `list_monitors` (~331 tokens) List Monitors List and search Monitors from OneUptime with optional filtering, pagination, and sorting. Returns an array of Monitor objects plus the total matching count. Input parameters: - `limit` (number): Maximum number of records to return. Default: 10, Maximum: 100. - `query` (object): Filter criteria for Monitors. Each field accepts a direct value (exact match) or an operator object {"_type": "", "value": ...}. Operators: EqualTo, NotEqual, IsNull, NotNull, EqualToOrNull… - `select` (array): Optional: field names to return for each Monitor (e.g. ["_id", "name"]). Omit to get all readable fields. Large fields excluded by default (request explicitly if needed): description, customFields, i… - `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. ### `update_monitor` (~934 tokens) Update Monitor 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. Input parameters: - `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, required): 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. ### `delete_monitor` (~55 tokens) Delete Monitor Permanently delete a Monitor from OneUptime. This action cannot be undone. Returns a confirmation message upon successful deletion. Input parameters: - `id` (string, required): The unique identifier (UUID) of the Monitor to delete. This action is irreversible. ### `count_monitors` (~186 tokens) Count Monitors Count the total number of Monitors in OneUptime, optionally filtered by query criteria. Returns a single number. Useful for dashboards, reports, or checking if records exist before listing. Input parameters: - `query` (object): Optional filter criteria. If omitted, counts all Monitors. Each field accepts a direct value (exact match) or an operator object {"_type": "", "value": ...}. Operators: EqualTo, NotEqual, I… ### `create_monitor_status` (~256 tokens) Create Monitor Status Create a new Monitor Status in OneUptime. Returns the created Monitor Status object with its ID. Use this to add new Monitor Statuses to your project. Note: projectId is inferred from your API key — you do not need to provide it. Input parameters: - `color` (object, required): Color of this resource in Hex (#32a852 for example). - `description` (string): Friendly description that will help you remember. - `isOfflineState` (boolean): Is this monitor in offline state? - `isOperationalState` (boolean): Is this monitor in operational state? - `name` (string, required): 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… - `projectId` (string): ID of your OneUptime Project in which this object belongs. ### `get_monitor_status` (~113 tokens) Get Monitor Status Retrieve a single Monitor Status by its unique ID from OneUptime. Use list_monitor_statuses first if you need to find the ID. Input parameters: - `id` (string, required): The unique identifier (UUID) of the Monitor Status to retrieve. Example: "550e8400-e29b-41d4-a716-446655440000" - `select` (array): Optional: field names to return for each Monitor Status (e.g. ["_id", "name"]). Omit to get all readable fields. ### `list_monitor_statuses` (~307 tokens) List Monitor Statuses List and search Monitor Statuses from OneUptime with optional filtering, pagination, and sorting. Returns an array of Monitor Status objects plus the total matching count. Input parameters: - `limit` (number): Maximum number of records to return. Default: 10, Maximum: 100. - `query` (object): Filter criteria for Monitor Statuses. Each field accepts a direct value (exact match) or an operator object {"_type": "", "value": ...}. Operators: EqualTo, NotEqual, IsNull, NotNull, Equal… - `select` (array): Optional: field names to return for each Monitor Status (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. ### `update_monitor_status` (~251 tokens) Update Monitor Status 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. Input parameters: - `color` (object): Color of this resource in Hex (#32a852 for example). - `description` (string): Friendly description that will help you remember. - `id` (string, required): 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… ### `delete_monitor_status` (~58 tokens) Delete Monitor Status Permanently delete a Monitor Status from OneUptime. This action cannot be undone. Returns a confirmation message upon successful deletion. Input parameters: - `id` (string, required): The unique identifier (UUID) of the Monitor Status to delete. This action is irreversible. ### `count_monitor_statuses` (~189 tokens) Count Monitor Statuses Count the total number of Monitor Statuses in OneUptime, optionally filtered by query criteria. Returns a single number. Useful for dashboards, reports, or checking if records exist before listing. Input parameters: - `query` (object): Optional filter criteria. If omitted, counts all Monitor Statuses. Each field accepts a direct value (exact match) or an operator object {"_type": "", "value": ...}. Operators: EqualTo, Not… ### `create_incident_state` (~292 tokens) Create Incident State Create a new Incident State in OneUptime. Returns the created Incident State object with its ID. Use this to add new Incident States to your project. Note: projectId is inferred from your API key — you do not need to provide it. Input parameters: - `color` (object, required): Color of this resource in Hex (#32a852 for example). - `description` (string): Friendly description that will help you remember. - `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, required): 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… - `projectId` (string): ID of your OneUptime Project in which this object belongs. ### `get_incident_state` (~114 tokens) Get Incident State Retrieve a single Incident State by its unique ID from OneUptime. Use list_incident_states first if you need to find the ID. Input parameters: - `id` (string, required): The unique identifier (UUID) of the Incident State to retrieve. Example: "550e8400-e29b-41d4-a716-446655440000" - `select` (array): Optional: field names to return for each Incident State (e.g. ["_id", "name"]). Omit to get all readable fields. ### `list_incident_states` (~305 tokens) List Incident States List and search Incident States from OneUptime with optional filtering, pagination, and sorting. Returns an array of Incident State objects plus the total matching count. Input parameters: - `limit` (number): Maximum number of records to return. Default: 10, Maximum: 100. - `query` (object): Filter criteria for Incident States. Each field accepts a direct value (exact match) or an operator object {"_type": "", "value": ...}. Operators: EqualTo, NotEqual, IsNull, NotNull, EqualT… - `select` (array): Optional: field names to return for each Incident 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. ### `update_incident_state` (~289 tokens) Update Incident State 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. Input parameters: - `color` (object): Color of this resource in Hex (#32a852 for example). - `description` (string): Friendly description that will help you remember. - `id` (string, required): 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… ### `delete_incident_state` (~59 tokens) Delete Incident State Permanently delete a Incident State from OneUptime. This action cannot be undone. Returns a confirmation message upon successful deletion. Input parameters: - `id` (string, required): The unique identifier (UUID) of the Incident State to delete. This action is irreversible. ### `count_incident_states` (~187 tokens) Count Incident States Count the total number of Incident States in OneUptime, optionally filtered by query criteria. Returns a single number. Useful for dashboards, reports, or checking if records exist before listing. Input parameters: - `query` (object): Optional filter criteria. If omitted, counts all Incident States. Each field accepts a direct value (exact match) or an operator object {"_type": "", "value": ...}. Operators: EqualTo, NotE… ### `create_incident` (~1078 tokens) Create Incident Create a new Incident in OneUptime. Returns the created Incident object with its ID. Use this to add new Incidents to your project. Note: projectId is inferred from your API key — you do not need to provide it. Input parameters: - `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. - `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, required): 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. - `projectId` (string): ID of your OneUptime Project in which this object belongs. - `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. - `shouldStatusPageSubscribersBeNotifiedOnIncidentCreated` (boolean): Should subscribers be notified about 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, required): Title of this incident. - `vmwareVCenters` (array): List of vCenters affected by this incident. ### `get_incident` (~158 tokens) Get Incident Retrieve a single Incident by its unique ID from OneUptime. Use list_incidents first if you need to find the ID. Input parameters: - `id` (string, required): The unique identifier (UUID) of the Incident to retrieve. Example: "550e8400-e29b-41d4-a716-446655440000" - `select` (array): Optional: field names to return for each Incident (e.g. ["_id", "name"]). Omit to get all readable fields. Large fields excluded by default (request explicitly if needed): subscriberNotificationStatu… ### `list_incidents` (~351 tokens) List Incidents List and search Incidents from OneUptime with optional filtering, pagination, and sorting. Returns an array of Incident objects plus the total matching count. Input parameters: - `limit` (number): Maximum number of records to return. Default: 10, Maximum: 100. - `query` (object): Filter criteria for Incidents. Each field accepts a direct value (exact match) or an operator object {"_type": "", "value": ...}. Operators: EqualTo, NotEqual, IsNull, NotNull, EqualToOrNul… - `select` (array): Optional: field names to return for each Incident (e.g. ["_id", "name"]). Omit to get all readable fields. Large fields excluded by default (request explicitly if needed): subscriberNotificationStatu… - `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. ### `update_incident` (~1050 tokens) Update Incident 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. Input parameters: - `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, required): 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. ### `delete_incident` (~56 tokens) Delete Incident Permanently delete a Incident from OneUptime. This action cannot be undone. Returns a confirmation message upon successful deletion. Input parameters: - `id` (string, required): The unique identifier (UUID) of the Incident to delete. This action is irreversible. ### `count_incidents` (~186 tokens) Count Incidents Count the total number of Incidents in OneUptime, optionally filtered by query criteria. Returns a single number. Useful for dashboards, reports, or checking if records exist before listing. Input parameters: - `query` (object): Optional filter criteria. If omitted, counts all Incidents. Each field accepts a direct value (exact match) or an operator object {"_type": "", "value": ...}. Operators: EqualTo, NotEqual,… ### `create_incident_state_timeline` (~213 tokens) Create Incident State Timeline Create a new Incident State Timeline in OneUptime. Returns the created Incident State Timeline object with its ID. Use this to add new Incident State Timelines to your project. Note: projectId is inferred from your API key — you do not need to provide it. Input parameters: - `endsAt` (object): When did this status change end? - `incidentId` (string, required): Relation to Incident ID in which this resource belongs. - `incidentStateId` (string, required): Incident State ID Relation. Which incident state does this incident change to? - `projectId` (string): ID of your OneUptime Project in which this object belongs. - `rootCause` (string): What is the root cause of this status change? - `shouldStatusPageSubscribersBeNotified` (boolean): Should subscribers be notified about this state change? - `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. ### `get_incident_state_timeline` (~141 tokens) Get Incident State Timeline Retrieve a single Incident State Timeline by its unique ID from OneUptime. Use list_incident_state_timelines first if you need to find the ID. Input parameters: - `id` (string, required): The unique identifier (UUID) of the Incident State Timeline to retrieve. Example: "550e8400-e29b-41d4-a716-446655440000" - `select` (array): Optional: field names to return for each Incident State Timeline (e.g. ["_id", "name"]). Omit to get all readable fields. Large fields excluded by default (request explicitly if needed): subscriberNo… ### `list_incident_state_timelines` (~333 tokens) List Incident State Timelines List and search Incident State Timelines from OneUptime with optional filtering, pagination, and sorting. Returns an array of Incident State Timeline objects plus the total matching count. Input parameters: - `limit` (number): Maximum number of records to return. Default: 10, Maximum: 100. - `query` (object): Filter criteria for Incident State Timelines. Each field accepts a direct value (exact match) or an operator object {"_type": "", "value": ...}. Operators: EqualTo, NotEqual, IsNull, NotNul… - `select` (array): Optional: field names to return for each Incident State Timeline (e.g. ["_id", "name"]). Omit to get all readable fields. Large fields excluded by default (request explicitly if needed): subscriberNo… - `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. ### `update_incident_state_timeline` (~143 tokens) Update Incident State Timeline 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. Input parameters: - `id` (string, required): 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. ### `delete_incident_state_timeline` (~63 tokens) Delete Incident State Timeline Permanently delete a Incident State Timeline from OneUptime. This action cannot be undone. Returns a confirmation message upon successful deletion. Input parameters: - `id` (string, required): The unique identifier (UUID) of the Incident State Timeline to delete. This action is irreversible. ### `count_incident_state_timelines` (~193 tokens) Count Incident State Timelines Count the total number of Incident State Timelines in OneUptime, optionally filtered by query criteria. Returns a single number. Useful for dashboards, reports, or checking if records exist before listing. Input parameters: - `query` (object): Optional filter criteria. If omitted, counts all Incident State Timelines. Each field accepts a direct value (exact match) or an operator object {"_type": "", "value": ...}. Operators: Equa… ### `create_incident_internal_note` (~208 tokens) Create Incident Internal Note Create a new Incident Internal Note in OneUptime. Returns the created Incident Internal Note object with its ID. Use this to add new Incident Internal Notes to your project. Note: projectId is inferred from your API key — you do not need to provide it. Input parameters: - `attachments` (array): Files attached to this note. - `incidentId` (string, required): Relation to Incident ID in which this resource belongs. - `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. - `postedFromSlackMessageId` (string): Unique identifier for the Slack message this note was created from (channel_id:message_ts). Used to prevent duplicate notes when multiple users react to the same message. - `projectId` (string): ID of your OneUptime Project in which this object belongs. ### `get_incident_internal_note` (~135 tokens) Get Incident Internal Note Retrieve a single Incident Internal Note by its unique ID from OneUptime. Use list_incident_internal_notes first if you need to find the ID. Input parameters: - `id` (string, required): The unique identifier (UUID) of the Incident Internal Note to retrieve. Example: "550e8400-e29b-41d4-a716-446655440000" - `select` (array): Optional: field names to return for each Incident Internal Note (e.g. ["_id", "name"]). Omit to get all readable fields. Large fields excluded by default (request explicitly if needed): savedFromChat… ### `list_incident_internal_notes` (~326 tokens) List Incident Internal Notes List and search Incident Internal Notes from OneUptime with optional filtering, pagination, and sorting. Returns an array of Incident Internal Note objects plus the total matching count. Input parameters: - `limit` (number): Maximum number of records to return. Default: 10, Maximum: 100. - `query` (object): Filter criteria for Incident Internal Notes. Each field accepts a direct value (exact match) or an operator object {"_type": "", "value": ...}. Operators: EqualTo, NotEqual, IsNull, NotNull… - `select` (array): Optional: field names to return for each Incident Internal Note (e.g. ["_id", "name"]). Omit to get all readable fields. Large fields excluded by default (request explicitly if needed): savedFromChat… - `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. ### `update_incident_internal_note` (~147 tokens) Update Incident Internal Note 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. Input parameters: - `attachments` (array): Files attached to this note. - `id` (string, required): 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. ### `delete_incident_internal_note` (~62 tokens) Delete Incident Internal Note Permanently delete a Incident Internal Note from OneUptime. This action cannot be undone. Returns a confirmation message upon successful deletion. Input parameters: - `id` (string, required): The unique identifier (UUID) of the Incident Internal Note to delete. This action is irreversible. ### `count_incident_internal_notes` (~190 tokens) Count Incident Internal Notes Count the total number of Incident Internal Notes in OneUptime, optionally filtered by query criteria. Returns a single number. Useful for dashboards, reports, or checking if records exist before listing. Input parameters: - `query` (object): Optional filter criteria. If omitted, counts all Incident Internal Notes. Each field accepts a direct value (exact match) or an operator object {"_type": "", "value": ...}. Operators: Equal… ### `create_incident_public_note` (~233 tokens) Create Incident Public Note Create a new Incident Public Note in OneUptime. Returns the created Incident Public Note object with its ID. Use this to add new Incident Public Notes to your project. Note: projectId is inferred from your API key — you do not need to provide it. Input parameters: - `attachments` (array): Files attached to this note. - `incidentId` (string, required): Relation to Incident ID in which this resource belongs. - `note` (string): Notes in markdown. - `postedAt` (object): Date and time when the note was posted. - `postedFromSlackMessageId` (string): Unique identifier for the Slack message this note was created from (channel_id:message_ts). Used to prevent duplicate notes when multiple users react to the same message. - `projectId` (string): ID of your OneUptime Project in which this object belongs. - `shouldStatusPageSubscribersBeNotifiedOnNoteCreated` (boolean): Should subscribers be notified about this note? If left out, this follows the incident: true when subscribers were notified that the incident was declared, false when it was declared without notifyin… ### `get_incident_public_note` (~148 tokens) Get Incident Public Note Retrieve a single Incident Public Note by its unique ID from OneUptime. Use list_incident_public_notes first if you need to find the ID. Input parameters: - `id` (string, required): The unique identifier (UUID) of the Incident Public Note to retrieve. Example: "550e8400-e29b-41d4-a716-446655440000" - `select` (array): Optional: field names to return for each Incident Public Note (e.g. ["_id", "name"]). Omit to get all readable fields. Large fields excluded by default (request explicitly if needed): subscriberNotif… ### `list_incident_public_notes` (~339 tokens) List Incident Public Notes List and search Incident Public Notes from OneUptime with optional filtering, pagination, and sorting. Returns an array of Incident Public Note objects plus the total matching count. Input parameters: - `limit` (number): Maximum number of records to return. Default: 10, Maximum: 100. - `query` (object): Filter criteria for Incident Public Notes. Each field accepts a direct value (exact match) or an operator object {"_type": "", "value": ...}. Operators: EqualTo, NotEqual, IsNull, NotNull,… - `select` (array): Optional: field names to return for each Incident Public Note (e.g. ["_id", "name"]). Omit to get all readable fields. Large fields excluded by default (request explicitly if needed): subscriberNotif… - `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. ### `update_incident_public_note` (~120 tokens) Update Incident Public Note 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. Input parameters: - `attachments` (array): Files attached to this note. - `id` (string, required): 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. ### `delete_incident_public_note` (~62 tokens) Delete Incident Public Note Permanently delete a Incident Public Note from OneUptime. This action cannot be undone. Returns a confirmation message upon successful deletion. Input parameters: - `id` (string, required): The unique identifier (UUID) of the Incident Public Note to delete. This action is irreversible. ### `count_incident_public_notes` (~190 tokens) Count Incident Public Notes Count the total number of Incident Public Notes in OneUptime, optionally filtered by query criteria. Returns a single number. Useful for dashboards, reports, or checking if records exist before listing. Input parameters: - `query` (object): Optional filter criteria. If omitted, counts all Incident Public Notes. Each field accepts a direct value (exact match) or an operator object {"_type": "", "value": ...}. Operators: EqualTo… ### `create_incident_severity` (~196 tokens) Create Incident Severity Create a new Incident Severity in OneUptime. Returns the created Incident Severity object with its ID. Use this to add new Incident Severities to your project. Note: projectId is inferred from your API key — you do not need to provide it. Input parameters: - `color` (object, required): Color of this resource in Hex (#32a852 for example). - `description` (string): Friendly description that will help you remember. - `name` (string, required): 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… - `projectId` (string): ID of your OneUptime Project in which this object belongs. ### `get_incident_severity` (~117 tokens) Get Incident Severity Retrieve a single Incident Severity by its unique ID from OneUptime. Use list_incident_severities first if you need to find the ID. Input parameters: - `id` (string, required): The unique identifier (UUID) of the Incident Severity to retrieve. Example: "550e8400-e29b-41d4-a716-446655440000" - `select` (array): Optional: field names to return for each Incident Severity (e.g. ["_id", "name"]). Omit to get all readable fields. ### `list_incident_severities` (~309 tokens) List Incident Severities List and search Incident Severities from OneUptime with optional filtering, pagination, and sorting. Returns an array of Incident Severity objects plus the total matching count. Input parameters: - `limit` (number): Maximum number of records to return. Default: 10, Maximum: 100. - `query` (object): Filter criteria for Incident Severities. Each field accepts a direct value (exact match) or an operator object {"_type": "", "value": ...}. Operators: EqualTo, NotEqual, IsNull, NotNull, Eq… - `select` (array): Optional: field names to return for each Incident Severity (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. ### `update_incident_severity` (~195 tokens) Update Incident Severity 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. Input parameters: - `color` (object): Color of this resource in Hex (#32a852 for example). - `description` (string): Friendly description that will help you remember. - `id` (string, required): 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… ### `delete_incident_severity` (~60 tokens) Delete Incident Severity Permanently delete a Incident Severity from OneUptime. This action cannot be undone. Returns a confirmation message upon successful deletion. Input parameters: - `id` (string, required): The unique identifier (UUID) of the Incident Severity to delete. This action is irreversible. ### `count_incident_severities` (~191 tokens) Count Incident Severities Count the total number of Incident Severities in OneUptime, optionally filtered by query criteria. Returns a single number. Useful for dashboards, reports, or checking if records exist before listing. Input parameters: - `query` (object): Optional filter criteria. If omitted, counts all Incident Severities. Each field accepts a direct value (exact match) or an operator object {"_type": "", "value": ...}. Operators: EqualTo,… ### `create_alert_state` (~290 tokens) Create Alert State Create a new Alert State in OneUptime. Returns the created Alert State object with its ID. Use this to add new Alert States to your project. Note: projectId is inferred from your API key — you do not need to provide it. Input parameters: - `color` (object, required): Color of this resource in Hex (#32a852 for example). - `description` (string): Friendly description that will help you remember. - `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, required): 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… - `projectId` (string): ID of your OneUptime Project in which this object belongs. ### `get_alert_state` (~112 tokens) Get Alert State Retrieve a single Alert State by its unique ID from OneUptime. Use list_alert_states first if you need to find the ID. Input parameters: - `id` (string, required): The unique identifier (UUID) of the Alert State to retrieve. Example: "550e8400-e29b-41d4-a716-446655440000" - `select` (array): Optional: field names to return for each Alert State (e.g. ["_id", "name"]). Omit to get all readable fields. ### `list_alert_states` (~304 tokens) List Alert States List and search Alert States from OneUptime with optional filtering, pagination, and sorting. Returns an array of Alert State objects plus the total matching count. Input parameters: - `limit` (number): Maximum number of records to return. Default: 10, Maximum: 100. - `query` (object): Filter criteria for Alert States. Each field accepts a direct value (exact match) or an operator object {"_type": "", "value": ...}. Operators: EqualTo, NotEqual, IsNull, NotNull, EqualToOr… - `select` (array): Optional: field names to return for each Alert 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. ### `update_alert_state` (~285 tokens) Update Alert State 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. Input parameters: - `color` (object): Color of this resource in Hex (#32a852 for example). - `description` (string): Friendly description that will help you remember. - `id` (string, required): 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… ### `delete_alert_state` (~58 tokens) Delete Alert State Permanently delete a Alert State from OneUptime. This action cannot be undone. Returns a confirmation message upon successful deletion. Input parameters: - `id` (string, required): The unique identifier (UUID) of the Alert State to delete. This action is irreversible. ### `count_alert_states` (~186 tokens) Count Alert States Count the total number of Alert States in OneUptime, optionally filtered by query criteria. Returns a single number. Useful for dashboards, reports, or checking if records exist before listing. Input parameters: - `query` (object): Optional filter criteria. If omitted, counts all Alert States. Each field accepts a direct value (exact match) or an operator object {"_type": "", "value": ...}. Operators: EqualTo, NotEqua… ### `create_alert` (~714 tokens) Create Alert Create a new Alert in OneUptime. Returns the created Alert object with its ID. Use this to add new Alerts to your project. Note: projectId is inferred from your API key — you do not need to provide it. Input parameters: - `alertSeverityId` (string, required): 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. - `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. - `projectId` (string): ID of your OneUptime Project in which this object belongs. - `proxmoxClusters` (array): List of Proxmox clusters affected by this alert. - `remediationNotes` (string): Notes on how to remediate this alert. This is in markdown. - `rootCause` (string): What is the root cause of this alert? - `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, required): Title of this alert. - `vmwareVCenters` (array): List of vCenters affected by this alert. ### `get_alert` (~135 tokens) Get Alert Retrieve a single Alert by its unique ID from OneUptime. Use list_alerts first if you need to find the ID. Input parameters: - `id` (string, required): The unique identifier (UUID) of the Alert to retrieve. Example: "550e8400-e29b-41d4-a716-446655440000" - `select` (array): Optional: field names to return for each Alert (e.g. ["_id", "name"]). Omit to get all readable fields. Large fields excluded by default (request explicitly if needed): customFields, createdStateLog,… ### `list_alerts` (~327 tokens) List Alerts List and search Alerts from OneUptime with optional filtering, pagination, and sorting. Returns an array of Alert objects plus the total matching count. Input parameters: - `limit` (number): Maximum number of records to return. Default: 10, Maximum: 100. - `query` (object): Filter criteria for Alerts. Each field accepts a direct value (exact match) or an operator object {"_type": "", "value": ...}. Operators: EqualTo, NotEqual, IsNull, NotNull, EqualToOrNull,… - `select` (array): Optional: field names to return for each Alert (e.g. ["_id", "name"]). Omit to get all readable fields. Large fields excluded by default (request explicitly if needed): customFields, createdStateLog,… - `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. ### `update_alert` (~693 tokens) Update Alert 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. Input parameters: - `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, required): 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. ### `delete_alert` (~55 tokens) Delete Alert Permanently delete a Alert from OneUptime. This action cannot be undone. Returns a confirmation message upon successful deletion. Input parameters: - `id` (string, required): The unique identifier (UUID) of the Alert to delete. This action is irreversible. ### `count_alerts` (~184 tokens) Count Alerts Count the total number of Alerts in OneUptime, optionally filtered by query criteria. Returns a single number. Useful for dashboards, reports, or checking if records exist before listing. Input parameters: - `query` (object): Optional filter criteria. If omitted, counts all Alerts. Each field accepts a direct value (exact match) or an operator object {"_type": "", "value": ...}. Operators: EqualTo, NotEqual, IsN… ### `create_alert_state_timeline` (~191 tokens) Create Alert State Timeline Create a new Alert State Timeline in OneUptime. Returns the created Alert State Timeline object with its ID. Use this to add new Alert State Timelines to your project. Note: projectId is inferred from your API key — you do not need to provide it. Input parameters: - `alertId` (string, required): Relation to Alert ID in which this resource belongs. - `alertStateId` (string, required): Alert State ID Relation. Which alert state does this alert change to? - `endsAt` (object): When did this status change end? - `projectId` (string): ID of your OneUptime Project in which this object belongs. - `rootCause` (string): What is the root cause of this status change? - `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. ### `get_alert_state_timeline` (~134 tokens) Get Alert State Timeline Retrieve a single Alert State Timeline by its unique ID from OneUptime. Use list_alert_state_timelines first if you need to find the ID. Input parameters: - `id` (string, required): The unique identifier (UUID) of the Alert State Timeline to retrieve. Example: "550e8400-e29b-41d4-a716-446655440000" - `select` (array): Optional: field names to return for each Alert State Timeline (e.g. ["_id", "name"]). Omit to get all readable fields. Large fields excluded by default (request explicitly if needed): stateChangeLog. ### `list_alert_state_timelines` (~327 tokens) List Alert State Timelines List and search Alert State Timelines from OneUptime with optional filtering, pagination, and sorting. Returns an array of Alert State Timeline objects plus the total matching count. Input parameters: - `limit` (number): Maximum number of records to return. Default: 10, Maximum: 100. - `query` (object): Filter criteria for Alert State Timelines. Each field accepts a direct value (exact match) or an operator object {"_type": "", "value": ...}. Operators: EqualTo, NotEqual, IsNull, NotNull,… - `select` (array): Optional: field names to return for each Alert State Timeline (e.g. ["_id", "name"]). Omit to get all readable fields. Large fields excluded by default (request explicitly if needed): stateChangeLog. - `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. ### `update_alert_state_timeline` (~140 tokens) Update Alert State Timeline 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. Input parameters: - `alertStateId` (string): Alert State ID Relation. Which alert state does this alert change to? - `id` (string, required): 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. ### `delete_alert_state_timeline` (~62 tokens) Delete Alert State Timeline Permanently delete a Alert State Timeline from OneUptime. This action cannot be undone. Returns a confirmation message upon successful deletion. Input parameters: - `id` (string, required): The unique identifier (UUID) of the Alert State Timeline to delete. This action is irreversible. ### `count_alert_state_timelines` (~192 tokens) Count Alert State Timelines Count the total number of Alert State Timelines in OneUptime, optionally filtered by query criteria. Returns a single number. Useful for dashboards, reports, or checking if records exist before listing. Input parameters: - `query` (object): Optional filter criteria. If omitted, counts all Alert State Timelines. Each field accepts a direct value (exact match) or an operator object {"_type": "", "value": ...}. Operators: EqualTo… ### `create_alert_internal_note` (~207 tokens) Create Alert Internal Note Create a new Alert Internal Note in OneUptime. Returns the created Alert Internal Note object with its ID. Use this to add new Alert Internal Notes to your project. Note: projectId is inferred from your API key — you do not need to provide it. Input parameters: - `alertId` (string, required): Relation to Alert ID in which this resource belongs. - `attachments` (array): Files attached to this note. - `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. - `postedFromSlackMessageId` (string): Unique identifier for the Slack message this note was created from (channel_id:message_ts). Used to prevent duplicate notes when multiple users react to the same message. - `projectId` (string): ID of your OneUptime Project in which this object belongs. ### `get_alert_internal_note` (~133 tokens) Get Alert Internal Note Retrieve a single Alert Internal Note by its unique ID from OneUptime. Use list_alert_internal_notes first if you need to find the ID. Input parameters: - `id` (string, required): The unique identifier (UUID) of the Alert Internal Note to retrieve. Example: "550e8400-e29b-41d4-a716-446655440000" - `select` (array): Optional: field names to return for each Alert Internal Note (e.g. ["_id", "name"]). Omit to get all readable fields. Large fields excluded by default (request explicitly if needed): savedFromChatMes… ### `list_alert_internal_notes` (~325 tokens) List Alert Internal Notes List and search Alert Internal Notes from OneUptime with optional filtering, pagination, and sorting. Returns an array of Alert Internal Note objects plus the total matching count. Input parameters: - `limit` (number): Maximum number of records to return. Default: 10, Maximum: 100. - `query` (object): Filter criteria for Alert Internal Notes. Each field accepts a direct value (exact match) or an operator object {"_type": "", "value": ...}. Operators: EqualTo, NotEqual, IsNull, NotNull, E… - `select` (array): Optional: field names to return for each Alert Internal Note (e.g. ["_id", "name"]). Omit to get all readable fields. Large fields excluded by default (request explicitly if needed): savedFromChatMes… - `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. ### `update_alert_internal_note` (~144 tokens) Update Alert Internal Note 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. Input parameters: - `attachments` (array): Files attached to this note. - `id` (string, required): 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. ### `delete_alert_internal_note` (~61 tokens) Delete Alert Internal Note Permanently delete a Alert Internal Note from OneUptime. This action cannot be undone. Returns a confirmation message upon successful deletion. Input parameters: - `id` (string, required): The unique identifier (UUID) of the Alert Internal Note to delete. This action is irreversible. ### `count_alert_internal_notes` (~189 tokens) Count Alert Internal Notes Count the total number of Alert Internal Notes in OneUptime, optionally filtered by query criteria. Returns a single number. Useful for dashboards, reports, or checking if records exist before listing. Input parameters: - `query` (object): Optional filter criteria. If omitted, counts all Alert Internal Notes. Each field accepts a direct value (exact match) or an operator object {"_type": "", "value": ...}. Operators: EqualTo,… ### `create_alert_severity` (~195 tokens) Create Alert Severity Create a new Alert Severity in OneUptime. Returns the created Alert Severity object with its ID. Use this to add new Alert Severities to your project. Note: projectId is inferred from your API key — you do not need to provide it. Input parameters: - `color` (object, required): Color of this resource in Hex (#32a852 for example). - `description` (string): Friendly description that will help you remember. - `name` (string, required): 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… - `projectId` (string): ID of your OneUptime Project in which this object belongs. ### `get_alert_severity` (~115 tokens) Get Alert Severity Retrieve a single Alert Severity by its unique ID from OneUptime. Use list_alert_severities first if you need to find the ID. Input parameters: - `id` (string, required): The unique identifier (UUID) of the Alert Severity to retrieve. Example: "550e8400-e29b-41d4-a716-446655440000" - `select` (array): Optional: field names to return for each Alert Severity (e.g. ["_id", "name"]). Omit to get all readable fields. ### `list_alert_severities` (~308 tokens) List Alert Severities List and search Alert Severities from OneUptime with optional filtering, pagination, and sorting. Returns an array of Alert Severity objects plus the total matching count. Input parameters: - `limit` (number): Maximum number of records to return. Default: 10, Maximum: 100. - `query` (object): Filter criteria for Alert Severities. Each field accepts a direct value (exact match) or an operator object {"_type": "", "value": ...}. Operators: EqualTo, NotEqual, IsNull, NotNull, Equal… - `select` (array): Optional: field names to return for each Alert Severity (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. ### `update_alert_severity` (~192 tokens) Update Alert Severity 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. Input parameters: - `color` (object): Color of this resource in Hex (#32a852 for example). - `description` (string): Friendly description that will help you remember. - `id` (string, required): 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… ### `delete_alert_severity` (~59 tokens) Delete Alert Severity Permanently delete a Alert Severity from OneUptime. This action cannot be undone. Returns a confirmation message upon successful deletion. Input parameters: - `id` (string, required): The unique identifier (UUID) of the Alert Severity to delete. This action is irreversible. ### `count_alert_severities` (~190 tokens) Count Alert Severities Count the total number of Alert Severities in OneUptime, optionally filtered by query criteria. Returns a single number. Useful for dashboards, reports, or checking if records exist before listing. Input parameters: - `query` (object): Optional filter criteria. If omitted, counts all Alert Severities. Each field accepts a direct value (exact match) or an operator object {"_type": "", "value": ...}. Operators: EqualTo, Not… ### `create_incident_alert` (~115 tokens) Create Incident Alert Create a new Incident Alert in OneUptime. Returns the created Incident Alert object with its ID. Use this to add new Incident Alerts to your project. Note: projectId is inferred from your API key — you do not need to provide it. Input parameters: - `alertId` (string, required): ID of the Alert that is linked to the incident. - `incidentId` (string, required): ID of the Incident this alert is linked to. - `projectId` (string): ID of your OneUptime Project in which this object belongs. ### `get_incident_alert` (~115 tokens) Get Incident Alert Retrieve a single Incident Alert by its unique ID from OneUptime. Use list_incident_alerts first if you need to find the ID. Input parameters: - `id` (string, required): The unique identifier (UUID) of the Incident Alert to retrieve. Example: "550e8400-e29b-41d4-a716-446655440000" - `select` (array): Optional: field names to return for each Incident Alert (e.g. ["_id", "name"]). Omit to get all readable fields. ### `list_incident_alerts` (~306 tokens) List Incident Alerts List and search Incident Alerts from OneUptime with optional filtering, pagination, and sorting. Returns an array of Incident Alert objects plus the total matching count. Input parameters: - `limit` (number): Maximum number of records to return. Default: 10, Maximum: 100. - `query` (object): Filter criteria for Incident Alerts. Each field accepts a direct value (exact match) or an operator object {"_type": "", "value": ...}. Operators: EqualTo, NotEqual, IsNull, NotNull, EqualT… - `select` (array): Optional: field names to return for each Incident Alert (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. ### `update_incident_alert` (~78 tokens) Update Incident Alert 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. Input parameters: - `id` (string, required): The unique identifier (UUID) of the Incident Alert to update. Required. Use list_incident_alerts to find IDs. ### `delete_incident_alert` (~59 tokens) Delete Incident Alert Permanently delete a Incident Alert from OneUptime. This action cannot be undone. Returns a confirmation message upon successful deletion. Input parameters: - `id` (string, required): The unique identifier (UUID) of the Incident Alert to delete. This action is irreversible. ### `count_incident_alerts` (~188 tokens) Count Incident Alerts Count the total number of Incident Alerts in OneUptime, optionally filtered by query criteria. Returns a single number. Useful for dashboards, reports, or checking if records exist before listing. Input parameters: - `query` (object): Optional filter criteria. If omitted, counts all Incident Alerts. Each field accepts a direct value (exact match) or an operator object {"_type": "", "value": ...}. Operators: EqualTo, NotE… ### `create_monitor_status_event` (~165 tokens) Create Monitor Status Event Create a new Monitor Status Event in OneUptime. Returns the created Monitor Status Event object with its ID. Use this to add new Monitor Status Events to your project. Note: projectId is inferred from your API key — you do not need to provide it. Input parameters: - `endsAt` (object): When did this status change end? - `monitorId` (string, required): Relation to Monitor ID Resource in which this object belongs. - `monitorStatusId` (string, required): Relation to Monitor Status ID Resource in which this object belongs. - `projectId` (string): ID of your OneUptime Project in which this object belongs. - `rootCause` (string): What is the root cause of this status change? - `startsAt` (object): When did this status change? ### `get_monitor_status_event` (~132 tokens) Get Monitor Status Event Retrieve a single Monitor Status Event by its unique ID from OneUptime. Use list_monitor_status_events first if you need to find the ID. Input parameters: - `id` (string, required): The unique identifier (UUID) of the Monitor Status Event to retrieve. Example: "550e8400-e29b-41d4-a716-446655440000" - `select` (array): Optional: field names to return for each Monitor Status Event (e.g. ["_id", "name"]). Omit to get all readable fields. Large fields excluded by default (request explicitly if needed): statusChangeLog. ### `list_monitor_status_events` (~324 tokens) List Monitor Status Events List and search Monitor Status Events from OneUptime with optional filtering, pagination, and sorting. Returns an array of Monitor Status Event objects plus the total matching count. Input parameters: - `limit` (number): Maximum number of records to return. Default: 10, Maximum: 100. - `query` (object): Filter criteria for Monitor Status Events. Each field accepts a direct value (exact match) or an operator object {"_type": "", "value": ...}. Operators: EqualTo, NotEqual, IsNull, NotNull,… - `select` (array): Optional: field names to return for each Monitor Status Event (e.g. ["_id", "name"]). Omit to get all readable fields. Large fields excluded by default (request explicitly if needed): statusChangeLog. - `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. ### `update_monitor_status_event` (~99 tokens) Update Monitor Status Event 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. Input parameters: - `id` (string, required): 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. ### `delete_monitor_status_event` (~61 tokens) Delete Monitor Status Event Permanently delete a Monitor Status Event from OneUptime. This action cannot be undone. Returns a confirmation message upon successful deletion. Input parameters: - `id` (string, required): The unique identifier (UUID) of the Monitor Status Event to delete. This action is irreversible. ### `count_monitor_status_events` (~189 tokens) Count Monitor Status Events Count the total number of Monitor Status Events in OneUptime, optionally filtered by query criteria. Returns a single number. Useful for dashboards, reports, or checking if records exist before listing. Input parameters: - `query` (object): Optional filter criteria. If omitted, counts all Monitor Status Events. Each field accepts a direct value (exact match) or an operator object {"_type": "", "value": ...}. Operators: EqualTo… ### `create_status_page_announcement` (~216 tokens) Create Status Page Announcement Create a new Status Page Announcement in OneUptime. Returns the created Status Page Announcement object with its ID. Use this to add new Status Page Announcements to your project. Note: projectId is inferred from your API key — you do not need to provide it. Input parameters: - `attachments` (array): Files attached to this announcement. - `description` (string, required): Text of the announcement. This can be in Markdown format. - `endAnnouncementAt` (object): When should this announcement hidden? - `monitors` (array): List of monitors affected by this announcement. If none are selected, all subscribers will be notified. - `projectId` (string): ID of your OneUptime Project in which this object belongs. - `shouldStatusPageSubscribersBeNotified` (boolean): Should subscribers be notified about this announcement? - `showAnnouncementAt` (object, required): When should this announcement be shown? - `statusPages` (array): Status Pages to show show this announcement on. - `title` (string, required): Title of this resource. ### `get_status_page_announcement` (~143 tokens) Get Status Page Announcement Retrieve a single Status Page Announcement by its unique ID from OneUptime. Use list_status_page_announcements first if you need to find the ID. Input parameters: - `id` (string, required): The unique identifier (UUID) of the Status Page Announcement to retrieve. Example: "550e8400-e29b-41d4-a716-446655440000" - `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… ### `list_status_page_announcements` (~336 tokens) List Status Page Announcements 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. Input parameters: - `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": "", "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. ### `update_status_page_announcement` (~193 tokens) Update Status Page Announcement Update an existing Status Page Announcement in OneUptime. Only include the fields you want to change - unspecified fields will remain unchanged. Use get_status_page_announcement afterwards to see the updated record. Input parameters: - `attachments` (array): Files attached to this announcement. - `description` (string): Text of the announcement. This can be in Markdown format. - `endAnnouncementAt` (object): When should this announcement hidden? - `id` (string, required): The unique identifier (UUID) of the Status Page Announcement to update. Required. Use list_status_page_announcements to find IDs. - `monitors` (array): List of monitors affected by this announcement. If none are selected, all subscribers will be notified. - `showAnnouncementAt` (object): When should this announcement be shown? - `statusPages` (array): Status Pages to show show this announcement on. - `title` (string): Title of this resource. ### `delete_status_page_announcement` (~62 tokens) Delete Status Page Announcement Permanently delete a Status Page Announcement from OneUptime. This action cannot be undone. Returns a confirmation message upon successful deletion. Input parameters: - `id` (string, required): The unique identifier (UUID) of the Status Page Announcement to delete. This action is irreversible. ### `count_status_page_announcements` (~192 tokens) Count Status Page Announcements Count the total number of Status Page Announcements in OneUptime, optionally filtered by query criteria. Returns a single number. Useful for dashboards, reports, or checking if records exist before listing. Input parameters: - `query` (object): Optional filter criteria. If omitted, counts all Status Page Announcements. Each field accepts a direct value (exact match) or an operator object {"_type": "", "value": ...}. Operators: Equ… ### `create_scheduled_maintenance_state` (~285 tokens) Create Scheduled Maintenance State Create a new Scheduled Maintenance State in OneUptime. Returns the created Scheduled Maintenance State object with its ID. Use this to add new Scheduled Maintenance States to your project. Note: projectId is inferred from your API key — you do not need to provide it. Input parameters: - `color` (object, required): Color of this resource in Hex (#32a852 for example). - `description` (string): Friendly description that will help you remember. - `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, required): 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… - `projectId` (string): ID of your OneUptime Project in which this object belongs. ### `get_scheduled_maintenance_state` (~121 tokens) Get Scheduled Maintenance State Retrieve a single Scheduled Maintenance State by its unique ID from OneUptime. Use list_scheduled_maintenance_states first if you need to find the ID. Input parameters: - `id` (string, required): The unique identifier (UUID) of the Scheduled Maintenance State to retrieve. Example: "550e8400-e29b-41d4-a716-446655440000" - `select` (array): Optional: field names to return for each Scheduled Maintenance State (e.g. ["_id", "name"]). Omit to get all readable fields. ### `list_scheduled_maintenance_states` (~311 tokens) List Scheduled Maintenance States 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. Input parameters: - `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": "", "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. ### `update_scheduled_maintenance_state` (~285 tokens) Update Scheduled Maintenance State 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. Input parameters: - `color` (object): Color of this resource in Hex (#32a852 for example). - `description` (string): Friendly description that will help you remember. - `id` (string, required): 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… ### `delete_scheduled_maintenance_state` (~63 tokens) Delete Scheduled Maintenance State Permanently delete a Scheduled Maintenance State from OneUptime. This action cannot be undone. Returns a confirmation message upon successful deletion. Input parameters: - `id` (string, required): The unique identifier (UUID) of the Scheduled Maintenance State to delete. This action is irreversible. ### `count_scheduled_maintenance_states` (~191 tokens) Count Scheduled Maintenance States Count the total number of Scheduled Maintenance States in OneUptime, optionally filtered by query criteria. Returns a single number. Useful for dashboards, reports, or checking if records exist before listing. Input parameters: - `query` (object): Optional filter criteria. If omitted, counts all Scheduled Maintenance States. Each field accepts a direct value (exact match) or an operator object {"_type": "", "value": ...}. Operators:… ### `create_scheduled_maintenance_event` (~697 tokens) Create Scheduled Maintenance Event Create a new Scheduled Maintenance Event in OneUptime. Returns the created Scheduled Maintenance Event object with its ID. Use this to add new Scheduled Maintenance Events to your project. Note: projectId is inferred from your API key — you do not need to provide it. Input parameters: - `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, required): When does this event end? - `hosts` (array): List of hosts affected by this event. - `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. - `projectId` (string): ID of your OneUptime Project in which this object belongs. - `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. - `shouldStatusPageSubscribersBeNotifiedOnEventCreated` (boolean): Should subscribers be notified about this event creation? - `shouldStatusPageSubscribersBeNotifiedWhenEventChangedToEnded` (boolean): Should subscribers be notified about this event event is changed to ended? - `shouldStatusPageSubscribersBeNotifiedWhenEventChangedToOngoing` (boolean): Should subscribers be notified about this event event is changed to ongoing? - `startsAt` (object, required): 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, required): Title of this scheduled event. - `vmwareVCenters` (array): List of vCenters affected by this event. ### `get_scheduled_maintenance_event` (~148 tokens) Get Scheduled Maintenance Event Retrieve a single Scheduled Maintenance Event by its unique ID from OneUptime. Use list_scheduled_maintenance_events first if you need to find the ID. Input parameters: - `id` (string, required): The unique identifier (UUID) of the Scheduled Maintenance Event to retrieve. Example: "550e8400-e29b-41d4-a716-446655440000" - `select` (array): Optional: field names to return for each Scheduled Maintenance Event (e.g. ["_id", "name"]). Omit to get all readable fields. Large fields excluded by default (request explicitly if needed): subscrib… ### `list_scheduled_maintenance_events` (~338 tokens) List Scheduled Maintenance Events List and search Scheduled Maintenance Events from OneUptime with optional filtering, pagination, and sorting. Returns an array of Scheduled Maintenance Event objects plus the total matching count. Input parameters: - `limit` (number): Maximum number of records to return. Default: 10, Maximum: 100. - `query` (object): Filter criteria for Scheduled Maintenance Events. Each field accepts a direct value (exact match) or an operator object {"_type": "", "value": ...}. Operators: EqualTo, NotEqual, IsNull, No… - `select` (array): Optional: field names to return for each Scheduled Maintenance Event (e.g. ["_id", "name"]). Omit to get all readable fields. Large fields excluded by default (request explicitly if needed): subscrib… - `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. ### `update_scheduled_maintenance_event` (~612 tokens) Update Scheduled Maintenance Event 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. Input parameters: - `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, required): 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. ### `delete_scheduled_maintenance_event` (~63 tokens) Delete Scheduled Maintenance Event Permanently delete a Scheduled Maintenance Event from OneUptime. This action cannot be undone. Returns a confirmation message upon successful deletion. Input parameters: - `id` (string, required): The unique identifier (UUID) of the Scheduled Maintenance Event to delete. This action is irreversible. ### `count_scheduled_maintenance_events` (~191 tokens) Count Scheduled Maintenance Events Count the total number of Scheduled Maintenance Events in OneUptime, optionally filtered by query criteria. Returns a single number. Useful for dashboards, reports, or checking if records exist before listing. Input parameters: - `query` (object): Optional filter criteria. If omitted, counts all Scheduled Maintenance Events. Each field accepts a direct value (exact match) or an operator object {"_type": "", "value": ...}. Operators:… ### `create_scheduled_maintenance_state_timeline` (~202 tokens) Create Scheduled Maintenance State Timeline Create a new Scheduled Maintenance State Timeline in OneUptime. Returns the created Scheduled Maintenance State Timeline object with its ID. Use this to add new Scheduled Maintenance State Timelines to your project. Note: projectId is inferred from your API key — you do not need to provide it. Input parameters: - `endsAt` (object): When did this status change end? - `projectId` (string): ID of your OneUptime Project in which this object belongs. - `scheduledMaintenanceId` (string, required): ID of Scheduled Maintenance this resource belongs to. - `scheduledMaintenanceStateId` (string, required): Scheduled Maintenance State ID. Which state does this event belongs to? - `shouldStatusPageSubscribersBeNotified` (boolean): Should subscribers be notified about this state change? - `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. ### `get_scheduled_maintenance_state_timeline` (~144 tokens) Get Scheduled Maintenance State Timeline Retrieve a single Scheduled Maintenance State Timeline by its unique ID from OneUptime. Use list_scheduled_maintenance_state_timelines first if you need to find the ID. Input parameters: - `id` (string, required): The unique identifier (UUID) of the Scheduled Maintenance State Timeline to retrieve. Example: "550e8400-e29b-41d4-a716-446655440000" - `select` (array): Optional: field names to return for each Scheduled Maintenance State Timeline (e.g. ["_id", "name"]). Omit to get all readable fields. Large fields excluded by default (request explicitly if needed):… ### `list_scheduled_maintenance_state_timelines` (~335 tokens) List Scheduled Maintenance State Timelines List and search Scheduled Maintenance State Timelines from OneUptime with optional filtering, pagination, and sorting. Returns an array of Scheduled Maintenance State Timeline objects plus the total matching count. Input parameters: - `limit` (number): Maximum number of records to return. Default: 10, Maximum: 100. - `query` (object): Filter criteria for Scheduled Maintenance State Timelines. Each field accepts a direct value (exact match) or an operator object {"_type": "", "value": ...}. Operators: EqualTo, NotEqual, I… - `select` (array): Optional: field names to return for each Scheduled Maintenance State Timeline (e.g. ["_id", "name"]). Omit to get all readable fields. Large fields excluded by default (request explicitly if needed):… - `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. ### `update_scheduled_maintenance_state_timeline` (~152 tokens) Update Scheduled Maintenance State Timeline 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. Input parameters: - `id` (string, required): 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. ### `delete_scheduled_maintenance_state_timeline` (~67 tokens) Delete Scheduled Maintenance State Timeline Permanently delete a Scheduled Maintenance State Timeline from OneUptime. This action cannot be undone. Returns a confirmation message upon successful deletion. Input parameters: - `id` (string, required): The unique identifier (UUID) of the Scheduled Maintenance State Timeline to delete. This action is irreversible. ### `count_scheduled_maintenance_state_timelines` (~197 tokens) Count Scheduled Maintenance State Timelines Count the total number of Scheduled Maintenance State Timelines in OneUptime, optionally filtered by query criteria. Returns a single number. Useful for dashboards, reports, or checking if records exist before listing. Input parameters: - `query` (object): Optional filter criteria. If omitted, counts all Scheduled Maintenance State Timelines. Each field accepts a direct value (exact match) or an operator object {"_type": "", "value": ...}. Op… ### `list_logs` (~426 tokens) List Logs Query Logs 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": "", "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"}}. Input parameters: - `limit` (number): Maximum number of records to return. Default: 10, Maximum: 100. Keep small for telemetry queries. - `query` (object): Filter criteria for Logs. Always include a time-range filter. Each field accepts a direct value (exact match) or an operator object {"_type": "", "value": ...}. Operators: EqualTo, NotEqual… - `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. ### `count_logs` (~160 tokens) Count Logs Count Logs telemetry records in OneUptime, optionally filtered. Prefer counting with a time-range filter. Input parameters: - `query` (object): Optional filter criteria. Each field accepts a direct value (exact match) or an operator object {"_type": "", "value": ...}. Operators: EqualTo, NotEqual, IsNull, NotNull, EqualToOrNull, Gr… ### `list_spans` (~429 tokens) List Spans 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": "", "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"}}. Input parameters: - `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": "", "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. ### `count_spans` (~162 tokens) Count Spans Count Spans telemetry records in OneUptime, optionally filtered. Prefer counting with a time-range filter. Input parameters: - `query` (object): Optional filter criteria. Each field accepts a direct value (exact match) or an operator object {"_type": "", "value": ...}. Operators: EqualTo, NotEqual, IsNull, NotNull, EqualToOrNull, Gr… ### `list_metrics` (~426 tokens) List Metrics Query Metrics 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": "", "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"}}. Input parameters: - `limit` (number): Maximum number of records to return. Default: 10, Maximum: 100. Keep small for telemetry queries. - `query` (object): Filter criteria for Metrics. Always include a time-range filter. Each field accepts a direct value (exact match) or an operator object {"_type": "", "value": ...}. Operators: EqualTo, NotEq… - `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. ### `count_metrics` (~160 tokens) Count Metrics Count Metrics telemetry records in OneUptime, optionally filtered. Prefer counting with a time-range filter. Input parameters: - `query` (object): Optional filter criteria. Each field accepts a direct value (exact match) or an operator object {"_type": "", "value": ...}. Operators: EqualTo, NotEqual, IsNull, NotNull, EqualToOrNull, Gr… ### `list_exception_instances` (~429 tokens) List Exception Instances Query Exception Instances 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": "", "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"}}. Input parameters: - `limit` (number): Maximum number of records to return. Default: 10, Maximum: 100. Keep small for telemetry queries. - `query` (object): Filter criteria for Exception Instances. Always include a time-range filter. Each field accepts a direct value (exact match) or an operator object {"_type": "", "value": ...}. Operators: Eq… - `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. ### `count_exception_instances` (~162 tokens) Count Exception Instances Count Exception Instances telemetry records in OneUptime, optionally filtered. Prefer counting with a time-range filter. Input parameters: - `query` (object): Optional filter criteria. Each field accepts a direct value (exact match) or an operator object {"_type": "", "value": ...}. Operators: EqualTo, NotEqual, IsNull, NotNull, EqualToOrNull, Gr… ### `list_monitor_logs` (~429 tokens) List Monitor Logs Query Monitor Logs 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": "", "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"}}. Input parameters: - `limit` (number): Maximum number of records to return. Default: 10, Maximum: 100. Keep small for telemetry queries. - `query` (object): Filter criteria for Monitor Logs. Always include a time-range filter. Each field accepts a direct value (exact match) or an operator object {"_type": "", "value": ...}. Operators: EqualTo,… - `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. ### `count_monitor_logs` (~162 tokens) Count Monitor Logs Count Monitor Logs telemetry records in OneUptime, optionally filtered. Prefer counting with a time-range filter. Input parameters: - `query` (object): Optional filter criteria. Each field accepts a direct value (exact match) or an operator object {"_type": "", "value": ...}. Operators: EqualTo, NotEqual, IsNull, NotNull, EqualToOrNull, Gr… ### `list_kubernetes_cost_allocations` (~436 tokens) List Kubernetes Cost Allocations Query Kubernetes Cost Allocations 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": "", "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"}}. Input parameters: - `limit` (number): Maximum number of records to return. Default: 10, Maximum: 100. Keep small for telemetry queries. - `query` (object): Filter criteria for Kubernetes Cost Allocations. Always include a time-range filter. Each field accepts a direct value (exact match) or an operator object {"_type": "", "value": ...}. Opera… - `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. ### `count_kubernetes_cost_allocations` (~167 tokens) Count Kubernetes Cost Allocations Count Kubernetes Cost Allocations telemetry records in OneUptime, optionally filtered. Prefer counting with a time-range filter. Input parameters: - `query` (object): Optional filter criteria. Each field accepts a direct value (exact match) or an operator object {"_type": "", "value": ...}. Operators: EqualTo, NotEqual, IsNull, NotNull, EqualToOrNull, Gr… ### `list_security_events` (~429 tokens) List Security Events 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": "", "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"}}. Input parameters: - `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": "", "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. ### `count_security_events` (~162 tokens) Count Security Events Count Security Events telemetry records in OneUptime, optionally filtered. Prefer counting with a time-range filter. Input parameters: - `query` (object): Optional filter criteria. Each field accepts a direct value (exact match) or an operator object {"_type": "", "value": ...}. Operators: EqualTo, NotEqual, IsNull, NotNull, EqualToOrNull, Gr… ### `list_change_events` (~429 tokens) List Change Events Query Change 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": "", "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"}}. Input parameters: - `limit` (number): Maximum number of records to return. Default: 10, Maximum: 100. Keep small for telemetry queries. - `query` (object): Filter criteria for Change Events. Always include a time-range filter. Each field accepts a direct value (exact match) or an operator object {"_type": "", "value": ...}. Operators: EqualTo,… - `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. ### `count_change_events` (~162 tokens) Count Change Events Count Change Events telemetry records in OneUptime, optionally filtered. Prefer counting with a time-range filter. Input parameters: - `query` (object): Optional filter criteria. Each field accepts a direct value (exact match) or an operator object {"_type": "", "value": ...}. Operators: EqualTo, NotEqual, IsNull, NotNull, EqualToOrNull, Gr… ### `list_threat_intel_indicators` (~435 tokens) List Threat Intel Indicators 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": "", "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"}}. Input parameters: - `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": "", "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. ### `count_threat_intel_indicators` (~167 tokens) Count Threat Intel Indicators Count Threat Intel Indicators telemetry records in OneUptime, optionally filtered. Prefer counting with a time-range filter. Input parameters: - `query` (object): Optional filter criteria. Each field accepts a direct value (exact match) or an operator object {"_type": "", "value": ...}. Operators: EqualTo, NotEqual, IsNull, NotNull, EqualToOrNull, Gr… ### `acknowledge_incident` (~99 tokens) Acknowledge Incident Acknowledge an incident: marks it as being worked on by moving it to the project's 'Acknowledged' state. Equivalent to pressing 'Acknowledge' in the OneUptime dashboard. An incident that is already acknowledged - in the Acknowledged state, a state placed after it, or resolved - is left as it is. Input parameters: - `incidentId` (string, required): UUID of the incident to acknowledge. Use list_incidents to find it. ### `resolve_incident` (~58 tokens) Resolve Incident Resolve an incident: moves it to the project's 'Resolved' state. Equivalent to pressing 'Resolve' in the OneUptime dashboard. Input parameters: - `incidentId` (string, required): UUID of the incident to resolve. Use list_incidents to find it. ### `acknowledge_alert` (~83 tokens) Acknowledge Alert Acknowledge an alert: marks it as being worked on by moving it to the project's 'Acknowledged' state. An alert that is already acknowledged - in the Acknowledged state, a state placed after it, or resolved - is left as it is. Input parameters: - `alertId` (string, required): UUID of the alert to acknowledge. Use list_alerts to find it. ### `resolve_alert` (~44 tokens) Resolve Alert Resolve an alert: moves it to the project's 'Resolved' state. Input parameters: - `alertId` (string, required): UUID of the alert to resolve. Use list_alerts to find it. ### `add_incident_note` (~102 tokens) Add Incident Note Add a note to an incident. Internal notes are visible to your team only; public notes are posted to the status page for subscribers/customers. Markdown is supported. Input parameters: - `incidentId` (string, required): UUID of the incident to annotate. - `note` (string, required): The note content (Markdown supported). - `visibility` (string): Where the note is visible: 'internal' (team only, default) or 'public' (posted to the status page). ### `add_alert_note` (~53 tokens) Add Alert Note Add an internal note to an alert, visible to your team. Markdown is supported. Input parameters: - `alertId` (string, required): UUID of the alert to annotate. - `note` (string, required): The note content (Markdown supported). ### `oneuptime_whoami` (~73 tokens) Who Am I 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. ### `oneuptime_help` (~887 tokens) OneUptime Help 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… Input parameters: - `topic` (string): Optional topic to get help on: 'resources', 'incidents', 'monitors', 'alerts', 'workflows', or 'examples' ### `oneuptime_list_resources` (~37 tokens) List OneUptime Resources List all available OneUptime resources and their supported operations. Use this to discover what resources you can manage through the MCP server. ### `get_public_status_page_overview` (~214 tokens) Get Status Page Overview Get the complete overview of a public status page including current status, resources, active incidents, scheduled maintenance, and announcements. This tool does NOT require an API key and works with public status pages. Status page owners can disable MCP access for their status page. If disabled, this tool returns an error and the data must be read from the status page website or its RSS feed instead. USAGE: \- By domain: statusPageIdOrDomain = "status.company.com" \- By ID: statusPageIdOrDomain = "550e8400-e29b-41d4-a716-446655440000" RETURNS: \- Status page metadata (name, description, branding) \- Resources and their current status \- Active incidents \- Upcoming scheduled maintenance \- Active announcements \- Monitor status history Input parameters: - `statusPageIdOrDomain` (string, required): The status page ID (UUID) or domain name (e.g., 'status.company.com'). Use domain for public status pages with custom domains. ### `get_public_status_page_incidents` (~205 tokens) Get Status Page Incidents Get incidents from a public status page. This tool does NOT require an API key and works with public status pages. Status page owners can disable MCP access for their status page. If disabled, this tool returns an error and the data must be read from the status page website or its RSS feed instead. USAGE: \- By domain: statusPageIdOrDomain = "status.company.com" \- By ID: statusPageIdOrDomain = "550e8400-e29b-41d4-a716-446655440000" RETURNS: \- List of incidents (active and recent history) \- Incident details (title, description, severity) \- Incident timeline and state changes \- Public notes/updates for each incident Input parameters: - `incidentId` (string): Optional: Specific incident ID to fetch details for - `statusPageIdOrDomain` (string, required): The status page ID (UUID) or domain name (e.g., 'status.company.com') ### `get_public_status_page_scheduled_maintenance` (~215 tokens) Get Status Page Maintenance Get scheduled maintenance events from a public status page. This tool does NOT require an API key and works with public status pages. Status page owners can disable MCP access for their status page. If disabled, this tool returns an error and the data must be read from the status page website or its RSS feed instead. USAGE: \- By domain: statusPageIdOrDomain = "status.company.com" \- By ID: statusPageIdOrDomain = "550e8400-e29b-41d4-a716-446655440000" RETURNS: \- List of scheduled maintenance events (upcoming and ongoing) \- Maintenance details (title, description, scheduled times) \- Maintenance timeline and state changes \- Public notes/updates for each maintenance event Input parameters: - `scheduledMaintenanceId` (string): Optional: Specific scheduled maintenance ID to fetch details for - `statusPageIdOrDomain` (string, required): The status page ID (UUID) or domain name (e.g., 'status.company.com') ### `get_public_status_page_announcements` (~185 tokens) Get Status Page Announcements Get announcements from a public status page. This tool does NOT require an API key and works with public status pages. Status page owners can disable MCP access for their status page. If disabled, this tool returns an error and the data must be read from the status page website or its RSS feed instead. USAGE: \- By domain: statusPageIdOrDomain = "status.company.com" \- By ID: statusPageIdOrDomain = "550e8400-e29b-41d4-a716-446655440000" RETURNS: \- List of active announcements \- Announcement details (title, description, dates) Input parameters: - `announcementId` (string): Optional: Specific announcement ID to fetch details for - `statusPageIdOrDomain` (string, required): The status page ID (UUID) or domain name (e.g., 'status.company.com') ## Diagnostics Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-oneuptime-mcp/oneuptime#diagnostics ## Score history - 2026-10-23: 68 - 2026-10-22: 67 - 2026-10-21: 67 - 2026-10-20: 66 - 2026-10-19: 66 ## Common questions ### 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. ## Links - Remote endpoint: https://oneuptime.com/mcp - Repository: https://github.com/OneUptime/oneuptime - Website: https://oneuptime.com/docs/ai/mcp-server - Changelog RSS feed: https://verifymcp.io/servers/com-oneuptime-mcp/oneuptime.xml - Changelog JSON feed: https://verifymcp.io/servers/com-oneuptime-mcp/oneuptime.json - HTML version of this page: https://verifymcp.io/servers/com-oneuptime-mcp/oneuptime