OneUptime MCP server

• Addresshttps://oneuptime.com/mcpnot in the official registry: answered when asked

No entry in the official MCP registry names this server. It answered on oneuptime.com when the Atlas asked at the address servers are usually mounted on, so it is the vendor's own. Clients and catalogues that list servers from the registry do not show it.

• Stateanswerschecked 2026-10-26
• Tools211
• Server calls itselfoneuptime-mcp
• Server version14.0.92
• Protocol version2025-06-18

On 2026-10-26 the server answered initialize and tools/list without a sign-in. First answer in 120 ms.

• Its tools do none of the product's use cases we checked: trace checkout latency spikes to a database pool setting; post incident updates to users on a status page.
• Checked on 1 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 1 so far
• What an agent can do with it0 of 2 use cases
• Answeredmeasuring1 of the 7 daily checks it takes to print a share
• Median first answer102 ms
• Space in an agent's context≈ 222,559 tokensthe definitions of all its tools (211), which an agent carries on every turn
• Tool definitionsA · 100 of 100
• Typed results0 of 211 toolsdeclared outputSchema: results come typed, read once

• Every tool passes all six checks.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• 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.

• get_team

  Retrieve a single Team by its unique ID from OneUptime. Use list_teams first if you need to find the ID.

• 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.

• 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.

• delete_team

  Permanently delete a Team from OneUptime. This action cannot be undone. Returns a confirmation message upon successful deletion.

• 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.

• 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.

• get_label

  Retrieve a single Label by its unique ID from OneUptime. Use list_labels first if you need to find the ID.

• 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.

• 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.

• delete_label

  Permanently delete a Label from OneUptime. This action cannot be undone. Returns a confirmation message upon successful deletion.

• 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.

• 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.

• 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.

• 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.

• 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.

• delete_security_case

  Permanently delete a Security Case from OneUptime. This action cannot be undone. Returns a confirmation message upon successful deletion.

• 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.

• 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.

• 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.

• 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.

• 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.

• delete_security_case_note

  Permanently delete a Security Case Note from OneUptime. This action cannot be undone. Returns a confirmation message upon successful deletion.

• 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.

• create_security_case_priority

  Create a new Security Case Priority in OneUptime. Returns the created Security Case Priority object with its ID. Use this to add new Security Case Priorities to your project. Note: projectId is inferred from your API key — you do not need…

• get_security_case_priority

  Retrieve a single Security Case Priority by its unique ID from OneUptime. Use list_security_case_priorities first if you need to find the ID.

• list_security_case_priorities

  List and search Security Case Priorities from OneUptime with optional filtering, pagination, and sorting. Returns an array of Security Case Priority objects plus the total matching count.

• update_security_case_priority

  Update an existing Security Case Priority in OneUptime. Only include the fields you want to change - unspecified fields will remain unchanged. Use get_security_case_priority afterwards to see the updated record.

• delete_security_case_priority

  Permanently delete a Security Case Priority from OneUptime. This action cannot be undone. Returns a confirmation message upon successful deletion.

• count_security_case_priorities

  Count the total number of Security Case Priorities in OneUptime, optionally filtered by query criteria. Returns a single number. Useful for dashboards, reports, or checking if records exist before listing.

• create_security_case_status

  Create a new Security Case Status in OneUptime. Returns the created Security Case Status object with its ID. Use this to add new Security Case Statuses to your project. Note: projectId is inferred from your API key — you do not need to…

• get_security_case_status

  Retrieve a single Security Case Status by its unique ID from OneUptime. Use list_security_case_statuses first if you need to find the ID.

• list_security_case_statuses

  List and search Security Case Statuses from OneUptime with optional filtering, pagination, and sorting. Returns an array of Security Case Status objects plus the total matching count.

• update_security_case_status

  Update an existing Security Case Status in OneUptime. Only include the fields you want to change - unspecified fields will remain unchanged. Use get_security_case_status afterwards to see the updated record.

• delete_security_case_status

  Permanently delete a Security Case Status from OneUptime. This action cannot be undone. Returns a confirmation message upon successful deletion.

• count_security_case_statuses

  Count the total number of Security Case Statuses in OneUptime, optionally filtered by query criteria. Returns a single number. Useful for dashboards, reports, or checking if records exist before listing.

• 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

  Retrieve a single Security Detection by its unique ID from OneUptime. Use list_security_detections first if you need to find the ID.

• 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.

• 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.

• delete_security_detection

  Permanently delete a Security Detection from OneUptime. This action cannot be undone. Returns a confirmation message upon successful deletion.

• 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.

• 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.

• 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.

• 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.

• 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.

• delete_security_playbook

  Permanently delete a Security Playbook from OneUptime. This action cannot be undone. Returns a confirmation message upon successful deletion.

• 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.

• 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.

• 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.

• 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.

• 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.

• delete_status_page

  Permanently delete a Status Page from OneUptime. This action cannot be undone. Returns a confirmation message upon successful deletion.

• 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.

• 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.

• 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.

• 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.

• 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.

• delete_on_call_policy

  Permanently delete a On-Call Policy from OneUptime. This action cannot be undone. Returns a confirmation message upon successful deletion.

• 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.

The first 60 of 211, as the server listed them.