No user-submitted related servers found.
Scored across 14 tools
The core write/read pairs are clearly separated: memory_store vs memory_store_many (one claim vs batch), memory_search vs memory_recent (relevance vs recency), and memory_link vs memory_store (graph edge vs prose). The only mild overlap is memory_status vs memory_selftest, both of which report vault health from different angles, and memory_relations vs memory_search, which target different data stores but could be confused by a hurried agent.
Every tool uses the memory_ prefix with snake_case, giving a predictable family. Most are verb-based (store, search, link, get, forget, lock, unlock), but a few are noun/adjective forms (memory_relations, memory_status, memory_selftest, memory_recent), a minor deviation from a strict verb_noun pattern.
Fourteen tools is well within a reasonable range for a memory vault that includes CRUD, a relation graph, namespace listing, admin/status, and lock controls. Each tool covers a distinct operation and none appear redundant or padded.
The surface covers memory lifecycle (store, store_many, search, get, forget with supersedes for corrections), full relation graph CRUD (link, relations, unlink), and admin controls (status, selftest, lock, unlock, list_namespaces). Minor gaps exist: no direct update of tags/importance/expiry on an existing record without re-storing via supersedes, and no namespace create/delete beyond listing.