Skip to main content
Glama
AIops-tools

endpoint-aiops-mcp

Related Servers

Alternatives to endpoint-aiops-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      A
      maintenance
      Governed network controller-layer operations (Cisco Meraki, plus Catalyst Center / Arista CVP / UniFi) — uplink loss/latency RCA, fleet health scoring, and config-template drift, with unbypassable audit logging (MCP + CLI), budget/runaway guards, and rollback.
      37
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Governed AI-ops for Ceph, providing root-cause health analysis and guarded destructive operations via a built-in governance harness with risk tiers, audit, and undo recording.
      37
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      A self-contained, security-first, EU-sovereign unified AI-operations MCP server that fuses a live bitemporal fleet model, a drift engine, and a tiered audited actuator into one control plane.
      5
      Apache 2.0
    • A
      license
      A
      quality
      A
      maintenance
      Governed, read-only OT data tap for substation and utility telecontrol — IEC 60870-5-104, DNP3/IEEE 1815, and IEC 61850 MMS connectors with cross-protocol asset discovery, alarm and downtime RCA, unbypassable audit logging (MCP + CLI), budget/runaway guards, and an airgap no-egress mode. Energy edition of Industrial-AIOps, built on iaiops.core.
      59
      1
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Discovers AI workloads on GCP using behavioral signals and runs deterministic governance checks, producing hashed evidence for EU AI Act and SOC 2 compliance audits.
      -

    TDQS

    A4.1/5.0

    Scored across 13 tools

    Disambiguation4/5

    Most tools are clearly distinct (endpoint_list vs endpoint_get vs endpoint_health_score). Patch-related tools (patch_status, patch_compliance, drift_report, endpoint_health_score) overlap in patch-level analysis, but each has a distinct framing (distribution, SLA, drift, health) and descriptions clarify the differences.

    Naming Consistency4/5

    Uses snake_case throughout with a consistent noun_verb pattern for most tools (endpoint_list, session_list, patch_status, login_storm_analysis). A few deviations like 'overview' (noun only) and 'undo_apply' (verb_noun) are minor and do not impede readability.

    Tool Count5/5

    13 tools is well within the typical 3-15 range and each tool serves a clear purpose in the endpoint-management/aiops domain. No redundant or superfluous tools; the count feels right for the scope.

    Completeness4/5

    Covers core monitoring (health, patch, drift, sessions) and common actions (assign profile, reboot) with undo support. Missing operations like endpoint create/delete or a direct patch-apply tool, but these may be out of scope for a monitoring/aiops server; the surface is largely complete for its stated purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues