GitHub
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
电脑或云端
Staygreen
概览
作者提供的说明（英文原文）
Uptime monitoring and status pages for apps built with coding agents: status, incidents, setup.
PopNx MCP 的三大支柱
这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。
- 用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
- 我们的基础检查i3 项中通过 3 项依据公开信息检查；尚未扫描代码
- 使用情况i非常新↓ 154/周 · ★ –
它能帮你做什么
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
- 连接方式: 电脑或云端
- 传输方式: stdio, Streamable HTTP
- 分类: 开发者工具
- 你需要填写：STAYGREEN_API_TOKEN
安装
选择你使用的 AI 应用，然后复制设置。
安装之前
- 基础检查：3 项中通过 3 项
- 在作者的服务器上运行：你向它提出的内容会经过他们的服务器。
- 需要你自己填写：
STAYGREEN_API_TOKEN
标为机密的值是你账户的钥匙。千万不要分享给别人，也不要粘贴到聊天里。
你需要
你用的是哪个应用？
在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。
适用于网页版、桌面版和手机版 Claude：
- 打开 Settings → Connectors
- 点击 Add custom connector
- 粘贴下面的地址，然后点击 Add
- 如果要求登录，请登录作者的服务
https://staygreen.io/mcp或者在你的电脑上运行
打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"staygreen": {
"command": "npx",
"args": [
"-y",
"staygreen",
"mcp"
],
"env": {
"STAYGREEN_API_TOKEN": "your-value"
}
}
}
}在终端中运行这条命令
claude mcp add --transport http staygreen https://staygreen.io/mcp或者在你的电脑上运行
claude mcp add staygreen --env STAYGREEN_API_TOKEN=your-value -- npx -y staygreen mcp运行前请先填写空着的值。
或者自己复制设置
粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json
{
"mcpServers": {
"staygreen": {
"url": "https://staygreen.io/mcp"
}
}
}或者在你的电脑上运行
或者自己复制设置
粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json
{
"mcpServers": {
"staygreen": {
"command": "npx",
"args": [
"-y",
"staygreen",
"mcp"
],
"env": {
"STAYGREEN_API_TOKEN": "your-value"
}
}
}
}浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。
或者自己复制设置
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"staygreen": {
"type": "http",
"url": "https://staygreen.io/mcp"
}
}
}或者在你的电脑上运行
或者自己复制设置
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"staygreen": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"staygreen",
"mcp"
],
"env": {
"STAYGREEN_API_TOKEN": "your-value"
}
}
}
}浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。
ChatGPT 只能连接互联网上的服务器：
- 打开网页版 ChatGPT → Settings → Connectors (Apps)
- 点击 Create 或 Add（部分套餐需要先在 Advanced 中开启 Developer mode）
- 粘贴下面的地址，起个名字，然后保存
- 如果要求登录，请登录作者的服务
https://staygreen.io/mcp菜单名称可能因套餐和版本不同而略有差异。
你的选择通过 Cookie 保存在这台设备上，无需账户。
需要你填写的值
- Staygreen workspace API token (dashboard: Agents and API), read-only or read-and-write. Without it only scan_app works.
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。
它能做什么
服务器要求先登录，才会列出它的工具。
基础检查i
我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月9日
- ✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 phuryn 验证，该账户拥有此仓库
- … 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
- … 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
- ✓ 通过
端点有响应
在 477 毫秒内响应（HTTP 401）
- ✓ 通过
使用 OAuth 登录
声明支持 OAuth 登录，你的 AI 应用可以带你去登录
- … 尚未检查
工具描述中没有隐藏指令
尚未检查；我们会在检查端点时读取工具列表
与“开发者工具”中的其他服务器比较i
- 星标数多于此分类中其他 5581 个服务器的 0%
- 发布到注册中心的时间比此分类中其他 5581 个服务器的 66% 更新
- 基础检查结果等于或优于此分类中其他 5581 个服务器的 100%
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。
常见问题
Staygreen 安全吗？
它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。
它需要哪些密钥或代码？
你需要填写：STAYGREEN_API_TOKEN
它在我的电脑上运行还是在云端？
两种方式都可以：安装在你的电脑上，或者连接云端版本。
它还在维护吗？
GitHub 仓库最后更新于–，最新版本（1.1.4）于13天前进入注册中心。
哪些应用可以使用它？
支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接，所以接受远程 MCP 服务器的应用也可以使用，例如开启开发者模式的 ChatGPT。
有什么可以替代它？
同一分类中有：GitHub, Desktop Commander, Cloudflare MCP
替代选择
同一分类中其他作者的服务器，按星标数排序。
如何看卡片：↓ 每周下载量i★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Desktop Commander
MCP server for terminal commands, file operations, and process management
在你的电脑上运行
作者的 README
打开 README
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Staygreen
Uptime and incident monitoring for apps built with coding agents: checks from more than one location, incidents with the evidence attached, and a public status page for each app. Free plan at staygreen.io.
This repository holds Staygreen's source under the Functional Source License, Version 1.1, MIT Future License (FSL-1.1-MIT): the dashboard, the probes, the status edge, the Workers, the widget and the agent API, with the staygreen command-line package in packages/staygreen/. You may use, change and redistribute it for any purpose except offering a competing commercial product or service, and each version becomes MIT two years after it is published. It is also Staygreen's public issue tracker.
It is a reviewed, one-way copy of the private working repository, refreshed after each release. Staygreen is not accepting pull requests or outside contributions at the moment; issues are welcome through the templates, and security problems go to private vulnerability reporting.
Connect an agent (MCP)
Staygreen's MCP server is at https://staygreen.io/mcp (streamable HTTP). Every call requires sign-in; there is no anonymous tool.
Sign in: no token to handle
Add https://staygreen.io/mcp to an MCP client that supports signing in (OAuth), then sign in with your Staygreen account and choose the workspace. If you don't have an account yet, signing up there creates a Free workspace; you don't need to open the dashboard first. The connection can read and change that workspace's monitors, and you must be an administrator of it.
Claude Code:
claude mcp add --transport http staygreen https://staygreen.io/mcpThen run /mcp, choose staygreen and Authenticate. In Claude, add it as a custom connector with the same URL.
With an API token (CI and scripts)
An administrator creates a token in the dashboard under Agents and API: read-only or read-and-write, shown once. Send it as Authorization: Bearer . The same token works on the MCP server and on the REST API (https://staygreen.io/api/v1/ ).
claude mcp add --transport http staygreen https://staygreen.io/mcp \--header "Authorization: Bearer $STAYGREEN_API_TOKEN"
Local server (npm)
The staygreen package runs the same tools as a local stdio server and calls the REST API with a workspace API token. Node 22 or later.
claude mcp add staygreen -e STAYGREEN_API_TOKEN=… -- npx -y staygreen mcpWithout a token only scan_app works. Configuration for Claude Desktop, Cursor and VS Code, and the package's scan and provision commands, are in CLI.md.
Tools
| Tool | What it does |
|---|---|
get_status | Current status of one app or every app: monitors, page components and open incidents |
list_monitors | Monitors in your workspace, filtered by app, type or state, with each one's last check |
get_uptime | Measured uptime, downtime minutes, incident counts and daily history. Unmeasured time is no data, not 100% |
get_response_times | Response-time series for a monitor, by city and country |
get_incidents | Incident evidence and timelines: failing assertions, locations and masked snippets |
get_ssl_and_domain_expiry | Certificate and domain expiry dates for monitored hosts |
scan_app | A one-time scan of a public app URL. Optional keys are used once and never stored. Creates nothing |
provision_app | Sets up an app's website check, SSL and domain check, status page and cron heartbeats in one call |
create_monitor | Adds one monitor to an app, with the dashboard's own checks and plan limits |
pause | Pauses one monitor or one app's monitors for up to 24 hours, then resumes them |
draft_incident_update | Saves an incident note as a draft. It appears publicly only once you publish it in the dashboard |
Writes take a request_id UUID: repeat it with the same inputs to retry safely. Deleting, alert channels, teammates, billing and publishing are not available to agents. Calls share your workspace's budget: 30 a minute on Free, 120 on Builder.
Report a bug or suggest a feature
Open an issue. Say what you did, what you expected, and what happened instead; the monitor type and the screen help.
Issues are public. Never paste a secret, service-role or restricted key, a token, a webhook or heartbeat URL, a signing secret or a header value, whether Staygreen issued it or another service did. If you posted one, treat it as leaked: make sure the old value stops working wherever it is accepted, because issuing a new one doesn't always retire it; see staygreen.io/support if you're not sure how.
For a security problem, don't open an issue: use private vulnerability reporting instead. For anything else private, see staygreen.io/support.
Run it yourself
Staygreen is several services, not a one-click app, but a coding agent with your providers' API tokens can do most of an installation. You may run a copy for your own organizations; the license rules out offering it to others as a competing commercial product or service.
| Layout | What runs where | Good for |
|---|---|---|
| Recommended | The dashboard on Netlify, the database on Supabase, sign-in on Clerk, two probe VMs in different regions (one also runs the status edge), and three Cloudflare Workers for heartbeats, alerts and the watchdog | Monitoring you rely on: an HTTP, TCP or service check that fails is confirmed from a second location before an incident opens |
| Smallest | One VM running the dashboard, one probe and the status edge, with Supabase, Clerk and the three Workers as above | Trying it, or watching a few apps where an occasional false alarm is acceptable |
- Deploying: what you need, suggested resources and their monthly cost, the smallest installation, setting it up with an agent, and the setup order.
- Sample configurations: the probe's and the status edge's service units, variables and Caddyfile, and the alert sender's and watchdog's Wrangler configurations.
- The environment reference and the architecture.
The product is at the repository root; the standalone npm package is in packages/staygreen/. Root server.json and glama.json retain the hosted MCP and npm listing identities.
Development
Use Node 22 or later. From the root run npm ci, npm run typecheck, and npm run test:unit. The unit tests use fakes and require neither database access nor credentials. Run npm ci, npm run typecheck, npm run build, and npm test inside packages/staygreen/ for the standalone CLI.
The export check skips integration tests (Postgres and Supabase credentials), browser tests (a configured app, Playwright browsers, and Clerk development accounts), live network tests, and go-live acceptance. Private operator/export tests do not ship; their omitted paths are recorded in deploying. A passing offline check does not verify a deployment or sign-in.
For the app, create your own local .env from .env.example, fill the required app variables, then run npm run dev. npm run build also validates configuration; the offline export check runs TypeScript and unit tests, not an unconfigured Next production build. Review the legal pages, branding, service URLs and plan copy before serving your own deployment.
The opt-in tests/unit/rdap-live.test.ts network cases are skipped in offline unit runs. The package symlink test can also skip on Windows when symlink creation is unavailable.