firewall-aiops
Related Servers
Alternatives to firewall-aiops
No user-submitted related servers found.
Related Servers
- 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
- AlicenseNot gradedqualityAmaintenanceManage a fleet of OPNsense firewalls from an AI agent, inside guardrails it can't drive around. MCP server for central management of OPNsense firewall fleets. 129 tools across devices, config sync, tasks, schedules, templates, backups and remote consoles - destructive actions confirmation-gated, MCP-issued tokens lifetime-bounded, backup and storage secrets excluded from the toolset entirely.Apache 2.0
- AlicenseAqualityAmaintenanceGoverned XCP-ng operations via Xen Orchestra REST — VM-health, SR-usage, backup-failure, and patch-state RCA, with unbypassable audit logging (MCP + CLI), budget/runaway guards, dry-run, and undo/rollback.29MIT
- AlicenseAqualityAmaintenanceGoverned 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 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
- 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
TDQS
Scored across 35 tools
Most tools target clearly distinct resources or analyses (e.g. states_table vs rule_states vs top_talkers differ by scope/aggregation, gateway_status vs gateway_health_rca differ raw-vs-RCA). The main overlap is apply_changes vs reconfigure, both of which can commit the staged filter set, but the descriptions explicitly call out the shared lockout guard and subsystem scoping, so it stays resolvable.
The set is dominated by a readable snake_case resource-oriented convention (rule_detail, states_table, nat_outbound, dhcp_leases), with a few verb-first variants (list_rules, toggle_rule, add_alias_entry). The mixed verb-first/noun-first ordering (list_rules vs rule_detail) is a minor inconsistency but naming stays predictable.
35 tools is heavy by any measure and crosses into over-scoped territory. The domain is genuinely broad (filter, NAT, aliases, states, DHCP, VPN, health, undo, write ops), so many tools earn their place, but the surface is large enough to be borderline unwieldy.
Read coverage is excellent across rules, NAT, aliases, DHCP, VPN, and health, and the analyze/apply/undo lifecycle is well thought out. However, the write surface is thin: rules can only be toggled (no create/edit/delete), and aliases only support entry add/remove, so key lifecycle operations are missing for a firewall-management domain.