Skip to main content
Glama
shenwell

stillonline-mcp

by shenwell
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to stillonline-mcp

No user-submitted related servers found.

    Related Servers

    • exit1-mcp

      Mopra
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for Exit1 uptime monitoring. Enables AI assistants to create and manage uptime checks, configure alerts, and query status via natural language.
      32 npm
      MIT

    • mcp-uptime-kuma

      DavidFuchs
      A
      license
      A
      quality
      A
      maintenance
      MCP server for Uptime Kuma that enables monitoring and management of uptime monitors, heartbeats, notifications, tags, and maintenance windows via natural language.
      31
      709 npm
      48
      MIT

    • @mnicole-dev/updown-mcp-server

      mnicole-dev
      A
      license
      A
      quality
      D
      maintenance
      An MCP server for Updown.io that enables managing website monitoring checks, viewing downtimes and metrics, configuring alert recipients, and controlling status pages through natural language.
      15
      7 npm
      MIT
    • @pipeworx/statuspage by pipeworx-io

      @pipeworx/statuspageofficial

      pipeworx-io
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that answers service status and uptime questions by reading Atlassian Statuspage feeds from hundreds of vendors, with keyless access and tools for checking status, incidents, and vendor listings.
      2 npm
      MIT
    • uptrack-mcp by Uptrack-App

      uptrack-mcpofficial

      Uptrack-App
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for Uptrack uptime monitoring. Manage monitors and incidents from AI agents like Claude, ChatGPT, and Cursor.
      12 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.4/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool targets a distinct resource (checks, incidents, projects, status) and action (create, delete, list, update, get), with no overlap. Descriptions clearly differentiate purposes.

    Naming Consistency5/5

    All tools follow a uniform object.action naming pattern (e.g., checks.create, incidents.get). No mixing of conventions.

    Tool Count5/5

    10 tools is well-scoped for a monitoring server, covering the main operations without being overwhelming or too sparse.

    Completeness4/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources