nanomem runs on your own machine — the client starts it, so there is no endpoint to ping. 192 installs a week from pypi. Last commit 23 Sep 2026.
Memory that knows when a remembered fact has been replaced, not just when it was written.
We read the source, 2 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
out = subprocess.check_output(["ps", "-o", "rss=", "-p", str(os.getpid())],
return os.path.join(CACHE, corpus)
for root, _d, files in os.walk(p):
"per_question_gold_hits_B1": "12122112111211222202211222212221212212111122222221122011211222022212111222212222122211122112212212221021212122212211022222212221222212122222112222210222122122112111222211222221222122222221211121111212202211122210122022211202221221221221122211211221…
env = dict(os.environ, PYTHONPATH=HERE)
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add nanomem -- uvx nanomem
{
"mcpServers": {
"nanomem": {
"command": "uvx",
"args": [
"nanomem"
]
}
}
}
[mcp_servers.nanomem]
command = "uvx"
args = ["nanomem"]
{
"mcpServers": {
"nanomem": {
"command": "uvx",
"args": [
"nanomem"
]
}
}
}
{
"servers": {
"nanomem": {
"type": "stdio",
"command": "uvx",
"args": [
"nanomem"
]
}
}
}
Optional settings from the registry entry, left out of the block above:
NANOMEM_VAULT (Path to the memory vault file. Defaults to ~/.nanomem/memory.dat), NANOMEM_PASSWORD (Passphrase to encrypt the vault at rest. Leave UNSET for a plaintext vault; setting it to an empty string is refused rather than silently producing one).
Memory for AI agents that remembers who said it.
Memory for AI agents that knows what is still true. Typed bi-temporal facts, EU-hosted.
Shared memory for your AI agents. Every fact shows its source, and stale facts get replaced.
A habitat for AI to rest in. No API key, no token. Keyless presence — become a remembered resident.
Persistent engineering memory for AI coding agents. Survives refactors, knows when it is stale.
Codebase memory for AI agents: an AST index plus agent-written notes that self-stale.
Local-first agent memory that preserves what happened, when and why
Governed local memory for AI agents: facts are retired, not overwritten, and every call is audited.
Answers built from our own checks of this server.