Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

Mnemoverse Memory

NPM · @MNEMOVERSE/MCP-MEMORY-SERVER · 2 COMPONENTS · SCANNED AUG 3

Hosted memory for AI agents that learns and forgets — one key across Claude, Cursor & ChatGPT.

+22 this week 67 Trust /100
Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →

Supply Chain Security86
  • No malware found by supply-chain analysis.Pass
  • Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability70
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1315 tokens (~146/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
  • Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · @mnemoverse/mcp-memory-server

# add to Claude Code
claude mcp add mnemoverse-mcp-memory-server -- npx -y @mnemoverse/mcp-memory-server
# add to Codex CLI
codex mcp add mnemoverse-mcp-memory-server -- npx -y @mnemoverse/mcp-memory-server
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mnemoverse-mcp-memory-server": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@mnemoverse/mcp-memory-server"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add mnemoverse-mcp-memory-server --command npx --arg -y --arg @mnemoverse/mcp-memory-server
# ~/.hermes/config.yaml
mcp_servers:
  mnemoverse-mcp-memory-server:
    command: "npx"
    args: ["-y", "@mnemoverse/mcp-memory-server"]
// mcp.json
{
  "mcpServers": {
    "mnemoverse-mcp-memory-server": {
      "command": "npx",
      "args": [
        "-y",
        "@mnemoverse/mcp-memory-server"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 2 Aug 26 +47
    • Provenance: unverified → fail security
    • Install scripts: unverified → pass security
    • Known CVEs: unverified → partial security
    • Malware scan: unverified → pass security
    • Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
    • Dependency health: unverified → partial functional
    • Stability: unverified → 0.20 functional
    • Maintenance: unverified → pass functional
    • Schema quality: unverified → excellent functional
    • License: unverified → pass functional
    • MCP protocol: unverified → pass functional
    • Licence: MIT functional
  • 1 Aug 26 +15
    • Tool coverage: unverified → 100 functional
  • 31 Jul 26 −22
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 −18
    • Malware scan: pass → unverified security
  • 27 Jul 26 45

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Analysed npm/@mnemoverse/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Dependencies 94 packages

94 packages in the resolved dependency tree · 94 deprecated · 29 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 9 exposed · ~1,315 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens
memory_create_room ~137

Create a SHARED memory room — a space you and OTHER people's assistants can both read and write, across Claude/ChatGPT/Cursor. Use when the user wants to share context or collaborate with someone else (e.g. 'make a room for me and Olya'). Returns the room's address; pass that address as the `domain` on memory_write/memory_read to use it. To bring someone in, call memory_invite_to_room next.

NameTypeReqDescription
descriptionstringOptional description of the room.
namestringyesRoom name, unique within your account (e.g. 'me-and-olya').

No output schema declared.

No examples provided.

memory_delete ~112

Permanently delete ONE memory by its atom_id — irreversible, the memory is gone for good. Use only when the user explicitly asks to forget something specific, or to correct a fact you stored wrongly. Get the atom_id from a memory_read result. To clear an entire topic at once, use memory_delete_domain instead. Never delete on your own initiative — require an explicit user request.

NameTypeReqDescription
atom_idstringyesThe atom_id of the memory to delete (from memory_read results — each item has an id)

No output schema declared.

No examples provided.

memory_delete_domain ~160

Permanently delete EVERY memory in one domain — irreversible, and far more destructive than memory_delete. Use only on an explicit user request to wipe a whole topic, e.g. 'forget everything about project X' or 'wipe my benchmark experiments'. First run memory_stats to confirm the exact domain name, then pass it together with confirm=true (a deliberate safety interlock). Never call this speculatively or to 'clean up' on your own — only when the user explicitly asks.

NameTypeReqDescription
confirmbooleanyesMust be exactly true to proceed. Acts as a safety interlock against accidental invocation.
domainstringyesThe domain namespace to wipe (e.g., 'project:old', 'experiments-2025'). Must match exactly.

No output schema declared.

No examples provided.

memory_feedback ~133

Report whether memories returned by memory_read were actually helpful. This is a learning signal, not a log: positive feedback raises a memory's ranking so it surfaces faster next time (across all of the user's tools), negative feedback lets it fade. Call it right after you act on (or reject) recalled memories, passing the ids from the memory_read results.

NameTypeReqDescription
atom_idsarrayyesIDs of memories to give feedback on (from memory_read results)
outcomenumberyesHow helpful was this? 1.0 = very helpful, 0 = neutral, -1.0 = harmful/wrong

No output schema declared.

No examples provided.

memory_invite_to_room ~143

Mint a one-time invite for a room you own and get a ready-to-forward message. The user sends that message to the person they want to add (any messenger); the recipient opens the link or tells THEIR assistant the code to join. Use after memory_create_room, or whenever the user says 'invite <someone>' to an existing room.

NameTypeReqDescription
expires_in_daysintegerDays until the invite expires (default 7).
room_idstringyesThe room's id (room_...), from memory_create_room.
scopestringRole the invitee gets — 'read' or 'read_write' (default read_write).

No output schema declared.

No examples provided.

memory_join_room ~87

Join a shared memory room using an invite code (starts with 'mnvr_'). Use when the user pastes an invite code or says something like 'join room with code ...'. After joining, use the returned address as the `domain` on memory_write/memory_read to read and write the shared room.

NameTypeReqDescription
codestringyesThe invite code (mnvr_...).

No output schema declared.

No examples provided.

memory_read ~202

Search your long-term memory before answering anything that may have come up before — user preferences, past decisions, project setup, people, or earlier context. This memory is shared: it persists across sessions and across every AI tool the user has connected (Claude, ChatGPT, Cursor, VS Code). ALWAYS check here first when you're unsure whether you already know something; no need to call it for general world knowledge you already hold. Returns matches ranked by relevance (semantic similarity plus learned concept associations); each result carries an id you can pass to memory_feedback or memory_delete.

NameTypeReqDescription
domainstringRestrict the search to one domain namespace (e.g. 'project:acme'); omit to search across all domains.
querystringyesNatural-language description of what you're looking for, e.g. 'database choice for the API' or 'user's preferred testing framework'.
top_kintegerMax results to return (default: 5)

No output schema declared.

No examples provided.

memory_stats ~88

Get an overview of the stored memory: total count, episodes vs consolidated prototypes, number of learned associations, the list of domains, and average quality scores. This memory is shared across all AI tools the user has connected to Mnemoverse. Use it to orient yourself, to confirm the exact domain name before a delete, or when the user asks what you remember. Read-only — changes nothing.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

memory_write ~253

Store a long-term memory that persists across sessions AND across every AI tool the user has connected to Mnemoverse (Claude, ChatGPT, Cursor, VS Code) — write once, recall everywhere. Call this PROACTIVELY the moment the user states a preference, makes a decision, or you learn a durable fact (people, roles, project setup, a lesson). Don't wait to be asked. Do NOT use it for transient chatter, secrets, or anything only relevant to the current turn. Behavior: an importance gate may filter low-value writes, so the result tells you whether the memory was stored or filtered. Write `content` as a self-contained statement that still makes sense when recalled out of context.

NameTypeReqDescription
conceptsarrayKey concepts for linking related memories (e.g. ['deploy', 'friday', 'staging'])
contentstringyesThe memory to store as a self-contained statement, e.g. 'User prefers TypeScript strict mode' or 'Decided to deploy the API on Cloudflare Workers (2026-06)'.
domainstringNamespace to organize memories (e.g. 'engineering', 'user:alice', 'project:acme')

No output schema declared.

No examples provided.