Skip to main content
Glama
mnicole-dev

@mnicole-dev/updown-mcp-server

by mnicole-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to @mnicole-dev/updown-mcp-server

No user-submitted related servers found.

    Related Servers

    • stillonline-mcp

      shenwell
      A
      license
      A
      quality
      D
      maintenance
      MCP server for StillOnline uptime monitoring, enabling management of projects, checks, incidents, and public status pages through natural language.
      10
      23 npm
      1
      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
      1,129 npm
      49
      MIT

    • 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

    • IsItDown MCP Server

      hesreallyhim
      A
      license
      B
      quality
      D
      maintenance
      An MCP server that allows users to check if a website is experiencing downtime by querying isitdownrightnow.com, providing status information and details about recent downtime events.
      1
      2
      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.
      5 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

    A3.6/5.0

    Scored across 15 tools

    Disambiguation5/5

    Each tool clearly targets a distinct resource and action: checks, nodes, recipients, and status pages each have their own list/get/create/update/delete where applicable, with no overlapping purposes. The specialized check metrics and downtimes tools are unambiguous subsets of check data.

    Naming Consistency5/5

    All tool names follow a consistent kebab-case verb-noun pattern (e.g., list-checks, create-status-page). The pattern is predictable across all resources, with compound names like get-check-downtimes extending the same convention.

    Tool Count5/5

    15 tools is within the well-scoped 3-15 range for a domain-specific server. Each tool maps to a real operation on the Updown.io API, and the count feels right for covering the main resources without unnecessary bloat.

    Completeness4/5

    Checks and status pages have full CRUD coverage, plus additional check-specific operations. Recipients lack an update operation, but since recipients are likely simple contact addresses, create/delete/list may be sufficient. Overall the surface covers the core domain well with only minor gaps.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources