Mnemosyne-Neural-OSBLOCK
A control room for AI memory. Your files and conversations become searchable memory any model you connect can draw on, and you decide what enters, what moves and what leaves. Vaults live on your hardware. Windows, macOS, Linux.
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
The sovereign AI Operating System
Open to build on · Private at the core
English ·  Français ·  Español ·  Deutsch ·  Português ·  Русский ·  中文
Everyone is building the intelligence. Mnemosyne OS builds the relationship: the memory that makes an AI truly know you, across sessions and across time. On your machine. Yours to see.
→ Why the relationship layer
[](https://github.com/Mnemosyne-OS/Mnemosyne-Neural-OS/actions) [](https://github.com/Mnemosyne-OS/MnemosyneOS---benchmarks/tree/main/longmemeval-rerun-2026-10) [
14 read · 9 write · 1 destructive. Blast radius: 1 tool can delete or overwrite — an agent that can be talked into calling a tool can be talked into calling this one.
| Tool | Risk | Description |
|---|---|---|
get_vault_info | read | Returns the active vault configuration: IDE, provider, vault path, chronicle count, local AI model. |
list_chronicles | read | List recent chronicles in the active vault. Returns filename, date, and preview. |
mnemosyne_about | read | Re-read the server instructions: the governance tenet, the vault protection model (NORMAL and MAXIMUM, mixableWith, isolated sandbox vaults), the spine model, and the rules for an agent working on someone else\ |
mnemosyne_agenda_add | write | Put appointments or deadlines into the user\ |
mnemosyne_agenda_list | read | Read the user\ |
mnemosyne_agenda_remove | destructive | Remove appointments from the user\ |
mnemosyne_agenda_update | write | Change an appointment already in the user\ |
mnemosyne_agent_collisions | read | Check whether two agent sessions are live in the same git working tree and branch right now, across every installed harness. Call it before |
mnemosyne_agent_files | read | List the files other agent sessions wrote or edited recently, newest first, with the session each one came from. Paths and timestamps only. Each entry says how it is known. |
mnemosyne_cockpit_update | write | Update your own status card on the user\ |
mnemosyne_memory_ingest | write | Write a memory into a vault: a decision, an architecture note, a debug finding, a session summary. It is stored permanently and indexed for every future agent to retrieve. Use it at the end of a meaningful work session, or whenever a decision is reached that someone will want to recall later. |
mnemosyne_memory_query | read | x |
mnemosyne_pheme_radar | read | Read what the user\ |
mnemosyne_pheme_watch | write | Add a subreddit, a Hacker News search query or a topic to the user\ |
mnemosyne_position_update | write | Record where you left off on a resonance: phase, current state, next steps. Call it at the end of a session. It is stored as a DECISION memory in the vault. |
mnemosyne_spine_assignments | read | See how Mnemosyne classified its memories. It returns the memory-to-spine assignments for one vault, newest first, and the per-spine counts for the whole vault. Use it to check whether memories landed in the right spines, to read a vault\ |
mnemosyne_todo_add | write | Put tasks into the user\ |
mnemosyne_todo_categories | read | Manage the lists of the user\ |
mnemosyne_todo_list | read | Read the user\ |
mnemosyne_todo_update | write | Change the user\ |
mnemosyne_vault_list | read | List the memory vaults this Mnemosyne OS exposes, each with its token, display name and memory count. Call it first when you are unsure which vault to work against, or when the user names a store you have not seen. Pass the bold token as the |
mnemosyne_voice_speak | read | Render a written script to a WAV file with a local voice, including the user\ |
name | read | description |
write_chronicle | write | Write a new chronicle entry into the MnemoForge vault. |
Trust audit
BLOCKgrade D · trust 69/100 Do not install this without reading the findings. The audit found something that could harm you or your machine.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | WARN |
| L2 | Instruction surface (what it tells the agent) | FAIL |
| L3 | Class-specific surface | WARN |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- declared (7 observation(s))
- Network
- declared (5 observation(s))
- Shell
- declared (2 observation(s))
- Dependencies
- not all pinned
- Secrets in source
- found
Findings (22)
# Contributor Covenant Code of Conduct
# Contributing to MnemoForge CLI
console.log(`[MnemoSDK] Token renewed for "${this.manifest.id}", expires: ${new Date(reg.expiresAt).toISOString()}`);const secret = 'sk-live-DO-NOT-LEAK-4815162342';
mnemosyne_agenda_remove
console.log(`[BridgeApp] ✓ Registered — token expires: ${new Date(reg.expiresAt).toISOString()}`);import { getInquirer } from '../../lib/lazy.js';import { loadVaultConfig, listChronicles, resolveChronicleDir } from '../../lib/vault.js';import { parseChronicle, getChronicleType } from '../../lib/chronicle-parser.js';import { renderChronicle } from '../../lib/chronicle-render.js';import { getInquirer } from '../../lib/lazy.js';const payload = JSON.parse(atob(padded)) as { sub?: string };? decodeURIComponent(escape(atob(base64)))
return decodeURIComponent(escape(atob(base64)));
@modelcontextprotocol/sdk, chalk, commander, inquirer, @types/inquirer, @types/node, tsx, typescript
@mnemosyne_os/cartridge-sdk, react, react-dom, @testing-library/jest-dom, @testing-library/react, @types/react, @types/react-dom, @vitejs/plugin-react
yjs, @types/node, rimraf, typescript, vitest
@types/node, typescript, vitest
jsdom, tsup, typescript, vitest
assets/infinite-canvas.gif
assets/infinite-canvas.mp4
assets/nexus-graph.png
Gates applied: no_behavioural_pass.
1180f51bb580full audit observations/trust-audit/mcp-server/mnemosyne-os__mnemosyne-neural-os.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-10 | 1180f51bb580 | BLOCK | D | 69 | first audit |
Questions
What is the Mnemosyne-Neural-OS MCP server?
A control room for AI memory. Your files and conversations become searchable memory any model you connect can draw on, and you decide what enters, what moves and what leaves. Vaults live on your hardware. Windows, macOS, Linux.
What tools does Mnemosyne-Neural-OS expose?
24 in total: 14 read-only, 9 that write, and 1 that can delete or overwrite (mnemosyne_agenda_remove). Every one is listed on this page with its risk.
Is Mnemosyne-Neural-OS safe to connect to an agent?
No — not without reading the findings first. The audit graded it D (69/100) and found 2 critical or high issues in the source. Each one is listed on this page with the file and line it is on. Separately from the audit: 1 of its tools can destroy data, so scope the token you give it to what you actually need.
What credentials does Mnemosyne-Neural-OS need?
No credential environment variables were found in its source, so it appears to need none.
How does Mnemosyne-Neural-OS run?
It speaks stdio, so it runs as a local process your client starts. It is published on npm as @mnemosyne_os/sdk at 1.5.7.
How current is this page?
The grade is for one exact copy of the source (1180f51bb580), read on 2026-10-10. The repository is watched and re-audited when it changes.