stillonline-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| STILLONLINE_API_KEY | Yes | Your StillOnline API key (sk_live_...) from Settings → API | |
| STILLONLINE_API_BASE | No | Base URL for StillOnline API (default https://api.stillonline.tech/v1) | https://api.stillonline.tech/v1 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| projects.listA | 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. |
| projects.createA | 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. |
| projects.deleteA | Soft-delete a StillOnline project. Removes it from the dashboard and disables checks, matching the UI delete behavior. |
| checks.listA | List HTTP and SSL checks for a StillOnline project. Use this before updating, pausing, deleting, or auditing monitor coverage. |
| checks.createA | 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. |
| checks.updateA | Update a StillOnline check. Use this to pause or resume monitoring, rename a check, or change its probe interval after deploy or infrastructure changes. |
| checks.deleteA | Permanently delete a StillOnline check. Use only when an endpoint should no longer be monitored. |
| status.getA | Get public StillOnline status JSON by status page slug. Use this to inspect customer-facing uptime without exposing private account data. |
| incidents.createA | Open an incident on a StillOnline status page. Use this when an outage or degraded service should be visible to subscribers and stakeholders. |
| incidents.getA | Get a StillOnline incident by ID. Despite the historical name, this returns one incident record for follow-up status updates or review. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| deploy.monitor | Guide an agent through adding or checking StillOnline monitors after a deploy. |
| incidents.respond | Guide an agent through checking uptime data and opening an incident when production is down. |
| agents.healthCheck | Guide an agent through monitoring an autonomous AI agent or MCP backend health endpoint. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| StillOnline MCP docs | Installation and setup guide for stillonline-mcp in Cursor, Claude Code, Windsurf, Codex, Antigravity, and other MCP clients. |
| StillOnline REST API docs | REST API v1 reference for projects, checks, public status, and incidents used by the MCP server. |
| Demo status page | Public StillOnline demo status page for evaluating customer-facing uptime output. |
TDQS
Scored across 10 tools
Each tool targets a distinct resource (checks, incidents, projects, status) and action (create, delete, list, update, get), with no overlap. Descriptions clearly differentiate purposes.
All tools follow a uniform object.action naming pattern (e.g., checks.create, incidents.get). No mixing of conventions.
10 tools is well-scoped for a monitoring server, covering the main operations without being overwhelming or too sparse.
CRUD is covered for checks and projects, but incidents only have create and get (missing update/delete). Minor gaps exist but core workflows are supported.