MCP.Market

mneme Record MCP server

by OnourImpram·io.github.OnourImpram/mneme·v4.1.0·3 stars
No reviews yet

Vault-native, accountable memory for Claude Code and MCP clients. Markdown is ground truth.

A92/100grade A
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
A92/100

full report

Adoption
Growing

3 stars147 downloads/wk

Reviews

Write one

Nobody has reviewed mneme Record yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

mneme Record tools (5)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • mneme_checkpoint_list

    List recent Context Continuity Engine checkpoints from the active scope,

  • mneme_health

    Report the memory index's own condition: schema version, locale profile,

  • mneme_prime

    Build a token-budgeted preflight context bundle from recent sessions and

  • mneme_propose

    Queue a redacted memory-edit proposal for the policy drain. The MCP server

  • mneme_working_set_load

    Load salience-ranked working-set items from a Context Continuity Engine

Public scan report

scanner v0.1.10 · 2026-10-29 · same rubric, same numbers if you re-run it

no findings
  • Code scan73 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 8 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 92/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How mneme Record compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
92/100
higher than 93% of 48,243 servers
Tools
5
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
3
more than 80% of 28,706 servers
Downloads a week
147
more than 70% of 12,306 servers with a package

What its tools let an agent do: 5 read

Install mneme Record in Claude Code, Cursor or VS Code

Runs npx -y mneme-mcp-server on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add mneme -- npx -y mneme-mcp-server
Add to Cursor

What the publisher says

From the mneme Record repository's README, as published. We do not edit it. Read it on GitHub

mneme Record

Vault-native memory for Claude Code. Markdown is ground truth.

Every session starts from zero. You re-explain the same architecture, the same constraints, the same decision you already settled yesterday, and the tools that promise to fix it mostly store your conversation history in opaque SQLite blobs and call an LLM every time you finish a session. The record of your own work ends up somewhere you cannot read, cannot grep, and cannot take with you.

mneme records what happened in each Claude Code session as plain markdown files in a directory you own (the vault) and indexes them with SQLite FTS5. The next session opens with a preflight block — today's headings, a git status summary, and the five most recently modified session documents — and the agent queries the index on demand through mneme_search.

Here is the file the Stop hook writes. The frontmatter, heading, and summary shape come from packages/mneme-cc-plugin/src/mnemeccplugin/hooks/stop.py and packages/mneme-core/src/mneme_core/distill/templates/summary-en.md; the contents below are illustrative.

---
id: session-2026-07-24
type: session
created: 2026-07-24T09:12:41.087213+00:00
schema_version: 1
---
# Sessions 2026-07-24

## 09:12 session a3f19c2e
transcript: `~/.claude/projects/mneme/a3f19c2e.jsonl`

**Session intent**: make the retrieval guard fail on the negative probe too

**Files touched**

- `benchmarks/retrieval/regression_guard.py`
- `benchmarks/retrieval/baseline.json`

**Tool activity** (34 events, 08:41:02 → 09:12:38)

- Edit: 11
- Bash: 9
- Read: 8

*Deterministic extractive summary (zero-LLM). Edit freely — this file is yours.*
pipx install mneme-cc-plugin && mneme install

That installs the plugin and registers the lifecycle hooks; mneme doctor verifies the result, and profiles and per-client installs are under Three-Tier Install. Claude Code registers six hook events; Codex and Antigravity map four. Any other MCP client (Kimi, Qwen, Cline, Cursor) gets the ten MCP tools through the open adapter, with no lifecycle hooks and no automatic capture.

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

mneme Record: common questions

Is mneme Record MCP server safe?
Yes, by our scan: it is graded A (92/100). Read the mneme Record safety report
How do I install mneme Record?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does mneme Record need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is mneme Record maintained?
The last commit was 15 days ago (2026-10-21). The latest release is v4.1.0.
How does mneme Record compare with other MCP servers?
safety score 92/100 (higher than 93% of 48,243 servers); tools 5 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.