GitHub
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
作者提供的说明(英文原文)
Uptime monitoring from your assistant: see what's down, run incidents, set up monitors and reports.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
适用于网页版、桌面版和手机版 Claude:
https://mcp.upti.my/mcp在终端中运行这条命令
claude mcp add --transport http upti https://mcp.upti.my/mcp粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"upti": {
"url": "https://mcp.upti.my/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"upti": {
"type": "http",
"url": "https://mcp.upti.my/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
ChatGPT 只能连接互联网上的服务器:
https://mcp.upti.my/mcp菜单名称可能因套餐和版本不同而略有差异。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
服务器要求先登录,才会列出它的工具。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过域名 upti.my 验证(注册中心会核实域名所有权)
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
在 417 毫秒内响应(HTTP 401)
声明支持 OAuth 登录,你的 AI 应用可以带你去登录
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于–,最新版本(1.0.0)于前天进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有:GitHub, Desktop Commander, Cloudflare MCP
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
MCP server for terminal commands, file operations, and process management
Cloudflare MCP servers
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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.
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:
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.
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:
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:
{
"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_..." }.
24 tools: 10 that read and 14 that change something.
| Read | What it does |
|---|---|
get_status_overview | Every monitor, cron job monitor, open incident, status page and followed third-party service, problems first |
get_monitor | One monitor's target, schedule, regions and current status |
get_monitor_metrics | Uptime and latency over a time range, per region, with the latest failed checks and their errors |
list_incidents, get_incident | Recent incidents, and one incident with its timeline |
get_dependencies | The third-party services Uptimy measures, their status, and which ones you follow |
list_reports, get_uptime_report | Your uptime reports, and availability against the SLA target for any period |
list_alerts | Who hears about incidents: every alert, where it sends and whether it's paused |
suggest_monitors | Scans a domain you name for what's worth monitoring (the scan the app's Setup runs); adds nothing |
| Change | What it does |
|---|---|
create_incident, post_incident_update | Open an incident; post timeline updates, change its status and publish it to status pages |
schedule_maintenance | Schedule a maintenance window, optionally announced on status pages |
set_monitor_paused, trigger_check | Pause or resume a monitor; run a check right away to confirm a fix |
follow_dependency | Follow or unfollow a third-party service, so its outages open incidents in your workspace |
add_monitors, add_cron_monitor | Add website, API, certificate, port, ping, DNS and MCP server checks; watch a cron job with a heartbeat |
create_status_page, add_to_status_page | Create a status page (private unless you ask); show more monitors on one |
add_alert, set_alert_paused | Send incidents to Slack, Discord, Teams, Telegram, PagerDuty, email or a webhook; pause or resume an alert |
add_report, update_report | Add 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.
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.
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).
Apache-2.0