Skip to main content
Glama
phuryn

Staygreen MCP Server

by phuryn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Staygreen MCP Server

No user-submitted related servers found.

    Related Servers

    • StackWitness by stackwitness

      StackWitnessofficial

      stackwitness
      F
      license
      Not graded
      quality
      D
      maintenance
      Let agents read and manage your org’s independent monitors, incidents, status pages, and alerts (honest measured state, no false greens).
      -

    • Nibble

      Talia04
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to investigate production incidents by exposing service health, logs, and deployment data through MCP tools.
      6 npm
      ISC

    • Vigilo

      temmeik
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients such as Claude to check current uptime status, inspect monitors and incidents, trigger fresh checks, and retrieve status summaries from a self-hosted monitoring service.
      2 npm
      2
      MIT

    • ai-sre

      lhermawan
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to query system health, metrics, service reconnaissance, run multi-node patrols, and send incident alerts across distributed infrastructure through MCP tools.
      ISC

    • Datadog MCP Server

      gfg-dat-le-vn
      A
      license
      B
      quality
      D
      maintenance
      Enables interaction with Datadog's monitoring and observability platform through the MCP protocol. Supports incident management, monitor status checks, log searches, metrics queries, APM traces, dashboard access, RUM analytics, host management, and downtime scheduling.
      13
      3 npm
      Apache 2.0
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A4.4/5.0

    Scored across 11 tools

    Disambiguation4/5

    The six read tools (get_status, list_monitors, get_uptime, get_response_times, get_incidents, get_ssl_and_domain_expiry) sit close together, but each description explicitly states its distinct metric and cross-references the alternatives ('Use get_uptime ... instead for latency'), which keeps selection reliable. The only real proximity risk is provision_app vs create_monitor, which is handled by an explicit 'for a new app use provision_app instead' rule.

    Naming Consistency4/5

    All snake_case with a mostly verb_noun pattern (get_incidents, list_monitors, create_monitor, provision_app, scan_app, draft_incident_update). Minor deviations: the bare verb 'pause' has no object, and draft_incident_update orders the noun before the action, but neither is confusing.

    Tool Count5/5

    Eleven tools is well within a comfortable range and each one covers a distinct facet: status, monitors, uptime, latency, incidents, expiry, creation, pausing, incident notes, and a one-off scan. No filler tools are apparent.

    Completeness3/5

    Read coverage is thorough and provisioning is solid, but the write surface is thin: no update_monitor or delete_monitor, no way to resume a paused monitor early, no app update/delete, and no incident publish (drafting only). Agents can work around some of this via the dashboard, but lifecycle coverage is notably incomplete.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources