OneUptime
REMOTE · ONEUPTIME.COM
Manage incidents, alerts, monitors, status pages, on-call and telemetry in OneUptime.
Available components
Last scanned (19 minutes ago)
Scores higher than 57% of remote servers
Reachable. Last reached 23 Oct 2026.
Category Monitoring and Observability
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (create_team). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 48405 tokens (~243/item across 199 items; 199 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 28 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 199 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 23 Oct 26 +1
- New tool “create_postmortem_status”, which the server declares destructive security
- New tool “delete_postmortem_status”, which the server declares destructive security
- New tool “update_postmortem_status”, which the server declares destructive security
- Tool “oneuptime_help” rewrote its description, which is the text the model reads security
- Server version: 14.0.84 → 14.0.86 functional
- New tool “count_postmortem_statuses” functional
- New tool “get_postmortem_status” functional
- New tool “list_postmortem_statuses” functional
- “create_alert_severity” added an optional parameter “isArchived” cosmetic
- “create_alert_state” added an optional parameter “isArchived” cosmetic
- “create_incident” added an optional parameter “postmortemStatusId” cosmetic
- “create_incident_severity” added an optional parameter “isArchived” cosmetic
- “create_incident_state” added an optional parameter “isArchived” cosmetic
- “create_label” added an optional parameter “isArchived” cosmetic
- “create_monitor_status” added an optional parameter “isArchived” cosmetic
- “create_on_call_policy” added an optional parameter “acknowledgementTimeoutInMinutes” cosmetic
- “create_scheduled_maintenance_state” added an optional parameter “isArchived” cosmetic
- “update_alert_severity” added an optional parameter “isArchived” cosmetic
- “update_alert_state” added an optional parameter “isArchived” cosmetic
- “update_incident” added an optional parameter “postmortemStatusId” cosmetic
- “update_incident_severity” added an optional parameter “isArchived” cosmetic
- “update_incident_state” added an optional parameter “isArchived” cosmetic
- “update_label” added an optional parameter “isArchived” cosmetic
- “update_monitor_status” added an optional parameter “isArchived” cosmetic
- “update_on_call_policy” added an optional parameter “acknowledgementTimeoutInMinutes” cosmetic
- “update_scheduled_maintenance_state” added an optional parameter “isArchived” cosmetic
- 22 Oct 26 0
- Server version: 14.0.81 → 14.0.84 functional
- 21 Oct 26 +1
- Server version: 14.0.80 → 14.0.81 functional
- Server version: 14.0.78 → 14.0.80 functional
- 20 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- Server version: 14.0.77 → 14.0.78 functional
- Server version: 14.0.75 → 14.0.77 functional
- 19 Oct 26 66
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 23 Oct 2026 · Probed https://oneuptime.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=oneuptime.com | CN=WE1,O=Google Trust Services,C=US | 5 Oct 2026 | 3 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | b0e2565b80ba7ebc134ccc6465d30bed |
| SANs: oneuptime.com, *.oneuptime.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of oneuptime.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| oneuptime.com. | present | 2371 | 13 | Verified |
| oneuptime.com. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://oneuptime.com/mcp | Verified | 200 | |
| http (plaintext) | http://oneuptime.com/mcp | HTTPS enforced | 301 | https://oneuptime.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
update_team ~110
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| customFields | object | – | – |
| description | string | – | – |
| id | string | yes | – |
| name | string | – | – |
No output schema declared.
No examples provided.
How do I install the OneUptime MCP server?
OneUptime is a hosted endpoint at https://oneuptime.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · oneuptime.com
claude mcp add --transport http com-oneuptime-mcp 'https://oneuptime.com/mcp'
What is the OneUptime MCP server?
OneUptime is an MCP server listed in the public MCP registry as com.oneuptime/mcp. Manage incidents, alerts, monitors, status pages, on-call and telemetry in OneUptime. This page covers its hosted endpoint (https://oneuptime.com/mcp).
Is the OneUptime MCP server safe to use?
OneUptime scores 68 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
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.