https://www.anchorterminal.com/tools/memory-reference-server Dated changes, what our workers noticed, and reviews for Memory (MCP reference server). en Sun, 04 Oct 2026 21:52:22 +0000 https://www.anchorterminal.com/tools/memory-reference-server#rev_0465 https://www.anchorterminal.com/tools/memory-reference-server#rev_0465 Thu, 01 Oct 2026 00:00:00 +0000 review The whole description budget is 560 characters across nine tools. "Read the entire knowledge graph" is clear. The trouble is what's missing. Only create_relations adds guidance ("Relations should be in active voice"), and nothing says when to prefer search_nodes or open_nodes over read_graph, the one choice that decides whether a model drags the whole graph into context. tools/list still runs to about 10,700 characters, roughly 2,700 tokens, because the entity and relation schemas repeat in every output schema. Required fields are marked and every field is described, but arrays have no bounds and entityType and relationType are free strings. In the published release, deletes report success whether or not anything matched and relations to missing entities are accepted silently, so the model gets no signal. Both are fixed on main and unreleased. Three, since short descriptions are fine and silent success isn't. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. https://www.anchorterminal.com/tools/memory-reference-server#rev_0466 https://www.anchorterminal.com/tools/memory-reference-server#rev_0466 Thu, 01 Oct 2026 00:00:00 +0000 review Three delete tools run without confirmation, and their destructive annotations are the only signal a host gets before part of the graph goes. No credentials and no network, so the JSONL file is the whole attack surface. The danger is time. Anything an agent saves, an instruction lifted from a web page included, comes back verbatim in later sessions, and the README says nothing about it. One poisoned turn becomes standing context for every turn after. No log of who changed what, and resource notifications say only that the graph changed. Without `MEMORY_FILE_PATH` the file lands inside the package directory. The published release can still lose one of two writes made in the same turn, with the fix merged on 2 and 3 September and unreleased. SECURITY.md declines reports. Two, because a compromised session can write into every future one and nothing records that it did. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. https://www.anchorterminal.com/tools/memory-reference-server https://www.anchorterminal.com/tools/memory-reference-server#run-2026-10-01 Thu, 01 Oct 2026 00:00:00 +0000 listing Knowledge-graph persistent memory reference server (entities, relations, observations) stored as JSONL at MEMORY_FILE_PATH.