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
- 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 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 a distinct resource and action, such as interface_status vs gateway_status vs dhcp_leases. However, 'apply_changes' and 'reconfigure' with subsystem='filter' overlap, and 'rule_stats'/'rule_states'/'rule_hit_and_shadow_analysis' could be confused by name, though descriptions clarify.
Naming mixes verb-noun patterns like list_rules and toggle_rule, noun-only names like health_status and nat_outbound, and single verbs like reboot and reconfigure. While readable, there is no consistent convention across the set.
35 tools is on the high side, but the firewall domain covers many distinct subsystems: system health, interfaces, gateways, aliases, rules, NAT, VPN, DHCP, logs, and state. The count is justifiable for a comprehensive AIOps tool, though it may feel heavy for agent navigation.
The server covers most read/monitoring needs and common write operations: toggle rules, add/remove alias entries, apply changes, restart services, reboot, and kill states. Missing create/delete rules or aliases, but for an AIOps tool focused on diagnostics and remediation, the surface is largely complete.