No user-submitted related servers found.
Scored across 81 tools
Many tools target distinct DNS/email controls, and descriptions often explicitly disambiguate neighbors such as check_dane vs check_dane_https or check_spf vs resolve_spf_chain. However, the set has several overlapping clusters (scan_domain vs batch_scan vs compare_domains, check_mx_reputation vs check_rbl, multiple OSINT start/status/report families), so an agent can still misselect without careful reading.
Most names use readable snake_case and follow recognizable verb_noun or resource_action patterns, especially in async families like batch_scan_start/status/findings. A few names deviate from the dominant pattern, such as generate, cymru_asn, sge_quickscan, and brand_audit_single, but the overall convention remains predictable.
The server covers a very broad security domain, but 81 tools is far beyond a practical MCP surface for reliable agent selection. Many tools are operator-only, tier-gated, or rarely needed, and the sheer breadth makes the set feel like several products combined.
Coverage is strong across DNS, email authentication, TLS, reputation, brand discovery, compliance mapping, remediation generation, validation, and async reporting. Minor operational gaps remain, such as no obvious scan-history/list management or cancellation surface for async jobs.
