No user-submitted related servers found.
Scored across 8 tools
Tools are largely distinct: search_techniques finds ATT&CK techniques, mitigations_for_technique maps a technique, techniques_for_actor maps an actor, and finding_details fetches check/fix text. Minor overlap exists between mitigations_for_technique and techniques_for_actor with include_mitigations, and resolve_system vs list_stigs both surface STIGs, but the descriptions differentiate them well.
All names use snake_case, but the set mixes verb_noun names (search_techniques, resolve_system, list_stigs, install_knowledge_base, check_sources) with noun_phrase names (mitigations_for_technique, techniques_for_actor, finding_details). The pattern is readable but not a single predictable convention.
Eight tools is well within the 3-15 range and each has a clear role: discovery, mapping, detail retrieval, system resolution, STIG listing, and knowledge-base lifecycle. No tool feels redundant or missing from a count perspective.
The surface covers the primary workflow: find technique or actor, get mapped controls/findings, then fetch DISA check/fix text, plus STIG discovery and KB install/check. Some reverse-lookup or bulk-finding operations are absent, such as control-to-technique lookup or all findings for a STIG, but agents can work around these via existing mapping and detail tools.