No user-submitted related servers found.
Scored across 14 tools
Most tools are clearly distinct (status, selftest, lock, unlock, get, store, search, recent, namespaces, link, relations, unlink), but memory_store and memory_store_many overlap in purpose (single vs. batch), and memory_forget vs. memory_unlink could be confused by name alone (deleting a memory vs. removing a relation).
The memory_* prefix is consistent and most tools follow verb_noun (memory_get, memory_store, memory_search, memory_forget, memory_unlock, memory_link, memory_unlink). Minor deviations: memory_status, memory_selftest, memory_recent, memory_list_namespaces are noun/adjective-first rather than verb-first, but the pattern is still readable.
14 tools is well within the ideal range for a memory vault server. Each tool covers a distinct operation: lifecycle (store/get/forget), search/recent, graph (link/relations/unlink), vault management (lock/unlock/status/selftest), and namespaces. No tool feels redundant or extraneous.
The surface covers the full memory lifecycle: store (single and batch), retrieve by id, search, list recent, forget with shred, plus graph relations (create/query/delete), namespace management, and vault lock/unlock/status/selftest. The only minor gap is no explicit update tool, but supersedes in memory_store covers corrections, so no dead ends.