Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

StillOnline

NPM · STILLONLINE-MCP · SCANNED SEP 21

StillOnline MCP: uptime, status pages, checks. REST API for Cursor and Claude Code.

Available components

0 this week 86 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 99 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability90
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 795 tokens (~61/item across 13 items; 10 tools + 3 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
  • Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the StillOnline MCP server?

StillOnline runs locally as an npm package, launched with npx -y stillonline-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · stillonline-mcp

# add to Claude Code
claude mcp add shenwell-stillonline -- npx -y stillonline-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "shenwell-stillonline": {
      "command": "npx",
      "args": [
        "-y",
        "stillonline-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "shenwell-stillonline": {
      "command": "npx",
      "args": [
        "-y",
        "stillonline-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add shenwell-stillonline -- npx -y stillonline-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "shenwell-stillonline": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "stillonline-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add shenwell-stillonline --command npx --arg -y --arg stillonline-mcp
# ~/.hermes/config.yaml
mcp_servers:
  shenwell-stillonline:
    command: "npx"
    args: ["-y", "stillonline-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "shenwell-stillonline": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "stillonline-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add shenwell-stillonline -t stdio -c npx -a -y stillonline-mcp
// mcp.json
{
  "mcpServers": {
    "shenwell-stillonline": {
      "command": "npx",
      "args": [
        "-y",
        "stillonline-mcp"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Sept 26 −3
    • Stability: pass → 0.83 functional
  • 16 Sept 26 +1
    • Stability: 0.97 → pass security
  • 14 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Sept 26 −4
    • Security disclosure: unverified → fail functional
    • Stability: pass → 0.77 functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Sept 2026 · Analysed npm/stillonline-mcp@0.3.6

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 99 packages
Packages resolved 99
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 10 exposed · ~710 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
checks.create ~118

Add a URL check to an existing StillOnline project. Use this for additional SaaS endpoints, API health URLs, MCP backends, or autonomous agent health checks.

NameTypeReqDescription
interval_secondsnumberOptional probe interval in seconds. Availability depends on the account plan.
namestringOptional check label shown in the dashboard and status context.
project_idstringyesStillOnline project ID that should receive the new check.
urlstringyesPublic URL to probe. Prefer HTTPS health endpoints that return 200 without authentication.
NameTypeReqDescription
checkobjectyesStillOnline check object, including identifiers, URL, enabled state, interval, and latest probe status fields returned by the REST API.

No examples provided.

checks.delete ~46

Permanently delete a StillOnline check. Use only when an endpoint should no longer be monitored.

NameTypeReqDescription
check_idstringyesStillOnline check ID returned by checks.list or checks.create.
NameTypeReqDescription
deletedbooleanyesWhether the check delete operation succeeded.

No examples provided.

checks.list ~51

List HTTP and SSL checks for a StillOnline project. Use this before updating, pausing, deleting, or auditing monitor coverage.

NameTypeReqDescription
project_idstringyesStillOnline project ID whose checks should be listed.
NameTypeReqDescription
checksarrayyesChecks configured for the requested StillOnline project.

No examples provided.

checks.update ~109

Update a StillOnline check. Use this to pause or resume monitoring, rename a check, or change its probe interval after deploy or infrastructure changes.

NameTypeReqDescription
check_idstringyesStillOnline check ID returned by checks.list or checks.create.
enabledbooleanSet true to resume monitoring or false to pause this check.
interval_secondsnumberOptional new probe interval in seconds. Availability depends on the account plan.
namestringOptional new display name for this check.
NameTypeReqDescription
checkobjectyesStillOnline check object, including identifiers, URL, enabled state, interval, and latest probe status fields returned by the REST API.

No examples provided.

incidents.create ~76

Open an incident on a StillOnline status page. Use this when an outage or degraded service should be visible to subscribers and stakeholders.

NameTypeReqDescription
status_page_idstringyesStillOnline status page ID associated with the affected project.
titlestringyesShort incident title, for example 'API latency elevated' or 'Agent gateway unavailable'.
NameTypeReqDescription
incidentobjectyesStillOnline incident object, including identifiers, title, status page relation, and current incident state fields returned by the REST API.

No examples provided.

incidents.get ~54

Get a StillOnline incident by ID. Despite the historical name, this returns one incident record for follow-up status updates or review.

NameTypeReqDescription
incident_idstringyesStillOnline incident ID returned by incidents.create or the incidents API.
NameTypeReqDescription
incidentobjectyesStillOnline incident object, including identifiers, title, status page relation, and current incident state fields returned by the REST API.

No examples provided.

projects.create ~111

Create 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.

NameTypeReqDescription
descriptionstringOptional short project description for dashboard context.
namestringyesHuman-readable project name shown in StillOnline and on the generated status page.
urlstringyesPublic HTTPS URL to monitor, usually an app URL, API health endpoint, or agent /health endpoint.
NameTypeReqDescription
projectobjectyesStillOnline project object, including identifiers, display name, status page metadata, and plan-scoped fields returned by the REST API.

No examples provided.

projects.delete ~49

Soft-delete a StillOnline project. Removes it from the dashboard and disables checks, matching the UI delete behavior.

NameTypeReqDescription
project_idstringyesStillOnline project ID returned by projects.list or projects.create.
NameTypeReqDescription
deletedbooleanyesWhether the project delete operation succeeded.
project_idstringID of the deleted StillOnline project.

No examples provided.

projects.list ~41

List 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.

Input schema present but exposes no named parameters.

NameTypeReqDescription
projectsarrayyesProjects available to the authenticated StillOnline account.

No examples provided.

status.get ~55

Get public StillOnline status JSON by status page slug. Use this to inspect customer-facing uptime without exposing private account data.

NameTypeReqDescription
slugstringyesPublic status page slug or ID from a StillOnline /s/{slug} URL.

Structured output declared, but exposes no named fields.

No examples provided.

Common questions

What is the StillOnline MCP server?

StillOnline is an MCP server listed in the public MCP registry as io.github.shenwell/stillonline. StillOnline MCP: uptime, status pages, checks. REST API for Cursor and Claude Code. This page covers its npm package (stillonline-mcp).

Is the StillOnline MCP server safe to use?

StillOnline scores 86 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the StillOnline MCP server expose?

StillOnline exposes 10 tools: projects.list, projects.create, projects.delete, checks.list, checks.create, and 5 more. Their descriptions and schemas cost roughly 710 tokens of context every time the server is loaded.

Is the StillOnline MCP server still maintained?

StillOnline is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the StillOnline MCP server under?

StillOnline declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.