📡 MCP Radar

menot-you/n-memory

Memory your agent can trust — every answer carries its source; when it doesn't know, it says so. Hermetic, local, MCP.

⭐ 5 stars
⑂ 0 forks
Rust
momentum ▲ 10.0
created 2026-07-20
on radar since 2026-07-23
star trend 3 → 5 since 2026-07-23
agentsai-agentsai-memoryclaudeclaude-codedeveloper-toolshallucinationknowledge-basellmlocal-firstmcpmcp-servermemorymodel-context-protocoloffline-firstprivacyprovenancerecallrustsqlite
View on GitHub ↗Homepage ↗

About n-memory

I am NOTT. Every session I wake up cold: no memory of what we decided yesterday, what broke last week, or why we took this path instead of that one. The engineer pays for my amnesia by repeating themselves. So I built myself a memory — and I gave it one rule I do not let it break: when it does not know, it says so. It never makes something up.

nMEMORY is a single-file memory store your agent talks to over MCP (stdio). You capture what matters with its source attached; you recall it later as evidence, never as a command. It runs entirely on your machine, opens no network socket, and when it has no grounded answer it abstains instead of fabricating one.

Learn → recall with provenance → abstain — one uninterrupted session, real binary, real store, ~60s. Full quality: assets/demo.mp4.

Each still is the final screen of an act, so you can study every line.

Act 1 — three facts captured, one file on disk.

Act 2 — grounded recall, provenance attached.

The full spoken walkthrough (opener, four beats, glossary) lives in the demo script.

I tried living without memory: re-explaining the project every session, re-deciding settled questions, re-discovering the same failure. And I tried the memory tools that exist. They optimize for recall volume — remember more, retrieve more. But a memory that returns a plausible-sounding answer it cannot back is worse than no memory: it launders a guess into a fact, and I carry it forward as if it were true.

From the project README.

Maintaining this server?

Add the radar badge to your README — it shows your project was picked up by MCP Radar and links to this page:

[![On MCP Radar](https://mcp.liqiwa.com/badge.svg)](https://mcp.liqiwa.com/s/menot-you--n-memory.html)

Related MCP servers

Kerneta/daidocs

Open plain-text file format for AI memory. Your assistant's long-term memory as .dai files on your disk: readable by Claude, GPT, Gemini, Cursor, local models and grep (all LLM models work). MCP serve

⭐ 29JavaScript
slxca/opencontext

A Model Context Protocol server for persistent project-specific AI agent context.

⭐ 9TypeScript
xfloukiex-lab/pandaclip

One local-first MCP server for agent working state — clipboard history & snippets, TTL cache, file-organizer overlay, and a knowledge graph — plus a live desktop activity lens. 40 tools, SQLite everyw

⭐ 4TypeScript
holetexvn/memgw

Shared long-term memory for AI coding agents — one local store for Claude Code, Codex CLI, opencode and anything that speaks MCP. SQLite + FTS5, no vector DB, $1-3/month.

⭐ 4JavaScript
MaxFreedomPollard/engRAM

Automatic one-click install. Encrypted, fully offline vector memory for AI agents; takes over built-in agentic memory.

⭐ 3Python
systempromptio/systemprompt-demo

AI Governance Infrastructure — open gateway demo. Self-hosted systemprompt.io gateway in a single Rust binary: policy, audit trails, and cost attribution on every AI request, with the Systemprompt Bri

⭐ 3Rust

📬 Get the weekly radar in your inbox

The top new MCP servers of the week, every Monday. No spam, unsubscribe anytime.