Skip to main content
Glama
openstack-incidents

openstack-incidents

Related Servers

Alternatives to openstack-incidents

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables read-only Kubernetes incident investigation through MCP tools for listing pods, describing resources, fetching logs, and searching runbooks.
      1
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides MCP-compatible safe read tools for incident investigation, enabling evidence collection and operational data access while keeping risky actions under human approval.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI clients to perform safe, read-only IT diagnostics and retrieve local runbooks, asset records, and knowledge articles through MCP, with allowlisted network checks and audit logging.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables investigation of devices, model breaches and analyst incidents from an MCP host through a bounded set of read-only tools, with operator-controlled profiles and a fixed operation inventory. Writes, PCAP export, email and HTTP transport are excluded, and responses are minimized and escaped before entering model context.
      16 npm
      3
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables evidence-first incident command: investigate outages, analyze evidence, approve simulated responses, verify recovery, and export postmortems through MCP tools.
      MIT

    TDQS

    B3.1/5.0

    Scored across 7 tools

    Disambiguation4/5

    Most tools target distinct resources/actions (validate_evidence, save_ticket_draft, search_logs, search_runbooks, get_timeline), but the read-side tools get_instance_summary, get_timeline, search_logs, and get_case_memory all return signals/context for the same instance/request pair and could be confused without careful reading. The descriptions disambiguate well enough (e.g. timeline = opening/terminal events, case memory = approved drafts).

    Naming Consistency5/5

    All names follow a consistent snake_case verb_noun pattern (get_*, search_*, validate_*, save_*), so the operation type is predictable at a glance. No mixed conventions or vague verbs.

    Tool Count5/5

    Seven tools is well-scoped for an incident investigation workflow, covering read/evidence/draft concerns without redundancy. Each tool earns its place.

    Completeness4/5

    The surface covers the core investigation lifecycle: gather signals, timeline, logs, runbooks, validate evidence, persist a draft, and recall prior drafts. Minor gaps exist (no tool to fetch/close the ticket itself or delete/update drafts), but agents can work around them.