Persistent memory tools for Claude Desktop. Search your vault or Obsidian notes mid-conversation.
Built by one non-coder. Running a live business. On consumer hardware. No CS degree required. New here? Start with the live site — it explains everything without a single line of code. Want the proof? → 353 sessions of real production data, rendered as charts Want the research? → Emergent values in persistent AI — tested on IBM Quantum hardware Want the full story? → 8 months, 3 AIs, one nuclear…
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Forge read 0 source files from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.
Built by one non-coder. Running a live business. On consumer hardware. No CS degree required. New here? Start with the live site — it explains everything without a single line of code. Want the proof? → 353 sessions of real production data, rendered as charts Want the research? → Emergent values in persistent AI — tested on IBM Quantum hardware Want the full story? → 8 months, 3 AIs, one nuclear reset "Every AI memory system stores what your agent knows. Adam stores who your agent is — in files…
Forge's dependency resolver reads npm metadata only, so this PyPI package has no resolved tree. That is a gap in coverage, not a clean bill of health.