Staygreen
io.github.phuryn/staygreen
About Staygreen
Staygreen is an MCP server published by the GitHub account phuryn. Uptime monitoring and status pages for apps built with coding agents: status, incidents, setup.
It runs on your own machine: your AI client starts it from the npm package staygreen at version 0.1.3, or you can connect to the hosted version instead.
It asks for one secret: STAYGREEN_API_TOKEN. Give it a key with the least access that still works.
Version 1.1.4 was published on 26 October 2026, and the source code is public, so you can read it before installing.
Written from the registry entry. 10 automated checks on the registry entry and the package code: 8 pass, 0 warn, 0 fail, 2 info. How we check.
What it asks for
| Variable | Required | Secret | Description |
|---|---|---|---|
STAYGREEN_API_TOKEN | Yes | Yes | Staygreen workspace API token (dashboard: Agents and API), read-only or read-and-write. Without it only scan_app works. |
Checks
| Check | Result | Detail |
|---|---|---|
| Source repository linked | Pass | https://github.com/phuryn/staygreen |
| Version pinned | Pass | Every package has an explicit version |
| Remote uses HTTPS | Pass | All remote endpoints use https:// |
| Secrets requested | Info | Asks for 1 secret: STAYGREEN_API_TOKEN |
| Known package registry | Pass | All packages come from npm, PyPI, OCI, NuGet or MCPB |
| Namespace ownership | Info | Name verified via GitHub account phuryn |
| Registry text aimed at the AI | Pass | Description and settings contain no hidden characters or instructions to the AI |
| Install scripts | Pass | staygreen@0.1.3 runs nothing at install |
| Code red flags | Pass | Read 4 files in staygreen@0.1.3: no obfuscation, encoded execution, credential reads or data-collection endpoints found |
| Text aimed at the AI | Pass | No hidden characters or instructions to the AI in 4 files, including comments and the README |
Popularity & health: 68 / 100
Worked out from public numbers and our own checks, not from user reviews or ratings. It says how used and how looked-after a server is, not whether it is safe.
2 forks, 0 merged pull requests. Sources: GitHub, npm, PyPI (pypistats.org) and Hacker News (Algolia), fetched 2026-10-31.
What people say
No Hacker News threads link to its source code.
Look further: search Reddit, search Hacker News, read its GitHub issues. These are not reviews we checked.
Facts
| Registry name | io.github.phuryn/staygreen |
|---|---|
| Publisher | GitHub account phuryn |
| How the name is verified | Name verified via GitHub account phuryn. The registry ties the name prefix to that account or domain; it does not check the code. |
| Type | Local package and a hosted remote |
| Packages | npm staygreen 0.1.3 (stdio) |
| Remote endpoints | streamable-http https://staygreen.io/mcp |
| Version | 1.1.4 |
| Published | |
| Last updated | |
| Source repository | https://github.com/phuryn/staygreen |
| Website | https://staygreen.io |
| Category | Analytics & monitoring (assigned by keyword rule, not by hand) |
Related servers in Analytics & monitoring
- SolidPing3/3Self-hostable uptime monitoring: create checks, read incidents,…
- SutramX7/7SutramX uptime monitoring: monitors, check results, incidents,…
Fettle8/8Uptime monitoring — monitors, incidents, heartbeats, maintenance…- mcp3/3Manage uptime monitors, incidents and status pages from any MCP…
- hyperping4/4Uptime, API and server monitoring with outages, reporting, on-call…
HostTracker3/3Website uptime monitoring: run checks from 300+ locations, manage…