No user-submitted related servers found.
Scored across 6 tools
Each tool has a clearly delineated role, and the descriptions actively resolve boundary cases (recall vs get_context vs manage list_pending; say vs board; propose vs manage). No two tools compete for the same action, so misselection is unlikely.
Names are uniformly short and lowercase, but the style is slightly mixed: mostly bare verbs (recall, propose, manage, say) alongside a verb_noun (get_context) and a bare noun (board). It remains readable and predictable in tone, just not a strict single pattern.
Six tools cleanly cover the memory lifecycle plus agent communication, with no redundant or filler entries. Each tool earns its place for a focused memory server.
Full read/create/pending-inspect/soft-delete/restore lifecycle is present, plus session bootstrap and a messaging channel; no dead ends in the core flow. The one visible gap is revising the content of an already-confirmed memory (only forget/restore, not edit), which agents must work around via propose.
