Mnemoscope

Predict context rot, sign every agent write, tier reads. Markdown-native, 100% local.

Quick Install

Automated & IDE Setup

Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.

Add to Cursor Add to VS Code

Manual Client & Custom JSON ConfigExpand JSON ▾

Client Config & Setup

Choose your client or environment

Target File:~/Library/Application Support/Claude/claude_desktop_config.json

claude_desktop_config.json

{
  "mcpServers": {
    "mnemoscope": {
      "command": "npx",
      "args": [
        "-y",
        "mnemoscope"
      ]
    }
  }
}

💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.

Documentation Overview

An open-source observability layer for LLM agent memory on Markdown vaults.
Predict context rot before it happens · audit every agent write with a signed journal · tier your knowledge the way the science says you should.

_{Demo · Workflow · Tools · Quickstart · Architecture · Science}

[!NOTE] The dominant 2025–2026 narrative on X — "Markdown trips up the LLM at scale" — is partially wrong. Markdown does not trip up the LLM. Long-context loading trips up the LLM (Chroma, Context Rot, July 2025). Mnemoscope is built on that distinction.

👀 See it in action

Real output, captured from the bundled examples/demo-vault — a 13-note synthetic vault built so every rot factor moves. Reproduce locally with mnemoscope-init examples/demo-vault (full transcript: SAMPLE-OUTPUT.md).

predict_rot — score, factors, top-risk notes

predict_rot card showing rot risk 52/100, dominant factor semanticRedundancy, factor breakdown bars, and the top 5 risk notes.

mnemoscope-verify — clean run vs. tamper detection

Two verify outputs side by side: a clean run with three valid entries and exit 0, and a tampered run with one signature-mismatch FAIL and exit 1.

Full overview (click) — gauge, factors, top-risk notes, both verify states, tier counts, hash chain — all on one page

Full demo page showing every Mnemoscope view at once.

✨ What is Mnemoscope?

Mnemoscope is not another memory store. It is an instrument that sits between your LLM agent and your Markdown vault and gives you three things nobody else gives you in one tool:

🎯 Predict the rot risk of a corpus before injection, with a citation-backed score across 5 factors.
📝 Witness every read and write your agent performs, in an Ed25519-signed, hash-chained journal that detects field-level tampering, deletion, and reordering.
🧱 Tier the corpus into a working / episodic / semantic hierarchy, drawing on the 2025–2026 science instead of the GraphRAG hype.

It ships as an MCP server (Claude Code, Cursor, ChatGPT desktop, anything MCP-compatible), an Obsidian plugin, and a Claude Code PostToolUse hook. Everything runs 100% locally. No cloud. No telemetry without explicit opt-in.

🔄 How it fits your workflow

Imagine you start a brand-new project — a folder of Markdown notes you'll grow with Claude Code over the next year. Mnemoscope plugs into the lifecycle in five places:

Code

   [create project]
        │
        ▼
   mnemoscope-init                     ◄─── 1× at the very start
        │                                   creates .mnemoscope/, generates Ed25519 keypair
        ▼
   ┌───────────────────────────────────────────────────────────┐
   │  [you work with Claude Code on the vault]                 │
   │                                                           │
   │   predict_rot       ──┐                                   │
   │                       ├─►  on demand (or before sessions) │
   │   get_tiered_read   ──┘    "is the vault healthy?"        │
   │                            "what should the agent read?"  │
   │                                                           │
   │   PostToolUse hook  ────►  passive, on every Write/Edit   │
   │                            "what did the agent just do?"  │
   └───────────────────────────────────────────────────────────┘
        │
        ▼
   mnemoscope-verify                   ◄─── on demand, or in CI
                                            "has anyone tampered?"

Phase	Tool / command	When to use it	What you get
1. Bootstrap	`mnemoscope-init`	Once, at project creation	`.mnemoscope/` + per-vault Ed25519 keypair
2. Predict	`predict_rot` (MCP tool)	Before injecting a vault into the LLM	A 0–100 risk score + factor breakdown + top-risk notes
3. Compact	`get_tiered_read` (MCP tool)	When the vault grows past your model's effective context	Working / episodic / semantic split
4. Witness	`mnemoscope-record-hook` (Claude Code PostToolUse hook)	Wired once in `~/.claude/settings.json`, then passive	Every agent write becomes a signed journal entry
5. Audit	`mnemoscope-verify`	Any time, or as a pre-commit / CI step	Exit 0 if all entries verify, exit 1 if tampered

🛠️ The four MCP tools

Tool	Input	What it returns
`predict_rot`	`vault_path`	Score 0–100, dominant factor, full factor breakdown, top 5 risk notes, vault stats
`get_tiered_read`	`vault_path`, optional age thresholds	Note paths grouped into `working` / `episodic` / `semantic`
`record_journal`	`vault_path`, `session_id`, `op`, `target_path`, optional content	The signed entry, including its `sig`, `keyFingerprint`, and `prevHash`
`read_journal`	`vault_path`, optional `session_id`	All journal entries, or a single session's entries

Example — `predict_rot` on a real vault

config.json

{
  "rot_risk": 41,
  "dominant_factor": "tokenVolume",
  "factors": {
    "tokenVolume": 100, "semanticRedundancy": 0,
    "distractorDensity": 2.65, "structuralCoherence": 100, "freshnessSpread": 0
  },
  "top_risk_notes": [
    { "relPath": "brainstorms/.../transcript.md", "approxTokens": 13439, "reason": "very large note" },
    { "relPath": "brainstorms/.../sylvie-signaux.md", "approxTokens": 12605, "reason": "very large note" }
  ],
  "vault_stats": { "noteCount": 113, "approxTokens": 506823 },
  "baseline_model": "v0-heuristic",
  "version": "0.2.0"
}

🚀 Quickstart

bash

git clone https://github.com/toonight/Mnemoscope
cd Mnemoscope
npm install
npm run build
npm test                           # 47 tests across core + mcp-server
npm audit                          # 0 vulnerabilities

# Make the CLI binaries available on your PATH
npm link --workspace @mnemoscope/cli

Bootstrap a vault

bash

mnemoscope-init /path/to/your/vault
# → state dir, Ed25519 keypair, fingerprint

Add .mnemoscope/ to your vault's .gitignore — the per-vault private key must never be committed.

Connect the MCP server to Claude Code (or Cursor / any MCP client)

json

// ~/.claude/settings.json
{
  "mcpServers": {
    "mnemoscope": {
      "command": "node",
      "args": ["/absolute/path/to/Mnemoscope/packages/mcp-server/dist/index.js"]
    }
  }
}

The four tools (predict_rot, get_tiered_read, record_journal, read_journal) become available to the agent immediately.

(Optional) wire the auto-journal hook

Asking the agent to call record_journal on every write is a recipe for forgetting. Wire the bundled hook instead:

json

// ~/.claude/settings.json
{
  "hooks": {
    "PostToolUse": [
      {
        "matcher": "Write|Edit|MultiEdit",
        "hooks": [{ "type": "command", "command": "mnemoscope-record-hook" }]
      }
    ]
  }
}

The hook resolves the vault root via MNEMOSCOPE_VAULT_PATH or by walking up to the closest .mnemoscope/ directory. It never blocks the tool call: any internal error is caught, logged to stderr, and the process exits 0. Full setup including safety properties: docs/claude-code-hook.md.

Verify the journal

bash

mnemoscope-verify /path/to/vault
# ok    2026-04-26T19:42:13.001Z  write  /vault/notes/foo.md
# ok    2026-04-26T19:43:01.220Z  write  /vault/notes/bar.md
# 2 entries; 2 valid; 0 invalid

mnemoscope-verify exits non-zero on any of:

field-level tampering (signature mismatch),
deletion or reordering (prevHash chain break),
entries signed by a key the current vault does not own.

(Optional) back up the per-vault private key

If you lose <vault>/.mnemoscope/keys/ed25519.key, the journal becomes unverifiable. The bundled backup CLIs encrypt the key with a passphrase (scrypt + AES-256-GCM, no extra deps) and let you restore it later:

bash

mnemoscope-backup-key /path/to/vault /path/to/off-vault-backup.enc.json
# … prompts for a passphrase, writes chmod 0600 …

Read the full README →View source on GitHub →

Related MCP Servers

View all in Developer Tools View all alternatives

Reviews

No reviews yet — be the first to share how this listing worked for you.

Frequently Asked Questions about Mnemoscope

Add the following block to your claude_desktop_config.json under mcpServers: "mcpServers": { "mnemoscope": { "command": "npx", "args": ["-y", "Mnemoscope"] } }

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:

Live Dynamic SVG Preview

Markdown (GitHub README)

[![AllMCPs](https://allmcps.com/api/badge/mnemoscope?style=directory)](https://allmcps.com/mcp/mnemoscope)

HTML Embed

<a href="https://allmcps.com/mcp/mnemoscope"><img src="https://allmcps.com/api/badge/mnemoscope?style=directory" alt="Mnemoscope on AllMCPs" /></a>

Technical Specs & Signals

CategoryDeveloper Tools

27Quality signal: Emerging · 27/100How this signal is calculated ▾

Server availabilityNot measured

Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.

Verified ownership8/20

Documentation & tools11/30

Adoption & activity1/15

Community engagement0/10

A guidance signal from public completeness & health data — not a user rating. New listings start lower and rise as they add docs, get verified, and grow adoption. Signals we can't observe for a listing are skipped, not counted against it.

★ Featured

Moxie Docs MCP

MCP & Agent Skills for Automated Documentation, and codebase conventions + context

Explore Server →

Own this project?

This directory is pre-filled from public sources. Claim via GitHub README, site badge, or DNS TXT to unlock edit access and the Official badge and attach your website — proof is checked automatically, then reviewed by our team.

Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.

Claim & get free dofollow

Share & Embed

Add our SVG badge (dark/light directory styles) or embeddable widget to your site.

Explore more

More in 💻 Developer Tools →Best MCP servers for Developers →Alternatives to Mnemoscope →Install in Claude Desktop Install in Cursor Install in VS Code

Mnemoscope

Predict context rot, sign every agent write, tier reads. Markdown-native, 100% local.

Quick Install

Automated & IDE Setup

Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.

Add to Cursor Add to VS Code

Manual Client & Custom JSON ConfigExpand JSON ▾

Client Config & Setup

Choose your client or environment

Target File:~/Library/Application Support/Claude/claude_desktop_config.json

claude_desktop_config.json

{
  "mcpServers": {
    "mnemoscope": {
      "command": "npx",
      "args": [
        "-y",
        "mnemoscope"
      ]
    }
  }
}

💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.

Documentation Overview

_{Demo · Workflow · Tools · Quickstart · Architecture · Science}

[!NOTE] The dominant 2025–2026 narrative on X — "Markdown trips up the LLM at scale" — is partially wrong. Markdown does not trip up the LLM. Long-context loading trips up the LLM (Chroma, Context Rot, July 2025). Mnemoscope is built on that distinction.

👀 See it in action

predict_rot — score, factors, top-risk notes

mnemoscope-verify — clean run vs. tamper detection

Full overview (click) — gauge, factors, top-risk notes, both verify states, tier counts, hash chain — all on one page

✨ What is Mnemoscope?

Mnemoscope is not another memory store. It is an instrument that sits between your LLM agent and your Markdown vault and gives you three things nobody else gives you in one tool:

🎯 Predict the rot risk of a corpus before injection, with a citation-backed score across 5 factors.
📝 Witness every read and write your agent performs, in an Ed25519-signed, hash-chained journal that detects field-level tampering, deletion, and reordering.
🧱 Tier the corpus into a working / episodic / semantic hierarchy, drawing on the 2025–2026 science instead of the GraphRAG hype.

🔄 How it fits your workflow

Imagine you start a brand-new project — a folder of Markdown notes you'll grow with Claude Code over the next year. Mnemoscope plugs into the lifecycle in five places:

Code

   [create project]
        │
        ▼
   mnemoscope-init                     ◄─── 1× at the very start
        │                                   creates .mnemoscope/, generates Ed25519 keypair
        ▼
   ┌───────────────────────────────────────────────────────────┐
   │  [you work with Claude Code on the vault]                 │
   │                                                           │
   │   predict_rot       ──┐                                   │
   │                       ├─►  on demand (or before sessions) │
   │   get_tiered_read   ──┘    "is the vault healthy?"        │
   │                            "what should the agent read?"  │
   │                                                           │
   │   PostToolUse hook  ────►  passive, on every Write/Edit   │
   │                            "what did the agent just do?"  │
   └───────────────────────────────────────────────────────────┘
        │
        ▼
   mnemoscope-verify                   ◄─── on demand, or in CI
                                            "has anyone tampered?"

Phase	Tool / command	When to use it	What you get
1. Bootstrap	`mnemoscope-init`	Once, at project creation	`.mnemoscope/` + per-vault Ed25519 keypair
2. Predict	`predict_rot` (MCP tool)	Before injecting a vault into the LLM	A 0–100 risk score + factor breakdown + top-risk notes
3. Compact	`get_tiered_read` (MCP tool)	When the vault grows past your model's effective context	Working / episodic / semantic split
4. Witness	`mnemoscope-record-hook` (Claude Code PostToolUse hook)	Wired once in `~/.claude/settings.json`, then passive	Every agent write becomes a signed journal entry
5. Audit	`mnemoscope-verify`	Any time, or as a pre-commit / CI step	Exit 0 if all entries verify, exit 1 if tampered

🛠️ The four MCP tools

Tool	Input	What it returns
`predict_rot`	`vault_path`	Score 0–100, dominant factor, full factor breakdown, top 5 risk notes, vault stats
`get_tiered_read`	`vault_path`, optional age thresholds	Note paths grouped into `working` / `episodic` / `semantic`
`record_journal`	`vault_path`, `session_id`, `op`, `target_path`, optional content	The signed entry, including its `sig`, `keyFingerprint`, and `prevHash`
`read_journal`	`vault_path`, optional `session_id`	All journal entries, or a single session's entries

Example — `predict_rot` on a real vault

config.json

{
  "rot_risk": 41,
  "dominant_factor": "tokenVolume",
  "factors": {
    "tokenVolume": 100, "semanticRedundancy": 0,
    "distractorDensity": 2.65, "structuralCoherence": 100, "freshnessSpread": 0
  },
  "top_risk_notes": [
    { "relPath": "brainstorms/.../transcript.md", "approxTokens": 13439, "reason": "very large note" },
    { "relPath": "brainstorms/.../sylvie-signaux.md", "approxTokens": 12605, "reason": "very large note" }
  ],
  "vault_stats": { "noteCount": 113, "approxTokens": 506823 },
  "baseline_model": "v0-heuristic",
  "version": "0.2.0"
}

🚀 Quickstart

bash

git clone https://github.com/toonight/Mnemoscope
cd Mnemoscope
npm install
npm run build
npm test                           # 47 tests across core + mcp-server
npm audit                          # 0 vulnerabilities

# Make the CLI binaries available on your PATH
npm link --workspace @mnemoscope/cli

Bootstrap a vault

bash

mnemoscope-init /path/to/your/vault
# → state dir, Ed25519 keypair, fingerprint

Add .mnemoscope/ to your vault's .gitignore — the per-vault private key must never be committed.

Connect the MCP server to Claude Code (or Cursor / any MCP client)

json

// ~/.claude/settings.json
{
  "mcpServers": {
    "mnemoscope": {
      "command": "node",
      "args": ["/absolute/path/to/Mnemoscope/packages/mcp-server/dist/index.js"]
    }
  }
}

The four tools (predict_rot, get_tiered_read, record_journal, read_journal) become available to the agent immediately.

(Optional) wire the auto-journal hook

Asking the agent to call record_journal on every write is a recipe for forgetting. Wire the bundled hook instead:

json

// ~/.claude/settings.json
{
  "hooks": {
    "PostToolUse": [
      {
        "matcher": "Write|Edit|MultiEdit",
        "hooks": [{ "type": "command", "command": "mnemoscope-record-hook" }]
      }
    ]
  }
}

Verify the journal

bash

mnemoscope-verify /path/to/vault
# ok    2026-04-26T19:42:13.001Z  write  /vault/notes/foo.md
# ok    2026-04-26T19:43:01.220Z  write  /vault/notes/bar.md
# 2 entries; 2 valid; 0 invalid

mnemoscope-verify exits non-zero on any of:

field-level tampering (signature mismatch),
deletion or reordering (prevHash chain break),
entries signed by a key the current vault does not own.

(Optional) back up the per-vault private key

bash

mnemoscope-backup-key /path/to/vault /path/to/off-vault-backup.enc.json
# … prompts for a passphrase, writes chmod 0600 …

Read the full README →View source on GitHub →

Related MCP Servers

View all in Developer Tools View all alternatives

Reviews

No reviews yet — be the first to share how this listing worked for you.

Frequently Asked Questions about Mnemoscope

Add the following block to your claude_desktop_config.json under mcpServers: "mcpServers": { "mnemoscope": { "command": "npx", "args": ["-y", "Mnemoscope"] } }

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:

Live Dynamic SVG Preview

Markdown (GitHub README)

[![AllMCPs](https://allmcps.com/api/badge/mnemoscope?style=directory)](https://allmcps.com/mcp/mnemoscope)

HTML Embed

<a href="https://allmcps.com/mcp/mnemoscope"><img src="https://allmcps.com/api/badge/mnemoscope?style=directory" alt="Mnemoscope on AllMCPs" /></a>

Technical Specs & Signals

CategoryDeveloper Tools

27Quality signal: Emerging · 27/100How this signal is calculated ▾

Server availabilityNot measured

Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.

Verified ownership8/20

Documentation & tools11/30

Adoption & activity1/15

Community engagement0/10

★ Featured

Moxie Docs MCP

MCP & Agent Skills for Automated Documentation, and codebase conventions + context

Explore Server →

Own this project?

Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.

Claim & get free dofollow

Share & Embed

Add our SVG badge (dark/light directory styles) or embeddable widget to your site.

Explore more

More in 💻 Developer Tools →Best MCP servers for Developers →Alternatives to Mnemoscope →Install in Claude Desktop Install in Cursor Install in VS Code

Mnemoscope

Quick Install

Client Config & Setup

Documentation Overview

👀 See it in action

✨ What is Mnemoscope?

🔄 How it fits your workflow

🛠️ The four MCP tools

Example — predict_rot on a real vault

🚀 Quickstart

Bootstrap a vault

Connect the MCP server to Claude Code (or Cursor / any MCP client)

(Optional) wire the auto-journal hook

Verify the journal

(Optional) back up the per-vault private key

Related MCP Servers

Reviews

Frequently Asked Questions about Mnemoscope

AllMCPs Directory Badge

Technical Specs & Signals

Moxie Docs MCP

Own this project?

Share & Embed

Explore more

Mnemoscope

Quick Install

Client Config & Setup

Documentation Overview

👀 See it in action

✨ What is Mnemoscope?

🔄 How it fits your workflow

🛠️ The four MCP tools

Example — predict_rot on a real vault

🚀 Quickstart

Bootstrap a vault

Connect the MCP server to Claude Code (or Cursor / any MCP client)

(Optional) wire the auto-journal hook

Verify the journal

(Optional) back up the per-vault private key

Related MCP Servers

Reviews

Frequently Asked Questions about Mnemoscope

AllMCPs Directory Badge

Technical Specs & Signals

Moxie Docs MCP

Own this project?

Share & Embed

Explore more

Example — `predict_rot` on a real vault

Example — `predict_rot` on a real vault