Skip to main content
Glama
AutomateIP

fwrule-mcp

by AutomateIP
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to fwrule-mcp

No user-submitted related servers found.

    Related Servers

    • Panorama MCP Server

      fquiroga
      A
      license
      A
      quality
      C
      maintenance
      A read-only MCP server for Palo Alto Panorama policy review that reads security rules, finds duplicates, broader coverage, conflicts, and overlaps, and returns preclear decisions without committing changes.
      4
      MIT

    • OPNsense MCP Server

      smaniktahla
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server for comprehensive OPNsense firewall management, enabling AI assistants to manage firewall rules, NAT, VLANs, and network diagnostics, plus execute SSH/CLI commands. Supports safety modes like read-only and dry-run for safe operation.
      118 npm
      MIT

    • Support Engineer MCP Server

      tsabra76
      -
      license
      Not graded
      quality
      B
      maintenance
      A vendor-agnostic MCP server for technical support engineers, providing knowledge search, ticket analysis, and resolution suggestions.
      -

    • mcp-opnsense

      drmfar
      F
      license
      Not graded
      quality
      C
      maintenance
      MCP server for managing OPNsense firewalls, providing read-only tools for firewall rules, aliases, interface statistics, and gateway status with multi-instance support.
      -

    • fortigate-mcp

      oscardagrach
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that enables natural language management of FortiGate firewalls via the FortiOS REST API, offering 393 tools for system, policy, routing, VPN, and security configuration.
      MIT
    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.4/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: parsing, listing vendors, single rule analysis, and batch analysis. No overlap or ambiguity.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun snake_case pattern (e.g., analyze_firewall_rule_overlap, batch_analyze_overlap, list_supported_vendors, parse_policy), making them predictable.

    Tool Count5/5

    With 4 tools, the set is well-scoped for firewall rule overlap analysis, covering all necessary operations without being overly large or sparse.

    Completeness5/5

    The tool surface is complete for the domain: parsing configs, listing vendors, and performing both single and batch overlap analysis. No obvious gaps.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources