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 分