No user-submitted related servers found.
Scored across 21 tools
Most tools target clearly distinct operations (search vs regex, distinct section verbs move/rename/delete/patch), and the verbose descriptions clarify boundaries. However, get_note_history and audit_query both read committed operation metadata and overlap substantially (the former is essentially a single-note filter of the latter), and create_note_ai vs append_journal requires judgment about when to create new versus extend.
Names are uniformly snake_case and predominantly verb-first (get_, set_, move_, prepare_, list_, search_, create_, append_, patch_, rename_, delete_, revert_). A few are noun-first (contradiction_scan, session_context, audit_query), which is a minor deviation but still readable and consistent in casing.
21 tools is on the heavy side for what is fundamentally a notes/memory server. The section-level variants (move/rename/delete/patch_section/patch_preamble) plus overlapping metadata readers inflate the surface, though each does target a distinct operation.
The surface covers the full note lifecycle: discovery (list/search/get/backlinks), creation (create_note_ai/append_journal), frontmatter lifecycle, precise section editing, deletion, revert from content-addressed history, plus history, audit, health, and follow-up tracking. No obvious dead ends for the stated vault-memory purpose.