Mnemoscope

io.github.toonightPublished by GitHub account toonightv0.2.0Updated Oct 24, 2026

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

VerifiedSTDIODesktop onlyFiles & StorageKnowledge & Memory

Overview

AI-generated overview

A local MCP server that scores context rot in a Markdown vault, splits notes into freshness tiers, and keeps a signed journal of agent reads and writes.

What you can do
Score a vault for context-rot risk, with a 0–100 score, dominant factor, factor breakdown and top risk notes, plus vault stats and token estimates. Split a vault into working, episodic and semantic tiers by note freshness, with optional age thresholds. Record signed journal entries for read, write, create and delete operations, returning the signature, key fingerprint and previous hash. Read back all journal entries or those of a single session.
When to use it
Useful when an assistant works over a local Markdown or Obsidian-style vault and you want to gauge how much context is degrading, decide which notes to read first by freshness, and keep a tamper-evident record of what the agent touched.
Requirements
Runs locally over stdio as an npm package, installed globally or via npx, so Node.js is needed. The journal tools need an Ed25519 keypair in the vault, created with the companion CLI or the Obsidian plugin before first use. No accounts, API keys or environment variables are declared.
Before you install
The journal tools write signed entries into the vault, so point them at the right vault path. Journal signing depends on a vault keypair; entries signed by a key the vault does not own fail verification. The optional timestamp CLI sends only a signature digest to a public calendar, never vault content.

Installation

In SourceWeft

  1. Open Mnemoscope in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

@mnemoscope/mcp-server

MCP server exposing Mnemoscope's context-rot scoring, tiered reading, and signed journal tools to any Model Context Protocol–compatible client (Claude Code, Cursor, ChatGPT desktop, anything that speaks MCP over stdio).

100% local. No cloud. No telemetry. Apache-2.0.

Install

bash
npm install -g @mnemoscope/mcp-server# the `mnemoscope-mcp` binary is now on your PATH

Or run via npx without a global install:

bash
npx -y @mnemoscope/mcp-server

Connect to Claude Code

jsonc
// ~/.claude/settings.json{  "mcpServers": {    "mnemoscope": {      "command": "npx",      "args": ["-y", "@mnemoscope/mcp-server"]    }  }}

Restart Claude Code. The four tools below are discovered automatically.

Tools

ToolInputWhat it returns
predict_rotvault_path0–100 risk score, dominant factor, full factor breakdown, top-5 risk notes, vault stats
get_tiered_readvault_path, optional working_max_age_days, episodic_max_age_daysWorking / episodic / semantic split of the vault by freshness
record_journalvault_path, session_id, op (read/write/create/delete), target_path, optional contentThe signed entry, including its sig, keyFingerprint, and prevHash
read_journalvault_path, optional session_idAll journal entries, or a single session's

Example — predict_rot

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" }  ],  "vault_stats": { "noteCount": 113, "approxTokens": 506823 },  "baseline_model": "v0-heuristic",  "version": "0.1.0"}

Bootstrap a vault

Before the journal tools work the vault needs an Ed25519 keypair. The companion @mnemoscope/cli ships mnemoscope-init for that:

bash
npx -p @mnemoscope/cli mnemoscope-init /path/to/your/vault

The auto-onboarding modal in the Obsidian plugin does the same on first launch.

Verify the journal

bash
npx -p @mnemoscope/cli mnemoscope-verify /path/to/your/vault

Exits non-zero on field tampering, hash-chain break, or entries signed by a key the current vault does not own.

What this server does NOT do

  • It does not store or transmit your vault content. All reads are local; all writes are local.
  • It does not call any external service. (The optional mnemoscope-timestamp CLI in @mnemoscope/cli POSTs only a SHA-256 digest of each journal entry's signature to a public OpenTimestamps calendar — never any vault content.)
  • It does not replace a memory store. It is an instrument for one — see the README for the comparison with Letta, Mem0, Zep, Cognee, MemPalace, and Smart Connections.

Repo + docs

License

Apache-2.0.

Source: packages/mcp-server/README.md at commit 914e15a

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.2.0LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts