No user-submitted related servers found.
Scored across 11 tools
Several tools target the same vulnerability/health space: dependency_health, vulnerability_scan, and dependency_check all report CVEs but on different scopes (aggregate counts, project lockfiles, single version), which can confuse an agent picking between them. Likewise agent_memory and decision_memory both store decisions/warnings, and get_context vs what_should_i_know both surface context, though the 'call when' cues in descriptions help disambiguate.
All names are snake_case so the casing is consistent, but the conventions are mixed: some are noun phrases (dependency_health, ecosystem_pulse, decision_memory), some are verb_noun (get_context, vulnerability_scan, check_decision_alignment), and one is a full question (what_should_i_know). It remains readable but there is no predictable verb_noun pattern throughout.
Eleven tools sit comfortably in the ideal 3-15 range and the set is coherently scoped to dependency intelligence plus developer context. A few dependency tools (health, scan, check, planner, impact) could arguably be consolidated, but none feels gratuitous.
The surface covers the domain well: health, upgrade planning, vulnerability scanning, pre-write version vetting, impact analysis, decision memory, agent memory, ecosystem pulse, and user context. Minor gaps exist (e.g., no explicit dependency listing/package-family enumeration, no advisory search), but agents can work around them.