# app.openuptime/mcp

Manage uptime monitors, incidents and status pages from any MCP client.

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the content rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 1.0.0
- **Author:** app.openuptime
- **License:** Unknown
- **Endpoints:** streamable-http https://openuptime.app/api/mcp
- **Source:** https://github.com/becoolme/openuptime
- **Endpoint health:** reachable (last checked 2026-10-16T11:16:30.042Z, 1 sample) — uptime is not a security property and is not part of the trust score
- **Compatible clients:** claude-code, cursor, copilot, chatgpt, gemini (basis: transport)

## Trust

60/100 (B), scored on the content rubric
- Publisher verified: no
- Install scripts: nothing suspicious found
- Prompt-injection scan: clean
- Obfuscation scan: clean
- Evidence age: 0 days

## Security scan

**Assessment scope:** Hosted endpoint only: Forge can assess who publishes it and whether it answers, not the code behind it. No CVE, dependency or source analysis applies, so nothing here is a clean bill for that code.
- **Status:** probed (endpoint answered; no code examined)
- **Scanned:** 2026-10-16T16:34:10.854Z
- **Version scanned:** HEAD
- **CVEs:** no coverage — this entry has no package coordinates to query OSV against, so "no known CVEs" is NOT asserted for it.

## Tools

22 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `list_workspaces` — List the workspaces and projects this connection can use, with their ids. Pass an id as `workspace` / `project` to any other tool to act there.
- `create_workspace` — Create a new workspace (with a first project) owned by the user. Only works when the user authorized access to all workspaces. Use the returned id as `workspace
- `create_project` — Create a project in a workspace (pass `workspace`; omit for the default one). Only works where this connection has access to all projects of that workspace. The
- `list_monitors` — List the monitors of the current project with status, uptime and latency.
- `get_monitor` — Get one monitor with its recent checks and uptime.
- `create_monitor` — Create a monitor. type is http, tcp, dns, heartbeat, postgres, mysql or redis; target is the URL, host:port or hostname. Omitted fields take defaults (60 s inte
- `update_monitor` — Change fields of a monitor; only the named fields are modified. Set paused to pause or resume it.
- `pause_monitor` — Pause a monitor: no checks run and no alerts are sent until it is resumed.
- `resume_monitor` — Resume a paused monitor.
- `run_check` — Run a check for a monitor right now and record the result. With `region` (an id from list_regions) it is one request from that region instead: the result is ret
- `list_regions` — List the regions checks can run from on this deployment (`auto` is always there) and how many one monitor may use. Set a monitor's `regions` to use them.
- `delete_monitor` — Permanently delete a monitor and its history.
- `list_incidents` — List incidents (open ones first), automatic and manual.
- `get_incident` — Get an incident with its update timeline and the failed checks around it.
- `create_incident` — Open a manual incident, optionally tied to a monitor. Appears on status pages that include that monitor.
- `post_incident_update` — Post a status update on an incident. status resolved closes it. Subscribers and alert channels are notified.
- `acknowledge_incident` — Acknowledge an incident as the API key's owner.
- `list_status_pages` — List the status pages of the current project.
- `create_status_page` — Create a public status page at /status/<slug> showing the given monitors (monitorIds). The slug is 3-40 lowercase letters, digits or hyphens and must be unused.
- `update_status_page` — Change a status page's title, theme, latency display or the monitors it shows (monitorIds replaces the list).
- `list_channels` — List alert channels (email, webhook, Slack…) with their ids, to attach to monitors.
- `list_maintenance` — List scheduled maintenance windows.

## Install

**Verdict: review** — Installable, but 3 things to check first: No CVE coverage: this entry has no npm/PyPI coordinates to query OSV against, so "no known vulnerabilities" is not a claim that can be made about it.
**Cautions** (coverage gaps and advisories — never blocking)
- No CVE coverage: this entry has no npm/PyPI coordinates to query OSV against, so "no known vulnerabilities" is not a claim that can be made about it.
- Hosted endpoint only: Forge can assess who publishes it and whether it answers, not the code behind it. No CVE, dependency or source analysis applies, so nothing here is a clean bill for that code.
- No publisher has proved control of this listing; it is indexed, not vouched for.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"mcp\": {\n      \"type\": \"http\",\n      \"url\": \"https://openuptime.app/api/mcp\"\n    }\n  }\n}"
```

## Blast radius

Moderate to extensive — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: deletes data; runs on someone else's infrastructure.
- Floor 32, ceiling 56 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/app.openuptime%2Fmcp
- Install plan: https://forgeregistry.com/api/v1/packages/app.openuptime%2Fmcp/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/app.openuptime%2Fmcp
- HTML page: https://forgeregistry.com/registry/app.openuptime%2Fmcp
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.