No user-submitted related servers found.
Scored across 52 tools
Many tools overlap in purpose: capture, extract, learn, decide, task, and brainstorm all store different knowledge artifacts, while status, stats, doctor, telemetry, hygiene_report, watchdog, resume, and session all report on project/session state. Descriptions help somewhat, but an agent faces multiple plausible choices for common actions like recalling context, recording knowledge, or checking health.
Naming mixes single-word nouns and verbs (spec, tickets, gate, read, write) with prefixed snake_case families (worktree_*, skill_*, graph_*, knowledge_*). The groupings are readable, but there is no single consistent verb_noun pattern across all 52 tools.
52 tools is far beyond the typical concise MCP surface and exceeds the rubric's 50+ extreme mismatch threshold. Even with broad knowledge, skill, worktree, and hygiene domains, this many tools creates a high selection burden and likely includes low-frequency operations better exposed as actions within fewer multiplexed tools.
The surface is extensive and covers most domains it names: vault read/write/search/link/capture/extract, skill install/list/remove/validate, worktree lifecycle, spec/ticket/evidence/gate workflows, graph traversal, and session coordination. Only minor gaps exist, such as explicit edit/delete operations for individual vault notes beyond deprecate/prune, but agents can work around them.