MCP tool
memory_status
memory_status is a tool name used by 2 different MCP servers. They are not necessarily the same tool — here is what each one does.
2 MCP servers expose a memory_status tool: mcp-memory-rs and MemoryRouter. Their input schemas differ, so compare them below before picking one.
Servers exposing memory_status
From the publisher:Local-first status: dirty queue, manifest hash, last sync.
Install mcp-memory-rs →From the publisher:Use this when the user asks whether MemoryRouter is connected, which opaque vault binding is active, or how many memories/tokens the connected vault contains. Does not reveal the memory key.
Install MemoryRouter →
Related tools
The same action under a namespaced name on other servers.
Tool lists are read from the live servers (or, for packaged servers, from their documentation) each morning, so this reflects what they exposed at the last refresh. Search all tools.