No user-submitted related servers found.
Scored across 9 tools
The list/get pairs are cleanly separated by resource type (frameworks, risks, mitigations), and search_frameworks is explicitly scoped to frameworks only, so an agent can tell it apart from the getters. The only soft overlap is between get_service_health and get_cache_stats, both diagnostic calls whose boundaries are not fully explained.
Every tool follows the same snake_case verb_noun pattern (list_*, get_*, search_*), with no camelCase or bare-noun outliers. The verb predicts the behavior reliably: list returns catalogs, get returns full document content, search returns matches.
Nine tools is well within the ideal range and each earns its place: three resource types times a list/get pair, plus one search and two small operational diagnostics. Nothing appears redundant or padded.
The read-only document lifecycle is fully covered for all three resources (list + get), plus search for frameworks. The notable gap is that phrase search exists only for frameworks, leaving risks and mitigations requiring an expensive list-then-get flow; there is also no cross-corpus search or framework-vs-requirement comparison capability.