Exact memory Β· MCP server

The memory bank that
never makes facts up

rse_mem gives your LLM agent an exact, verifiable memory. Store a fact, get it back byte-for-byte β€” or an explicit MISS. No confabulation on what's stored. Ever.

agent Β· rse_mem
agent> memory_recall("project.deadline")
HIT (verified, exact)
2026-11-14 β€” ship v1 to the pilot customer
β€” provable-recall receipt: root βœ“ Β· proof βœ“
agent> memory_recall("project.budget")
MISS β€” not in memory. I won't guess.

Hallucination is a recall problem

When an LLM reconstructs a known fact from its weights, it can produce a confident, plausible, wrong answer. The fix isn't a bigger model β€” it's reading instead of reconstructing.

Without an exact memory

Reconstructed from weights

The model regenerates the fact lossily every time. When it's uncertain, it fills the gap with something that sounds right.

"I think the deadline was probably mid-November…"
With rse_mem

Read back, byte-for-byte

The fact is stored losslessly and returned exactly, with a proof β€” or an explicit MISS that tells the model to stop and ask.

"2026-11-14."  Β·  "Not in memory."

Built to be trusted, not believed

Three properties make rse_mem different from embeddings, RAG, and vector search.

βœ“

Exact recall

Facts are stored losslessly and reconstructed byte-for-byte. No embeddings, no summarization, no similarity guesswork β€” the value you get is the value you stored.

πŸ”

Provable

Every recall returns a cryptographic receipt. An independent verifier confirms the value against a published root β€” you don't have to trust the server, you verify it.

β›”

Honest misses

Ask for something that isn't stored and you get an explicit MISS β€” never an invented answer. "I don't know" becomes a first-class, reliable response.

How it works

rse_mem runs as an MCP server. Your agent calls it like any other tool.

Remember

Store a durable fact under a stable key β€” project.deadline, user.timezone, a decision, a result. It's kept exactly.

Recall

Before answering from memory, the agent calls memory_recall. A HIT returns the exact value plus a proof; a MISS says so plainly.

Verify

Any recall can be checked against the published root with memory_verify. A substituted or altered value cannot pass.

Install in one line

Register rse_mem as an MCP server in your agent client.

# register the rse_mem MCP server claude mcp add rse-memory -- rse_mem_server

Runs locally. Your memory store stays on your machine.

Request access