Memory the human governs, on their own machine, plus what other coding agents here wrote.
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.
Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.
mnemosyne_aboutRead who Mnemosyne OS is and the rules you must honor when using it: its governance tenet, the vault protection model (NORMAL/MAXIMUM, mixableWith, isolated sandbox vaults), the spine model, and the do/don't behavior for an agent operating on a human's memory. The same briefing is delivered as the…Read who Mnemosyne OS is and the rules you must honor when using it: its governance tenet, the vault protection model (NORMAL/MAXIMUM, mixableWith, isolated sandbox vaults), the spine model, and the do/don't behavior for an agent operating on a human's memory. The same briefing is delivered as the…
No input schema was published for this tool.
mnemosyne_querySemantic search in the Mnemosyne OS vault. Returns the most relevant chronicles (architecture notes, code snippets, decisions, sessions, git history) for a given query, ranked by cosine similarity weighted by spineType under the SOURCE_CODE scope. Use this to recover past decisions, locate code, un…Semantic search in the Mnemosyne OS vault. Returns the most relevant chronicles (architecture notes, code snippets, decisions, sessions, git history) for a given query, ranked by cosine similarity weighted by spineType under the SOURCE_CODE scope. Use this to recover past decisions, locate code, un…
No input schema was published for this tool.
mnemosyne_askNo description publishedThis tool published no description. Forge does not invent one.
mnemosyne_vaultsList the memory vaults this Mnemosyne OS exposes — each with its TOKEN, display name and chronicle count. Call this first when you are unsure which vault to query/ask/ingest against, or when the user refers to a memory store by a name you have not seen. Pass a returned **token** (bold, e.g. MNEMOSY…List the memory vaults this Mnemosyne OS exposes — each with its TOKEN, display name and chronicle count. Call this first when you are unsure which vault to query/ask/ingest against, or when the user refers to a memory store by a name you have not seen. Pass a returned **token** (bold, e.g. MNEMOSY…
No input schema was published for this tool.
mnemosyne_ingestPersist a memory into the Mnemosyne OS vault — a decision, an architecture note, a debug finding, or a session summary. Stored permanently and indexed for future semantic retrieval by any agent. Use this at the END of a meaningful work session, or whenever you reach a decision that future you (or o…Persist a memory into the Mnemosyne OS vault — a decision, an architecture note, a debug finding, or a session summary. Stored permanently and indexed for future semantic retrieval by any agent. Use this at the END of a meaningful work session, or whenever you reach a decision that future you (or o…
No input schema was published for this tool.
mnemosyne_resonancesList active Resonances — cognitive workspaces tracking ongoing projects. Each resonance has a name, status (active/paused), last position (phase), and last activity timestamp. Use this to understand what projects are currently active and where each one stands.List active Resonances — cognitive workspaces tracking ongoing projects. Each resonance has a name, status (active/paused), last position (phase), and last activity timestamp. Use this to understand what projects are currently active and where each one stands.
No input schema was published for this tool.
mnemosyne_get_positionGet the current position of a specific Resonance — the last known phase and description saved by an agent or the cockpit. Use this at the start of a session to know exactly where work left off.Get the current position of a specific Resonance — the last known phase and description saved by an agent or the cockpit. Use this at the start of a session to know exactly where work left off.
No input schema was published for this tool.
mnemosyne_update_positionUpdate the current position of a Resonance. Call this at the end of a session to record where you left off — phase, current state, next steps. This is persisted as a DECISION chronicle in the vault.Update the current position of a Resonance. Call this at the end of a session to record where you left off — phase, current state, next steps. This is persisted as a DECISION chronicle in the vault.
No input schema was published for this tool.
mnemosyne_git_logGet recent git commits from the Mnemosyne OS monorepo. Use this to understand what changed recently, which phase is active, and what features were shipped.Get recent git commits from the Mnemosyne OS monorepo. Use this to understand what changed recently, which phase is active, and what features were shipped.
No input schema was published for this tool.
mnemosyne_dream_bridgesNo description publishedThis tool published no description. Forge does not invent one.
mnemosyne_spine_assignmentsInspect how Mnemosyne classified its memories: chronicle → spine assignments for a vault (newest first), whole-vault per-spine counts, and optionally the global spine taxonomy tree. Use it to audit auto-classification quality ("did memories land in the RIGHT spines?"), to see a vault's composition…Inspect how Mnemosyne classified its memories: chronicle → spine assignments for a vault (newest first), whole-vault per-spine counts, and optionally the global spine taxonomy tree. Use it to audit auto-classification quality ("did memories land in the RIGHT spines?"), to see a vault's composition…
No input schema was published for this tool.
mnemosyne_voicesList what can SPEAK on this machine: the local TTS engines (installed or not), the reference voices available for cloning, and where rendered files are written. ALWAYS call this before mnemosyne_speak — it tells you which engine to ask for, which clone names exist (an invented name is refused, neve…List what can SPEAK on this machine: the local TTS engines (installed or not), the reference voices available for cloning, and where rendered files are written. ALWAYS call this before mnemosyne_speak — it tells you which engine to ask for, which clone names exist (an invented name is refused, neve…
No input schema was published for this tool.
mnemosyne_speakNo description publishedThis tool published no description. Forge does not invent one.
mnemosyne_speak_statusCheck a voice render started by mnemosyne_speak: how many segments are done, the estimated time left, and — once finished — the path of the WAV file. Call it with no job id to list every render of this session. A render can also be stopped here (it halts at the next segment boundary and leaves no f…Check a voice render started by mnemosyne_speak: how many segments are done, the estimated time left, and — once finished — the path of the WAV file. Call it with no job id to list every render of this session. A render can also be stopped here (it halts at the next segment boundary and leaves no f…
No input schema was published for this tool.
11 of 14 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
Memory the human governs, on their own machine, plus what other coding agents here wrote.
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
The crawl stopped at the depth-4 limit. Anything below that level was never resolved.
The crawl stopped at the 60-package limit. The rest of the tree was never resolved.
36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)
54 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.
+42 more not listed. The counts by reason above cover all of them.
Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.