StillOnline

It requires STILLONLINE_API_KEY and STILLONLINE_API_BASE. The API key is sensitive; if exposed via logs, config files, or downstream tooling, it could be used to access the StillOnline API. The provided material does not describe any additional credential protection mechanism.

Based on the name, description, and STILLONLINE_API_BASE, the tool is expected to send network requests to a StillOnline-related REST API and may transmit user status/check queries. The material does not disclose a default remote host, so egress transparency is limited, but there is no evidence of exfiltration to unrelated or suspicious endpoints.

The system flags it as executes-code, meaning it runs as a local MCP tool process. This is a normal capability for this class of tool; the available material does not show requests for unusual system privileges or high-risk actions unrelated to status pages and checks.

The available material only indicates an API integration for uptime, status pages, and checks, with no stated need to read or write local files, databases, or broad system resources. Based on the known facts, there is no clear sign of excessive data access.

It is listed in an official registry and has an open-source repository with updates within the last year, which are positive risk-reducing signals. On the other hand, the lack of a README, no declared license, and 0 stars limit auditability and ecosystem maturity, so the source code and dependencies should be reviewed before adoption.