No user-submitted related servers found.
Scored across 112 tools
Most tools are clearly distinct due to strong domain prefixes and specific CRUD operations. However, with 112 tools there are a few overlapping ones (e.g., opnsense_sys_info vs opnsense_diag_system_info) and similar diagnostics tools that could cause misselection, though descriptions help differentiate them.
The naming pattern is highly consistent: 'opnsense_' + domain + action + object (e.g., opnsense_dns_list_overrides, opnsense_fw_add_rule). Verbs like list/add/delete/update/apply are used uniformly. Minor exceptions like opnsense_fw_manage_alias and opnsense_acme_settings exist but are negligible.
112 tools is far beyond the typical 3-15 for a well-scoped server. While OPNsense covers many subsystems, this count feels excessive and could overwhelm agents. Many tools are specialized (e.g., 6 DNS cache tools, 4 log tools) and could be consolidated into fewer parameterized operations.
The set covers major OPNsense domains comprehensively: DNS, firewall, DHCP, Kea, interfaces, routes, NAT, ACME, firmware, Tailscale, and diagnostics. CRUD operations exist for key objects with apply functions. Minor gaps exist (e.g., no destination NAT/port forwarding tools, no VPN management), but the core firewall and network management lifecycle is well-covered.
