原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。评价和账户功能将在后续阶段推出。
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

UptimeRobot

作者:uptimerobot版本 0.1.0i★ –i在云端运行
注册名称com.uptimerobot/uptimerobot

安装

概览

作者提供的说明(英文原文)

Monitor websites, APIs, and servers: create monitors, triage incidents, and query uptime stats.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

安装

选择你使用的 AI 应用,然后复制设置。

安装之前

你需要

你用的是哪个应用?

在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。

适用于网页版、桌面版和手机版 Claude:

  1. 打开 Settings → Connectors
  2. 点击 Add custom connector
  3. 粘贴下面的地址,然后点击 Add
  4. 如果要求登录,请登录作者的服务
SettingsConnectors1+ Add2https://…3
https://mcp.uptimerobot.com/mcp

在终端中运行这条命令

claude mcp add --transport http uptimerobot https://mcp.uptimerobot.com/mcp

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "uptimerobot": {
      "url": "https://mcp.uptimerobot.com/mcp"
    }
  }
}

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "uptimerobot": {
      "type": "http",
      "url": "https://mcp.uptimerobot.com/mcp"
    }
  }
}

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

ChatGPT 只能连接互联网上的服务器:

  1. 打开网页版 ChatGPT → Settings → Connectors (Apps)
  2. 点击 Create 或 Add(部分套餐需要先在 Advanced 中开启 Developer mode)
  3. 粘贴下面的地址,起个名字,然后保存
  4. 如果要求登录,请登录作者的服务
SettingsConnectors1+ Create2https://…3
https://mcp.uptimerobot.com/mcp

菜单名称可能因套餐和版本不同而略有差异。

你的选择通过 Cookie 保存在这台设备上,无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。

它能做什么

我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过域名 uptimerobot.com 验证(注册中心会核实域名所有权)

  • … 尚未检查

    仍在维护

    我们还没有从 GitHub 读取这个仓库

  • … 尚未检查

    有许可证

    我们还没有从 GitHub 读取这个仓库

  • … 尚未检查

    端点有响应

    尚未检查;我们会轮流检查各个端点

  • … 尚未检查

    使用 OAuth 登录

    尚未检查;我们会轮流检查各个端点

  • … 尚未检查

    工具描述中没有隐藏指令

    尚未检查;我们会在检查端点时读取工具列表

与“其他”中的其他服务器比较i

  • 星标数多于此分类中其他 32435 个服务器的 0%
  • 发布到注册中心的时间比此分类中其他 32435 个服务器的 23% 更新
  • 基础检查结果等于或优于此分类中其他 32435 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

UptimeRobot 安全吗?

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端?

它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。

它还在维护吗?

GitHub 仓库最后更新于–,最新版本(0.1.0)于3个月前进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。

有什么可以替代它?

同一分类中有:Spec Driven Development, Remote Desktop Commander, Apify MCP Server

替代选择

同一分类中其他作者的服务器,按星标数排序。

如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Spec Driven Development

作者:formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

在你的电脑上运行★ 440MIT14个月前更新
安装

Remote Desktop Commander

作者:desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

在云端运行★ 211昨天更新
安装

Apify MCP Server

作者:apify

Extract data from any website with thousands of scrapers, crawlers, and automations on Apify Store ⚡

在云端运行今天更新
安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

UptimeRobot for AI agents

This repo is UptimeRobot's single source of truth for AI agent integrations. It publishes:

  • llms.txt and AGENTS.md — discovery and orientation for LLMs and coding agents.
  • .claude-plugin, .cursor-plugin, and .codex-plugin folders — installable plugin manifests for Claude Code, Cursor, and Codex.
  • skills folder — workflow skills (setup, no-account quick monitor, bulk pause, SLA reports, incident response, status pages) plus short per-tool reference pages that cover only what the MCP tool schemas don't say. See Skills.
  • rules folder — Cursor rules (.mdc). Claude Code gets the same rules from the conventions skill.
  • mcp.json — Cursor-format MCP server config (dot-less filename).
  • .mcp.json — Claude Code and Codex MCP server config (dot-prefixed so Claude Code auto-registers the server when the plugin loads; the Codex manifest references it explicitly, as OpenAI's plugin submission requires).
  • .agents/plugins/marketplace.json — repo-scoped Codex marketplace for local install and testing; Codex auto-discovers this file when the repo is open.
  • The assets folder — the marketplace logo, declared as the icon in the Cursor and Codex manifests (Claude Code's plugin manifest has no icon field; the directory listing supplies its icon at submission time).

The mcp.json and .mcp.json files both connect directly to the hosted server at https://mcp.uptimerobot.com/mcp over streamable HTTP. Nothing runs locally: the client discovers the server's OAuth endpoints and runs the browser login itself. Two filenames exist only because Cursor expects the dot-less name and Claude Code and Codex the dot-prefixed one.

The same content is mirrored under uptimerobot.com/ for crawler discovery (uptimerobot.com/llms.txt, uptimerobot.com/AGENTS.md, etc.).

Install

Claude Code
From the marketplace (once published)

UptimeRobot is being submitted to Anthropic's community plugin marketplace. Once accepted, add that marketplace once and install:

/plugin marketplace add anthropics/claude-plugins-community

/plugin install uptimerobot@claude-community

Or run /plugin, open the Discover tab, find UptimeRobot, and install it. (The community marketplace must be added first — it isn't built in. Only Anthropic's curated official marketplace shows up in /plugin with no setup.)

The MCP server auto-registers via .mcp.json as soon as the plugin loads. The first time it connects, a browser opens for you to log into UptimeRobot and authorize access (OAuth) — there's no API key to paste. Tokens are cached locally, so you only do this once.

Local clone (manual plugin install)

To run the full plugin (skills and the auto-registered MCP server) straight from a local checkout — no marketplace required — clone the repo and load it with the --plugin-dir flag:

git clone https://github.com/uptimerobot/ai.git

claude --plugin-dir ./ai

--plugin-dir loads the plugin from a directory (the one containing .claude-plugin/plugin.json) for that session only. The flag is repeatable and also accepts a .zip. Use an absolute path if you launch Claude Code from elsewhere:

claude --plugin-dir /absolute/path/to/ai

On first connection a browser opens for the OAuth flow. Run /plugin to confirm the plugin is loaded and uptimerobot MCP Server shows ✓ connected.

MCP server only (scripted)

If you just want the MCP tools without the rest of the plugin (dotfiles, CI bootstrap), register the server yourself:

claude mcp add --transport http uptimerobot https://mcp.uptimerobot.com/mcp

Then run /mcp, select uptimerobot, and choose Authenticate to complete the OAuth browser flow. Run /mcp (or claude mcp list in a terminal) to confirm uptimerobot shows ✓ connected.

Cursor
From the Marketplace (once published)

Browse the Cursor Marketplace, find UptimeRobot, and click Add to Cursor. Authorize through the OAuth browser flow when the MCP server first connects — no API key needed.

Local install (for development and pre-submission testing)

Follow Cursor's plugin docs:

# Clone or symlink this repo into Cursor's local plugin folder

git clone https://github.com/uptimerobot/ai.git ~/.cursor/plugins/local/uptimerobot-ai

Launch Cursor and run Developer: Reload Window from the command palette.

Verify the plugin is discovered:

  • Settings → Rules, Skills, Subagents — the uptimerobot.mdc rule and every skills/*/SKILL.md entry should be listed.
  • Settings → Tools & MCPs — uptimerobot should appear with up to 60 tools (fewer for read-only or team sessions) once the MCP server connects. Complete the OAuth browser flow on first connection.
Codex
Local install (for development and pre-submission testing)

Clone the repo and open it in Codex. The repo-scoped marketplace at .agents/plugins/marketplace.json is auto-discovered, so UptimeRobot (local) will appear in the Codex plugin directory without any extra setup. Install the plugin, then complete the OAuth browser flow on first MCP connection.

If you want Codex to track the source explicitly:

codex plugin marketplace add ./

Verify the plugin is loaded: the UptimeRobot skills should be available and the uptimerobot MCP server should appear with up to 60 tools (fewer for read-only or team sessions) once connected.

Other agents / direct MCP

The server is listed in the official MCP Registry as com.uptimerobot/uptimerobot, so any registry-aware client can discover and install it without a per-client plugin submission. Metadata lives in server.json:

curl -s "https://registry.modelcontextprotocol.io/v0.1/servers?search=com.uptimerobot/uptimerobot"

Clients without registry support can connect to the same URL directly (OAuth on first use):

{

"mcpServers": { "uptimerobot": { "type": "http", "url": "https://mcp.uptimerobot.com/mcp" } } }

Headless / CI (no browser)

Where the OAuth browser flow can't run, add the server to your own client config with an API key from the dashboard (Integrations & API) instead — a Read-only key unless the job needs to write. Keep the key in an environment variable, not in the file, and never commit it. This is a manual setup — the plugin itself never reads or sends an API key:

{

"mcpServers": { "uptimerobot": { "type": "http", "url": "https://mcp.uptimerobot.com/mcp", "headers": { "Authorization": "Bearer ${UPTIMEROBOT_API_KEY}" } } } }

Claude Code expands ${UPTIMEROBOT_API_KEY} from the environment; other clients have their own syntax (Cursor: ${env:UPTIMEROBOT_API_KEY}).

What the plugin provides

60 tools via MCP, grouped by resource — full list in AGENTS.md; each tool's own schema and description are the reference for its parameters:

Monitors
ToolPurpose
create-monitorCreate HTTP, KEYWORD, PING, PORT, HEARTBEAT, DNS, API, or UDP monitors
update-monitorChange name, URL, interval, alert contacts, tags, HTTP settings (list and map fields replace the whole value — see AGENTS.md)
update-monitor-statusPause or resume a monitor
list-monitorsPaginated list filtered by name, URL, tags, group, custom field, or state
get-monitor-detailsFull config + current state for one monitor
get-monitor-statsAggregated up/down/paused counts + uptime (a 0–1 fraction)
get-response-timesTime-series response-time data with buckets
delete-monitorPermanently delete a monitor and its history
Monitor groups (create/update/delete plan-gated: monitor-groups)
ToolPurpose
create-monitor-groupCreate a group and assign monitors to it
update-monitor-groupRename an existing group
delete-monitor-groupDelete a group; its monitors move to another group or none
get-monitor-groupFetch a single group by ID
list-monitor-groupsPaginated list of groups
Status pages (PSPs)
ToolPurpose
create-pspCreate a status page from monitors, groups, or tags (always created public; pause with update-psp)
update-pspChange name, domain, sort order, visibility, publish status, or monitors (monitor lists replace the whole list)
get-pspFetch a single status page by ID
list-pspsPaginated list of status pages
delete-pspPermanently delete a status page
PSP announcements (plan-gated: psp-subscribers)
ToolPurpose
create-psp-announcementPost an announcement (info/maintenance/issue) to a status page
update-psp-announcementEdit title, content, dates, type, or publish status
pin-psp-announcementPin an announcement to the top of the page
unpin-psp-announcementUnpin an announcement
get-psp-announcementFetch a single announcement by ID
list-psp-announcementsPaginated list of announcements for a status page
delete-psp-announcementPermanently delete an announcement
Maintenance windows (plan-gated: maintenance-window)
ToolPurpose
create-maintenance-windowSchedule a one-off or recurring window that suppresses alerts
update-maintenance-windowChange schedule, duration, monitors, or pause/resume the window
get-maintenance-windowFetch a single window by ID
list-maintenance-windowsPaginated list of windows
delete-maintenance-windowPermanently delete a window
Incidents
ToolPurpose
list-incidentsIncidents across monitors, with time range, monitor, or open-only filter
get-incident-detailsPer-incident request logs and cause
get-incident-activity-logIncident timeline summary plus paginated entries
get-incident-alertsAlerts sent during an incident, with delivery summary
Incident comments (plan-gated: incident-comments)

| Tool | Purpose

只显示了开头部分;其余内容请在仓库中阅读

问 PopNx