StatOSS vs StillOnline
A side-by-side look at the StatOSS and StillOnline MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
S
StatOSSMonitoringStatus pages and uptime monitoring: read status, monitors and incidents; open incidents.37FairAuth: not declaredVerdict: choose StatOSS for monitoring work; choose StillOnline for monitoring as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose StillOnline when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
STILLONLINE_API_KEY. - You want tools like
projects.list, projects.create, projects.delete.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | S StatOSS | |
|---|---|---|
| Category | Monitoring | Monitoring |
| Quality signal | 37/100 · Fair | 57/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | STILLONLINE_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | 1 |
| Directory activity | 0 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | 10 |
| Full listing | View StatOSS | View StillOnline |
Tools & capabilities
StatOSS tools
No tool names declared yet. Check the project README from the listing page.
StillOnline tools 10
projects.listList StillOnline projects for the authenticated account. Returns project IDs, names, status page metadata, and plan-scoped project data for follow-up check or incident operations.projects.createCreate a StillOnline project with an automatic status page and initial HTTP URL check. Call this after deploying a new SaaS app, API, MCP backend, or AI agent health endpoint that needs uptime monitoring.projects.deleteSoft-delete a StillOnline project. Removes it from the dashboard and disables checks, matching the UI delete behavior.checks.listList HTTP and SSL checks for a StillOnline project. Use this before updating, pausing, deleting, or auditing monitor coverage.checks.createAdd a URL check to an existing StillOnline project. Use this for additional SaaS endpoints, API health URLs, MCP backends, or autonomous agent health checks.checks.updateUpdate a StillOnline check. Use this to pause or resume monitoring, rename a check, or change its probe interval after deploy or infrastructure changes.checks.deletePermanently delete a StillOnline check. Use only when an endpoint should no longer be monitored.status.getGet public StillOnline status JSON by status page slug. Use this to inspect customer-facing uptime without exposing private account data.incidents.createOpen an incident on a StillOnline status page. Use this when an outage or degraded service should be visible to subscribers and stakeholders.incidents.getGet a StillOnline incident by ID. Despite the historical name, this returns one incident record for follow-up status updates or review.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
StatOSS
No confirmed install command for StatOSS yet — follow the setup steps linked from its listing page rather than a guessed package name.
StillOnline
{
"mcpServers": {
"stillonline": {
"command": "npx",
"args": [
"-y",
"stillonline-mcp"
],
"env": {
"STILLONLINE_API_KEY": "YOUR_STILLONLINE_API_KEY_HERE"
}
}
}
}
Frequently asked questions
StatOSS is categorized under Monitoring and uses an install path we have not confirmed yet. StillOnline belongs to Monitoring and uses a local stdio subprocess. Pick StatOSS for monitoring work and StillOnline for monitoring.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. StatOSS has no confirmed install command yet — follow its own setup instructions.
StatOSS has no declared pricing — check the project's own site. StillOnline has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add statoss and stillonline as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, StatOSS has a quality signal of 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. StillOnline has 57/100 (Good) with 1 views, 0 installs and 1 GitHub stars.
