Mnemoscope
NPM · @MNEMOSCOPE/MCP-SERVER
Predict context rot, sign every agent write, tier reads. Markdown-native, 100% local.
Available components
Last scanned (8 hours ago)
Scores higher than 93% of npm servers
Category Memory and Knowledge
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 → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to toonight/Mnemoscope). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 190 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability66
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 269 tokens (~67/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage69
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 8% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 3 Nov 26 0
- Stability: 0.97 → pass security
- 2 Nov 26 0
- Stability: pass → 0.97 functional
- 27 Oct 26 0
- Stability: 0.97 → pass security
- 26 Oct 26 0
- Stability: pass → 0.97 functional
- 20 Oct 26 0
- Stability: 0.97 → pass security
- 19 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
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 5 Nov 2026 · Analysed npm/@mnemoscope/mcp-server@0.2.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | toonight/Mnemoscope |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/toonight/Mnemoscope/.github/workflows/release.yml@refs/tags/v0.2.0 |
| Rekor log index | 1396707599 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:ca518c9787c4cfa87d0f5e660254322cfe7dd197af87507c7fc076635590209516549fd34f70bd7da56f43d25438e6df5a7a3afed3a9be8c87da48c8b |
Background: How many MCP packages publish verified provenance →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_tiered_read ~75
Returns a tiered (working / episodic / semantic) view of a Markdown vault, designed to be used as a compacted context substitute instead of injecting the full vault.
| Name | Type | Req | Description |
|---|---|---|---|
| episodic_max_age_days | number | – | – |
| vault_path | string | yes | – |
| working_max_age_days | number | – | – |
No output schema declared.
No examples provided.
predict_rot ~66
Compute a predictive context-rot risk score (0-100) for a Markdown vault before injecting it into an LLM. Returns the score, a breakdown of contributing factors, and the 5 highest-risk notes.
| Name | Type | Req | Description |
|---|---|---|---|
| vault_path | string | yes | Absolute path to the vault root directory. |
No output schema declared.
No examples provided.
read_journal ~40
Read the journal entries for a vault. Optionally filter by session_id.
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | string | – | – |
| vault_path | string | yes | – |
No output schema declared.
No examples provided.
record_journal ~88
Append an entry to the local signed journal of agent operations on a vault. Use this to record reads, writes, creates, or deletes performed during a session.
| Name | Type | Req | Description |
|---|---|---|---|
| content_after | string | – | – |
| content_before | string | – | – |
| op | string | yes | – |
| session_id | string | yes | – |
| target_path | string | yes | – |
| vault_path | string | yes | – |
No output schema declared.
No examples provided.
How do I install the Mnemoscope MCP server?
Mnemoscope runs locally as an npm package, launched with npx -y @mnemoscope/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @mnemoscope/mcp-server
claude mcp add toonight-mnemoscope -- npx -y @mnemoscope/mcp-server
What is the Mnemoscope MCP server?
Mnemoscope is an MCP server listed in the public MCP registry as io.github.toonight/mnemoscope. Predict context rot, sign every agent write, tier reads. Markdown-native, 100% local. This page covers its npm package (@mnemoscope/mcp-server).
Is the Mnemoscope MCP server safe to use?
Mnemoscope scores 90 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Mnemoscope MCP server expose?
Mnemoscope exposes 4 tools: predict_rot, get_tiered_read, record_journal, read_journal. Their descriptions and schemas cost roughly 269 tokens of context every time the server is loaded.
Is the Mnemoscope MCP server still maintained?
Mnemoscope is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Mnemoscope MCP server under?
Mnemoscope declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.