No user-submitted related servers found.
Scored across 30 tools
Several tools genuinely overlap: ssl_check/http_security/security_scan/owasp_check all grade a domain's posture, lookalike_domains vs impersonation_exposure, subdomain_discovery vs exposure_map, check_before_action vs phishing_link_check, and set_expectations vs verify_expectations all cover close ground. To the server's credit, descriptions explicitly cross-reference each other ('use X instead for Y'), which rescues the agent from most misselection, but the boundaries remain fuzzy enough that wrong picks are plausible.
Names are uniformly snake_case and almost all follow a subject_action or action_noun pattern (asn_lookup, dns_propagation, port_scan, check_before_action). Minor deviations exist (reverse_dns and subnet_calc place the noun differently, infra pivot/subnet_calc use different verbs), but the scheme is predictable and readable throughout.
At 30 tools this is on the heavy side and sits above the 25-tool threshold that signals bloat. The scope is genuinely broad (DNS, TLS, email, reputation, impersonation, MCP vetting, monitoring, reporting), so many tools earn their place, but the overlap noted above suggests a few could be consolidated.
For an external security/recon domain the surface is remarkably complete: point-in-time checks, historical timelines, daily monitoring watches, declarative expectation sets, one-shot composite scans, safe-browsing verdicts, a reporting path, and even niche areas like PQC readiness and MCP-server vetting. No obvious dead ends for the stated purpose; the only limits are declared scope boundaries (authenticated/active testing) rather than missing operations.