Skip to main content
Glama
Sign In
endpoint-aiops-mcp

endpoint-aiops-mcp

by AIops-tools
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to endpoint-aiops-mcp

No user-submitted related servers found.

    Related Servers

    • fabric-aiops

      AIops-tools
      A
      license
      A
      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

    • io.github.AIops-tools/ceph

      AIops-tools
      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

    • aiops-mcp

      rmednitzer
      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

    • OT-AIops Energy

      industrial-aiops
      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
      70 PyPI
      2
      MIT

    • gov-mcp

      OLG-MAN
      F
      license
      Not graded
      quality
      C
      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.
      -
    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/5.0

    Scored across 13 tools

    Disambiguation3/5

    Most tools are distinct, but there is meaningful overlap in the fleet-analysis cluster: patch_compliance is explicitly a reframe of patch_status, drift_report and endpoint_health_score both fold the same baseline-derived signals, and overview overlaps with the list/health tools. The descriptions do a good job explaining the boundaries and relationships, which keeps agents from misselecting, but several tools answer very similar 'how is the fleet doing' questions.

    Naming Consistency4/5

    Naming is consistently snake_case and resource-prefixed (endpoint_*, patch_*, session_*, undo_*, drift_report), giving a readable, predictable pattern. Minor deviations exist where action verbs and noun descriptors are mixed (endpoint_health_score, login_storm_analysis) and the bare 'overview' breaks the prefix convention, but overall it is coherent.

    Tool Count5/5

    13 tools is well within the ideal range and each earns its place across triage, analysis, write, and undo categories. The surface is neither thin nor bloated for a fleet-management/aiops server.

    Completeness4/5

    The set covers read/analysis (inventory, drift, patch, health, sessions), write actions (assign profile, reboot), and a governed undo lifecycle, which is solid lifecycle coverage. Gaps remain: no profile inventory/listing tool, and no direct patch-remediation action despite heavy patch analysis, but agents can work around these.

    Maintenance

    ActivityNo data
    ResponsivenessSyncing

    Resources