container-host-aiops
Related Servers
Alternatives to container-host-aiops
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceGoverned CI/CD operations for self-hosted GitLab and Gitea — pipeline-failure, runner, artifact-bloat, and stale-branch RCA, with unbypassable audit logging (MCP + CLI), budget/runaway guards, dry-run, and undo/rollback.28MIT
- AlicenseBqualityAmaintenanceGoverned MinIO object-storage operations — capacity, exposure-surface audit, lifecycle, and healing RCA, with guarded bucket writes, unbypassable audit logging (MCP + CLI), budget/runaway guards, dry-run, and undo/rollback.48MIT
- AlicenseAqualityAmaintenanceGoverned reverse-proxy operations for Traefik, Caddy, and HAProxy — backend-health, cert-expiry, 5xx, and route-conflict RCA, with unbypassable audit logging (MCP + CLI), budget/runaway guards, dry-run, and undo/rollback.28MIT
- AlicenseBqualityAmaintenanceGoverned Prometheus + Grafana operations — firing-alert and scrape-target RCA, alert noise/flapping analysis, silences, and dashboards, with unbypassable audit logging (MCP + CLI), budget/runaway guards, dry-run, and undo/rollback.39MIT
- AlicenseAqualityAmaintenanceGoverned MySQL + MariaDB DBA operations — slow-query, lock-wait/deadlock, replication, and fragmentation RCA, with unbypassable audit logging (MCP + CLI), budget/runaway guards, dry-run, and undo/rollback.35MIT
- AlicenseAqualityAmaintenanceGoverned SSO/IAM operations for Keycloak and Authentik — login-failure, stale-permission, client-config, and MFA RCA, with unbypassable audit logging (MCP + CLI), budget/runaway guards, dry-run, and undo/rollback.29MIT
TDQS
Scored across 38 tools
Most tools are clearly scoped, but several groups overlap: dangling_images, image_disk_usage, system_df, and image_and_volume_bloat all report reclaimable disk / prune candidates, while container_restart_summary overlaps with restart_loop_rca. list_stacks vs list_compose_stacks is also easy to confuse despite the detailed descriptions.
The set follows consistent verb_noun conventions: list_*, inspect_*, system_*, container_*, and write verbs like stop_container, start_container, prune_images, and remove_container. Minor deviations like dangling_images, stack_detail, overview, restart_loop_rca, and image_and_volume_bloat keep it from being perfectly uniform.
38 tools is well above the 25+ threshold for a heavy toolset. Several read-only analysis tools (system_df, image_disk_usage, image_and_volume_bloat, dangling_images) overlap enough that the surface could be consolidated without losing real capability.
The read/diagnostic surface is comprehensive: containers, images, volumes, networks, system state, events, logs, stats, restart RCA, pressure analysis, and prune candidates are all covered. Container lifecycle writes (start/stop/restart/remove/update) and pruning are present; gaps are mostly targeted image/volume/network removal and compose/stack create-update flows, which are workable around.