No user-submitted related servers found.
Scored across 18 tools
Each tool targets a distinct operation—CRUD, assessment, import, scan, metrics, VEX—and the cross-references with 'Don't use when' guidance reinforce boundaries. The only close pairs are list_resources vs list and describe_resource vs list_resources, which could confuse by name alone, but the purposes are clearly separated.
All tools share the secobserve_ prefix and most follow verb_noun (list_resources, trigger_scan, run_periodic_task). Deviations include bare verbs (get, list, create, update, delete) and noun-phrase names (status, product_metrics, vex_document), so the pattern is consistent but not uniform.
18 tools is on the high side but justified by the broad vulnerability-management domain: generic CRUD, schema discovery, assessment workflow, import paths, scanning, metrics, and VEX generation each earn their place. It is slightly above the typical well-scoped range, so not a perfect score.
The surface covers the full lifecycle: schema discovery before writes, CRUD for all resources, an audited assessment workflow with bulk and approval steps, multiple ingestion paths, scan triggering, metrics, background jobs, and VEX output. Generic list/get/create/update/delete plus call_action covers long-tail resources, leaving no obvious dead ends.
