Uptimy

my.upti由 upti.my 发布官方发布者v1.0.0更新于 Nov 6, 2026

Uptime monitoring from your assistant: see what's down, run incidents, set up monitors and reports.

已验证Streamable HTTP可网页运行效率与工作流安全与监控

概览

AI 生成的概览

Uptimy 的远程 MCP 服务器：让助手查看哪些服务宕机、处理事件，并配置监控、告警和报告。

可以做什么
  • 读取监控状态：整体概览、单个监控项、按区域的上线率与延迟指标、事件及其时间线、关注的三方服务、告警和 SLA 报告
  • 扫描指定域名并建议值得监控的项目（不会新增任何内容）
  • 处理事件：开启事件、发布时间线更新、更改状态并发布到状态页，安排维护窗口
  • 管理监控项：添加网站、API、证书、端口、ping、DNS 及 cron 心跳检查，暂停或恢复，立即触发检查
  • 配置状态页、发送到 Slack、Discord、Teams、Telegram、PagerDuty、邮件或 webhook 的告警，以及上线率报告
适用场景
适合想通过助手了解当前故障与延迟情况，或让助手开启事件、发布状态更新、配置监控项、告警和报告，而不必切换到 Uptimy 应用的场景。
运行要求
通过 streamable HTTP 连接 mcp.upti.my 远程端点；需要 Uptimy 账户（免费方案即可），连接时用 OAuth 登录并选择助手可访问的工作区。不支持登录的客户端需在设置中创建 API 密钥，并以 Authorization Bearer 请求头发送。部分工具取决于套餐。
安装前请注意
24 个工具中有 14 个会修改数据：开启事件、发布公开状态更新、发布状态页、暂停监控、添加监控项、告警和报告。服务器会要求助手在发布公开更新、发布状态页或暂停监控前先与你确认。每个连接有独立 API 密钥，有效期 90 天，可在设置中撤销，应视为机密。不会删除任何内容，含机密的监控设置会以脱敏形式返回。

安装

在 SourceWeft 中

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

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

交给智能体安装

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

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

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

其他 MCP 客户端

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

{
  "mcpServers": {
    "uptimy": {
      "type": "http",
      "url": "https://mcp.upti.my/mcp"
    }
  }
}

README

[Uptimy]

Uptimy MCP server

Your uptime monitoring, in your AI assistant.
Ask what's down, run incidents and status page updates, and set up monitors, alerts and reports from Claude, ChatGPT or Cursor.

[CI] [License]

Connect · Tools · Docs

Uptimy monitors websites, APIs and cron jobs from several regions, opens incidents when something fails, and runs status pages and uptime reports. This is its remote MCP server, hosted at https://mcp.upti.my/mcp. Connect it and ask:

  • Is anything down right now?
  • Set up monitoring for my domain and alert #ops in Slack when something goes down.
  • Post an update on the open incident: the fix is deployed and we're monitoring.
  • How has my API's latency looked this week, per region?
  • Did we meet our SLA last month? Add a monthly report for Acme's monitors and email it to their CTO.

The assistant answers from your real checks, including the errors from failed ones. It also sees the third-party services you follow (GitHub, Cloudflare, Stripe, ...), so it can tell your problem apart from a provider's.

Connect

You need an Uptimy account; the free plan works. You sign in with it when you connect, so there's no key to copy.

Claude: open Customize → Connectors, choose + Add → Add custom connector and enter https://mcp.upti.my/mcp.

ChatGPT: add a custom connector in ChatGPT's connector settings with the same URL.

Claude Code:

bash
claude mcp add --transport http uptimy https://mcp.upti.my/mcp

Then run /mcp, pick uptimy and choose Authenticate.

Cursor (~/.cursor/mcp.json) and other clients that take a URL:

json
{  "mcpServers": {    "uptimy": {      "url": "https://mcp.upti.my/mcp"    }  }}

When you sign in, you pick the workspace the assistant may see. Each connection gets its own API key, valid for 90 days and marked AI assistant under Settings → API Keys, where you can revoke it at any time. For clients without sign-in support, create a key there and send it as a header: "headers": { "Authorization": "Bearer upt_..." }.

Tools

24 tools: 10 that read and 14 that change something.

ReadWhat it does
get_status_overviewEvery monitor, cron job monitor, open incident, status page and followed third-party service, problems first
get_monitorOne monitor's target, schedule, regions and current status
get_monitor_metricsUptime and latency over a time range, per region, with the latest failed checks and their errors
list_incidents, get_incidentRecent incidents, and one incident with its timeline
get_dependenciesThe third-party services Uptimy measures, their status, and which ones you follow
list_reports, get_uptime_reportYour uptime reports, and availability against the SLA target for any period
list_alertsWho hears about incidents: every alert, where it sends and whether it's paused
suggest_monitorsScans a domain you name for what's worth monitoring (the scan the app's Setup runs); adds nothing
ChangeWhat it does
create_incident, post_incident_updateOpen an incident; post timeline updates, change its status and publish it to status pages
schedule_maintenanceSchedule a maintenance window, optionally announced on status pages
set_monitor_paused, trigger_checkPause or resume a monitor; run a check right away to confirm a fix
follow_dependencyFollow or unfollow a third-party service, so its outages open incidents in your workspace
add_monitors, add_cron_monitorAdd website, API, certificate, port, ping and DNS checks; watch a cron job with a heartbeat
create_status_page, add_to_status_pageCreate a status page (private unless you ask); show more monitors on one
add_alert, set_alert_pausedSend incidents to Slack, Discord, Teams, Telegram, PagerDuty, email or a webhook; pause or resume an alert
add_report, update_reportAdd an uptime report, for example one per client emailed every month; change one

What each tool can do depends on your plan, as in the app: reports other than the weekly default, for example, need Growth and above.

What it won't do

  • Nothing deletes. Removing monitors, alerts, status pages or reports stays in the Uptimy app and uptimyctl, and so does editing a monitor's settings or a status page's design.
  • Adding twice is safe. The setup tools skip what's already monitored and return what already exists under the same name.
  • It asks first. Every tool is marked as read-only or not and destructive or not, so your client can ask before running it. The server also tells the assistant to confirm with you before posting public updates, publishing a status page or pausing monitors.

How it works

The server is a stateless gateway with no database and no credentials of its own. Every request carries the caller's API key. The server checks the key with the Uptimy API and forwards the request to the same API uptimyctl uses. Successful checks are cached for 3 minutes, so a revoked key stops working within a few minutes. Responses are trimmed before they reach the model. Monitor settings that can hold secrets (headers, bodies, tokens, passwords, scripts, ...) come back as [redacted].

It logs one line per request and one per tool call: the tool, the key's ID, how long it took and any error. It never logs arguments or results.

Sign-in is OAuth 2.1 with PKCE and dynamic client registration. https://api.upti.my is the authorization server, found through https://mcp.upti.my/.well-known/oauth-protected-resource/mcp.

Help & support

  • Questions and setup help: ask in Discord, in the #help forum. Say which assistant you connected (Claude, ChatGPT, Cursor, ...).
  • Bugs and feature requests: open an issue.
  • Security issues: report them privately, see SECURITY.md.
  • Uptimy account or billing: [email protected].

Contributing

Bug reports, fixes and new tools are welcome. See CONTRIBUTING.md for setup, how the code is laid out and how to add a tool. Report security issues privately (SECURITY.md).

License

Apache-2.0

来源：README.md，提交 a5fdb4a

工具

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

版本历史

1
  1. v1.0.0最新Nov 6, 2026

评分

已满足适用检查项的 85%

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

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

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

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