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

io.github.MarcelRoozekrans/longterm-memory

NPM · LONGTERM-MEMORY-MCP

A fully local MCP server for long-term memory with semantic search

Available components

0 this week 0 Trust /100

Last scanned (20 hours ago)

Scores higher than 0% of npm servers

Category Memory and Knowledge

Recent critical change

Known CVEs (1 Nov 2026). See the changelog before you install this server.

Trust breakdown (7 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 → Why this is hard to score →

Supply Chain Security73
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to MarcelRoozekrans/LongtermMemory-MCP). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 4 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability76
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 788 tokens (~71/item across 11 items; 11 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
  • Stability observed for 13 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
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_memory" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 11 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
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.

  • 1 Nov 26 −73
    • Known CVEs: unverified → fail ▼ critical
    • Score status: scored → failed ▼ critical
    • Dependency health: unverified → 0.83 ▲ functional
  • 31 Oct 26 +73
    • Known CVEs: fail → unverified ▼ security
    • Malware scan: unverified → pass ▲ security
    • Dependency health: 0.83 → unverified ▼ functional
    • Score status: failed → scored ▲ functional
    • Package version: 1.6.0 → 1.6.1 functional
  • 30 Oct 26 0
    • Malware scan: pass → unverified ▼ security
    • Package version: 1.5.0 → 1.6.0 functional
  • 22 Oct 26 0

    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 4 Nov 2026 · Analysed npm/longterm-memory-mcp@1.6.1

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 MarcelRoozekrans/LongtermMemory-MCP
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/MarcelRoozekrans/LongtermMemory-MCP/.github/workflows/release-please.yml@refs/heads/main
Rekor log index 3608705949
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:00e2b4ff3a6be013fa6597fdb80c32f8ad2af6f29cf822beb990793ae2cf4102495a2efcfed90d1764c09056945ef45e0a28ea2f0067ee04bb8363351

Background: How many MCP packages publish verified provenance →

Vulnerabilities 14 findings
ID CVE Severity Vector Fix available
GHSA-2pr8-phx7-x9h3 CVE-2026-44294 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L yes
GHSA-66ff-xgx4-vchm CVE-2026-44293 high yes
GHSA-685m-2w69-288q CVE-2026-44289 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-75px-5xx7-5xc7 CVE-2026-44291 high CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H yes
GHSA-f38q-mgvj-vph7 CVE-2026-54269 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L yes
GHSA-fx83-v9x8-x52w CVE-2026-44292 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N yes
GHSA-jggg-4jg4-v7c6 CVE-2026-45740 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L yes
GHSA-jvwf-75h9-cwgg CVE-2026-44290 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-q6x5-8v7m-xcrf CVE-2026-44288 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N yes
GHSA-wcpc-wj8m-hjx6 CVE-2026-48712 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-xq3m-2v4x-88gg CVE-2026-41242 critical CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H yes
GHSA-f88m-g3jw-g9cj CVE-2026-114113 high yes
GHSA-rgj7-g3m4-5g8c CVE-2026-114112 high yes
GHSA-wq5f-xc86-pv6w CVE-2026-114111 high yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 169 packages
Packages resolved 169
Deprecated 1
Stale 60
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 11 exposed · ~788 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. 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 →

Tool Tokens
create_backup ~23

Create a manual backup of the memory database and export all memories as JSON.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

delete_all_memories ~32

Delete ALL stored memories. This action is irreversible. Only use when the user explicitly asks to clear all memories.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

delete_memory ~48

Delete a specific memory by its ID. Only delete when the user explicitly requests it or when a memory is confirmed outdated or incorrect.

NameTypeReqDescription
idstringyesThe UUID of the memory to delete

No output schema declared.

No examples provided.

get_all_memories ~63

Retrieve all stored memories, ordered by most recent first. Results are paginated.

NameTypeReqDescription
limitinteger–Maximum number of memories to return (default: 50)
offsetinteger–Number of memories to skip for pagination (default: 0)

No output schema declared.

No examples provided.

memory_stats ~21

Get statistics about the memory store — total count and database location.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

save_memory ~188

Save information to long-term memory. The content will be embedded locally and indexed for semantic search. Use this to store facts, decisions, preferences, or any context worth remembering across sessions. Text inside <private>…</private> is removed before storing; content that looks like a secret (tokens, keys, passwords) is rejected.

NameTypeReqDescription
contentstringyesThe text content to store in memory
importancenumber–Importance level 1-10 (default: 5). Higher = more resistant to decay
memory_typestring–Memory category (default: general). Affects decay rate
metadataobject–Optional key-value metadata to attach to this memory (e.g. { "topic": "auth", "project": "api" })
tagsarray–Optional tags for categorization (e.g. ["personal", "preference"])

No output schema declared.

No examples provided.

search_by_date_range ~97

Find memories created within a specific date range. Use ISO date format.

NameTypeReqDescription
date_fromstringyesStart date in ISO format (e.g. "2026-01-01" or "2026-01-01T00:00:00Z")
date_tostring–End date in ISO format (defaults to now)
limitinteger–Maximum number of results (default: 50)

No output schema declared.

No examples provided.

search_by_tags ~60

Find memories that match any of the provided tags. Returns memories ordered by importance.

NameTypeReqDescription
limitinteger–Maximum number of results (default: 20)
tagsarrayyesTags to search for — matches memories containing ANY of these tags

No output schema declared.

No examples provided.

search_by_type ~60

Search memories by category type (e.g. fact, preference, conversation). Returns memories ordered by importance.

NameTypeReqDescription
limitinteger–Maximum number of results (default: 20)
memory_typestringyesThe memory type to filter by

No output schema declared.

No examples provided.

search_memory ~88

Search long-term memory using semantic similarity. The query is embedded locally and compared against all stored memories using cosine similarity.

NameTypeReqDescription
limitinteger–Maximum number of results to return (default: 5)
querystringyesNatural language search query describing what you're looking for
thresholdnumber–Minimum similarity score threshold, 0-1 (default: 0.3)

No output schema declared.

No examples provided.

update_memory ~108

Update an existing memory. Can modify content (triggers re-embedding), metadata, tags, importance, or memory type.

NameTypeReqDescription
contentstring–New text content (triggers re-embedding)
idstringyesThe UUID of the memory to update
importancenumber–New importance level 1-10
memory_typestring–New memory category
metadataobject–New metadata object
tagsarray–New tags array

No output schema declared.

No examples provided.

Install

How do I install the io.github.MarcelRoozekrans/longterm-memory MCP server?

io.github.MarcelRoozekrans/longterm-memory runs locally as an npm package, launched with npx -y longterm-memory-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · longterm-memory-mcp

# add to Claude Code
claude mcp add marcelroozekrans-longterm-memory -- npx -y longterm-memory-mcp
Common questions

What is the io.github.MarcelRoozekrans/longterm-memory MCP server?

io.github.MarcelRoozekrans/longterm-memory is an MCP server listed in the public MCP registry as io.github.MarcelRoozekrans/longterm-memory. A fully local MCP server for long-term memory with semantic search. This page covers its npm package (longterm-memory-mcp).

What tools does the io.github.MarcelRoozekrans/longterm-memory MCP server expose?

io.github.MarcelRoozekrans/longterm-memory exposes 11 tools: save_memory, search_memory, get_all_memories, update_memory, search_by_type, and 6 more. Their descriptions and schemas cost roughly 788 tokens of context every time the server is loaded.

Is the io.github.MarcelRoozekrans/longterm-memory MCP server still maintained?

io.github.MarcelRoozekrans/longterm-memory is still listed as active in the MCP registry. We last reached this channel on 4 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 io.github.MarcelRoozekrans/longterm-memory MCP server under?

io.github.MarcelRoozekrans/longterm-memory declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.