Openuptime

app.openuptime由 openuptime.app 发布官方发布者v1.0.0更新于 Oct 24, 2026

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

已验证Streamable HTTP可网页运行云端与基础设施安全与监控

概览

AI 生成的概览

OpenUptime 的托管 MCP 端点，让 AI 助手在任意 MCP 客户端中管理可用性监控、故障事件和状态页。

可以做什么
  • 管理可用性监控：HTTP/HTTPS 关键词匹配、TCP、DNS、WebSocket、心跳、数据库与 RPC 节点检查
  • 处理故障事件：确认、指派和事后复盘，以及维护窗口
  • 维护公开状态页，包括订阅、徽章与嵌入
  • 管理团队的工作区、项目和角色
  • 同一套工具既可用于托管服务，也可用于自建实例的 /api/mcp 路径
适用场景
适合已经在 OpenUptime 中做可用性监控、希望助手无需打开控制台就能创建或调整监控、处理故障事件、更新状态页的团队。自建 OpenUptime 并希望让智能体访问自有实例的场景同样适用。
运行要求
需要远程 Streamable HTTP 端点（服务商的 /api/mcp 路径，或自建主机的对应路径）。必须使用 OAuth 授权，README 也提到可用 API 密钥替代。需要托管账户，或已部署的自建实例（含 Postgres 及相应密钥）。
安装前请注意
这些工具会改变监控状态：创建或修改监控、确认和指派故障事件、修改公开状态页，助手操作会直接呈现给访客和值班人员。托管服务按套餐计费，付费套餐自每月 5 美元起。自建需要 BETTER_AUTH_SECRET、CRON_SECRET 等密钥，托管版数据存放在服务商的数据库中。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Openuptime，将其添加到工作区。
  2. 连接 所需的 凭据。它们会被私密存储，绝不会在公开页面上展示。
  3. 为需要使用其工具的对话启用该服务。

Web executable，通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体，或 SourceWeft 对话中。智能体会读取该服务器的安装指南，先向你展示发布者、端点和登录方式，经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/app.openuptime%2Fmcp/install.md，并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前，先告诉我它的发布者、端点和登录方式，等我确认。不要把 API 密钥写进命令或我会提交的文件；问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。 客户端会在首次连接时完成 OAuth 登录。

{
  "mcpServers": {
    "openuptime": {
      "type": "http",
      "url": "https://openuptime.app/api/mcp"
    }
  }
}

README

[OpenUptime]

OpenUptime

Open-source uptime monitoring and status pages. Runs on Cloudflare Workers with Postgres, or in one Docker container.

Hosted version · Docs · Reference · MIT license

Features

Monitoring

  • HTTP / HTTPS with keyword matching and slow-response alerts
  • TCP, DNS and WebSocket
  • Heartbeat (push) monitors for cron jobs and background workers
  • PostgreSQL, MySQL and Redis
  • Domain expiry
  • EVM and Solana RPC node health
  • MCP server checks
  • Multi-region checks, with your own probes
  • Monitor dependencies, so a downstream outage doesn't page you twice

Incidents and status pages

  • Incidents with acknowledgement, assignment and postmortems
  • Maintenance windows, one-off or recurring
  • Public status pages
  • Email and RSS subscriptions for status page visitors
  • Status badges and embeds for your site or README

Alerts

  • Slack, Discord, Microsoft Teams, Telegram, Lark / Feishu and ntfy
  • PagerDuty, webhooks and email
  • Push notifications to the iOS app
  • Repeat reminders and escalation

Teams and automation

  • Workspaces, projects and roles
  • GitHub sign-in and two-factor authentication
  • REST API with API keys
  • MCP server so your AI agent can manage monitors, incidents and status pages
  • JSON import / export
PartStack
apps/apiHono, better-auth, Cloudflare Worker (cron + queue consumer)
apps/webAstro (static pages, SSR for status pages) + React islands
packages/repoStorage interface (Repo) and entity types
packages/db-pgPostgres implementation of Repo: Drizzle schema, migrations

Deploy to Cloudflare

The site is two Workers on one domain:

WorkerServesAlso does
openuptime-apiyour-domain/api/* (a Worker route on your zone)minute cron, queue consumer that runs the checks
openuptime-webeverything else on your-domain (a Worker custom domain)status pages (SSR); reaches the API through a service binding

Keeping the API under /api/* of the same domain means session cookies stay same-origin. You need no separate API hostname.

Before you start

  • A Cloudflare account and a domain whose DNS is on Cloudflare (the zone).
  • A Postgres database reachable from the internet (Neon, Supabase, RDS, your own). Workers connect through Hyperdrive.
  • Node.js 22+ and pnpm (corepack enable provides the pinned version).
  • Workers Paid plan for the Queue (default). On the Free plan, run in inline mode instead: see Reference.

1. Get the code and sign in

bash
git clone https://github.com/becoolme/openuptime.git && cd openuptimepnpm installcd apps/api && npx wrangler login

All npx wrangler … commands below run in apps/api unless noted.

2. Create the Queue and Hyperdrive

bash
npx wrangler queues create openuptime-checksnpx wrangler hyperdrive create openuptime-prod --connection-string="postgres://user:pass@host:5432/db"

The second command prints an id. In apps/api/wrangler.jsonc uncomment the hyperdrive line and paste it:

jsonc
"hyperdrive": [{ "binding": "HYPERDRIVE", "id": "<id printed above>" }],

The commented placement line is optional (it runs the Worker next to your database host); leave it commented unless you want that.

3. Create the schema

From the repository root:

bash
DATABASE_URL="postgres://user:pass@host:5432/db" pnpm db:migrate

It only applies what is new, so run it again after every upgrade. It never issues CREATE SCHEMA, so a role without database-level CREATE works too.

4. Point the config at your domain

Edit two files. In both, replace status.example.com with your own domain.

apps/api/wrangler.jsonc, where zone_name is the zone (the apex domain) even when you serve from a subdomain. Uncomment routes and set:

jsonc
"routes": [{ "pattern": "status.example.com/api/*", "zone_name": "example.com" }],"vars": {  "BETTER_AUTH_URL": "https://status.example.com",   // public origin: cookies, OAuth, email links  "WEB_ORIGIN": "https://status.example.com",        // same value  "EMAIL_FROM": "[email protected]"                 // sender address; optional, see below}

Email is optional: without it invitations and alerts are written to the Worker log. To send it, onboard your domain under Email Sending in the Cloudflare dashboard first (see Reference).

apps/web/wrangler.jsonc:

jsonc
"routes": [{ "pattern": "status.example.com", "custom_domain": true }],"vars": { "PRODUCT_URL": "https://status.example.com" }   // target of the "Powered by" link on status pages

The custom domain creates its DNS record and certificate for you; the hostname must not already have a DNS record pointing elsewhere.

No domain on Cloudflare? Leave routes out of both files and set BETTER_AUTH_URL and WEB_ORIGIN to the web Worker's https://openuptime-web.<your-subdomain>.workers.dev address. The web Worker then forwards /api/* to the API Worker through the service binding, so cookies stay same-origin.

5. Set the secrets

bash
npx wrangler secret put BETTER_AUTH_SECRET     # openssl rand -hex 32npx wrangler secret put CRON_SECRET            # any long random string; guards /internal/*

If wrangler asks to create the Worker first, answer yes. Optional: GITHUB_CLIENT_ID and GITHUB_CLIENT_SECRET add "Sign in with GitHub".

6. Deploy

bash
pnpm exec wrangler deploy                     # in apps/apicd ../web && pnpm build && pnpm exec wrangler deploy

Deploy the API first: the web Worker binds to it by name.

7. Check it

bash
curl https://status.example.com/api/health    # {"ok":true}

Open the domain and sign up. Once your own account exists you can set "DISABLE_SIGNUP": "true" in the API vars and deploy again to close registration (invited people can still join).

Upgrade later: pull, pnpm install, pnpm db:migrate, then deploy the API and the web Worker, in that order.

Self-host with Docker

One container runs the API, the web app and the check scheduler; Postgres comes with the compose file. Either run the published image or build it from source; the settings are the same.

Option A: run the published image

Tagged releases are published to ghcr.io/becoolme/openuptime for linux/amd64 and linux/arm64. You need no clone and no build:

bash
mkdir openuptime && cd openuptimecurl -fsSLO https://raw.githubusercontent.com/becoolme/openuptime/main/docker-compose.ymlcurl -fsSL https://raw.githubusercontent.com/becoolme/openuptime/main/.env.docker.example -o .env

Edit .env: set POSTGRES_PASSWORD and BETTER_AUTH_SECRET (openssl rand -hex 32), and uncomment OPENUPTIME_IMAGE. Pin a version (ghcr.io/becoolme/openuptime:0.1.0) or follow the newest release (:latest). Then:

bash
docker compose pull && docker compose up -d     # http://localhost:8080

Upgrade: change the tag if you pinned one, then run the same two commands again. Migrations run on start.

Option B: build from source

bash
git clone https://github.com/becoolme/openuptime.git && cd openuptimecp .env.docker.example .env      # set POSTGRES_PASSWORD and BETTER_AUTH_SECRET (openssl rand -hex 32)docker compose up -d --build     # http://localhost:8080

Upgrade: git pull, then docker compose up -d --build.

Either way

The schema is migrated on start and the data lives in the pgdata volume. Set PUBLIC_URL when the app is not served from http://localhost:8080. Email is optional; see Reference.

Once your own account exists, set DISABLE_SIGNUP=true in .env and run docker compose up -d to close registration (invited people can still join).

Develop

bash
pnpm installcp .env.example apps/api/.dev.vars   # edit DATABASE_URL and secretsDATABASE_URL=postgres://user:pass@localhost:5432/openuptime_dev pnpm db:migrate   # same URL as in .dev.varspnpm dev:api    # http://localhost:8787  (checks run inline every 15s)pnpm dev:web    # http://localhost:4321  (proxies /api to the API)pnpm typecheck

MCP server

Agents (Claude, Cursor, Codex and any MCP client) can manage monitors, incidents and status pages over Streamable HTTP at /api/mcp, authorizing with OAuth or an API key:

bash
claude mcp add --transport http openuptime https://openuptime.app/api/mcp   # or https://<your-host>/api/mcp

Client setup, scopes and the tool list are in the MCP docs. An agent skill that teaches the common workflows ships in skills/openuptime: npx skills add becoolme/openuptime. The hosted server is listed in the MCP Registry as app.openuptime/mcp; server.json is its entry.

Tests, how checks run, the MCP server, alert channels and the other details are in docs/reference.md.

Open source vs hosted

The monitoring itself is the same code in both. The hosted service at openuptime.app adds plans, billing and a few features that live only in that build; it plugs into this repo through one interface (Edition, see docs/editions.md), so nothing in the core is locked or throttled.

Self-hosted (this repo, MIT)Hosted (openuptime.app)
Monitors, incidents, status pages, alert channels, API, MCPAll of itAll of it
LimitsNone: no plans, quotas or meteringFree plan, paid plans from $5/month (pricing); monitors, checks, emails and history length depend on the plan
Running itYou: Postgres, the Worker or container, a mail provider, backups, upgradesWe do; nothing to install
SSL certificate monitoring (expiry alerts, ssl monitor type)Not includedLite and above
Custom domain for a status pageNot includedEvery paid plan (Lite and above), plus early-access workspaces
Where your data livesYour databaseOurs (Postgres on managed hosting)

Pick self-hosting if you want to own the data and the infrastructure, or have no limits to worry about. Pick hosted if you would rather not run anything. Both receive the same core updates.

Contributing & security

See CONTRIBUTING.md. Report vulnerabilities privately as described in SECURITY.md, not in public issues.

License

MIT

来源：README.md，提交 4a02d75

工具

0
该服务器需要登录，因此 SourceWeft 无法在没有账号的情况下读取其工具，也未收录。已连接账号所能看到的内容可能因账号及其权限而异。

版本历史

1
  1. v1.0.0最新Oct 15, 2026

评分

已满足适用检查项的 85%

该评分衡量此收录条目的完整程度，依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价，也不表示服务器安全或当前可用：可连通性是带日期的检查结果，评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list，或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分