endpoint-aiops-mcp
Related Servers
Alternatives to endpoint-aiops-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceAI Governance and SecOps platform for remote servers1-
- AlicenseAqualityAmaintenanceGoverned 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.34MIT
- AlicenseAqualityAmaintenanceGoverned 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.37MIT
- AlicenseAqualityBmaintenanceA 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.5Apache 2.0
- AlicenseAqualityAmaintenanceGoverned, 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.591MIT
- FlicenseNot gradedqualityBmaintenanceDiscovers 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
Scored across 13 tools
patch_status and patch_compliance both evaluate patch levels against a target, and overview, endpoint_health_score, and drift_report all present fleet-health summaries, so an agent could pick the wrong one. The descriptions do separate raw distribution from SLA verdict and live triage from injected analysis, but the boundaries are not always crisp.
Most tools use a lowercase resource-prefixed pattern like endpoint_list, endpoint_get, and undo_apply, but verbs and nouns are mixed: overview, patch_status, login_storm_analysis, and drift_report are not action-oriented. The names are readable and grouped by domain, but the convention is not uniform.
At 13 tools, the set is well within the ideal range and covers inventory, health, patch analysis, session analysis, drift, writes, and undo. Each tool maps to a distinct operational need for an endpoint AIOps workflow, with no obvious bloat.
The server covers the main AIOps loop: inventory, health, patch compliance, login storms, drift, and reversible actions. Missing profile management and broader endpoint lifecycle operations are minor workarounds rather than dead ends.