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.thuupx/memory-mcp-lite

NPM · MEMORY-MCP-LITE

A lightweight, structured, token-efficient local-first MCP memory server

Available components

0 this week 75 Trust /100

Last scanned (15 hours ago)

Scores higher than 51% of npm servers

Category Memory and Knowledge

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 Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects drizzle-orm 0.36.4, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 38 of 121 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency32
Schema Quality & AI Usability68
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 2193 tokens (~243/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • 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 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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 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
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

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.

  • 19 Nov 26 0
    • Stability: 0.97 → pass security
  • 18 Nov 26 0
    • Stability: pass → 0.97 functional
  • 12 Nov 26 0
    • Stability: 0.97 → pass security
  • 11 Nov 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.

  • 9 Nov 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.

  • 7 Nov 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.

  • 6 Nov 26 −3
    • Stability: pass → 0.80 functional
  • 31 Oct 26 0
    • Stability: 0.97 → pass security
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 21 Nov 2026 · Analysed npm/memory-mcp-lite@2.0.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Vulnerabilities 2 findings
ID CVE Severity Vector Fix available
GHSA-gpj5-g38j-94v9 CVE-2026-39356 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N yes
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 121 packages
Packages resolved 121
Deprecated 1
Stale 37
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 9 exposed · ~1,764 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
get_global_summary ~86

Return the user's cross-project global memory summary (coding style, recurring preferences, stable workflow conventions). USE WHEN: the request depends on durable user-level preferences that apply across projects. DO NOT USE WHEN: the question is project-specific, purely syntactic, or self-contained. RETURNS: { found, summary? } where summary has { id, title, summary, updated_at }.

Input schema present but exposes no named parameters.

NameTypeReqDescription
foundbooleanyes–
summary–yes–

No examples provided.

get_memory_detail ~141

Load the full body of a specific memory by id. USE WHEN: a search_memory_light candidate looks relevant and you need its full content / metadata. DO NOT USE WHEN: you have not identified a specific memory id, or you are tempted to call this many times in a row. LIMIT: call at most 3 times per user turn. RETURNS: { found, memory? } where memory has { id, title, summary, content, memory_type, level, importance, source, metadata, created_at, updated_at }.

NameTypeReqDescription
idstringyesMemory node id as returned by search_memory_light (e.g. 'mem_<hex>')
NameTypeReqDescription
foundbooleanyes–
memory–yes–

No examples provided.

get_project_summary ~204

Return the concise summary for the current project (architecture, key decisions, conventions). USE WHEN: the request depends on project-level context — architecture, conventions, long-term decisions, or project overview. DO NOT USE WHEN: the request is about the current task's state, global preferences, or is self-contained. CALL ORDER: prefer this before search_memory_light. Pass workspace_path OR git_root OR remote_url OR project_id so the server can identify the project. RETURNS: { project_id, found, summary? } where summary has { id, title, summary, updated_at }.

NameTypeReqDescription
git_rootstring–Absolute path to the git repository root
project_idstring–Explicit project id (skip auto-resolution when known)
remote_urlstring–Git remote URL, e.g. https://github.com/org/repo
workspace_pathstring–Absolute path to the workspace root, e.g. /Users/me/code/app
NameTypeReqDescription
foundbooleanyes–
project_idstringyes–
summary–yes–

No examples provided.

get_task_summary ~164

Return the current task summary (what was done, blockers, next steps). USE WHEN: the user asks to continue, resume, or recall recent work on a task. DO NOT USE WHEN: there is no prior task state referenced, or the request is about global / project-level context. RETURNS: { project_id, found, summary? } where summary has { id, title, summary, updated_at }.

NameTypeReqDescription
git_rootstring–Absolute path to the git repository root
project_idstring–Explicit project id
remote_urlstring–Git remote URL for the project
task_idstring–Optional task node id to scope the summary to
workspace_pathstring–Absolute path to the workspace root
NameTypeReqDescription
foundbooleanyes–
project_idstringyes–
summary–yes–

No examples provided.

remember_decision ~249

Persist a durable technical decision (architecture choice, trade-off, accepted pattern, rejected alternative). USE WHEN: the user confirms a decision that should outlive the current session. DO NOT USE WHEN: the info is a transient fact/command (use remember_fact) or raw chat log. IMPORTANCE: defaults to 0.8 — override only if the user signals otherwise. RETURNS: { project_id, memory_id }.

NameTypeReqDescription
contentstring–Optional extended rationale, trade-offs, and rejected alternatives
git_rootstring–Absolute path to the git repository root
importancenumber–0.0-1.0, defaults to 0.8 for decisions
project_idstring–Explicit project id
remote_urlstring–Git remote URL
sourcestring–Optional source pointer (file path, PR url, doc link)
summarystringyesOne-paragraph summary: what was decided and the primary reason (max 500 chars)
titlestringyesShort, specific title for the decision (max 200 chars)
workspace_pathstring–Absolute path to the workspace root
NameTypeReqDescription
memory_idstringyes–
project_idstringyes–

No examples provided.

remember_fact ~283

Persist a concise atomic memory: fact, command, gotcha, link, or convention. USE WHEN: the user gives concrete reusable info (a command, env detail, integration note, rule). DO NOT USE WHEN: the info is a major decision (use remember_decision) or a summary (use upsert_*_summary). FACT TYPES: fact | command | gotcha | link | convention | decision (prefer remember_decision for 'decision'). RETURNS: { project_id, memory_id }.

NameTypeReqDescription
contentstring–Optional extended detail or example usage
fact_typestring–Atomic memory type: fact | command | gotcha | link | convention | decision. Prefer remember_decision for 'decision'.
git_rootstring–Absolute path to the git repository root
importancenumber–0.0-1.0, defaults to the type-specific default in MemoryPolicy
project_idstring–Explicit project id
remote_urlstring–Git remote URL
sourcestring–Optional source pointer (file path, PR url, doc link)
summarystringyesConcise fact body (max 500 chars)
titlestringyesShort title for the fact (max 200 chars)
workspace_pathstring–Absolute path to the workspace root
NameTypeReqDescription
memory_idstringyes–
project_idstringyes–

No examples provided.

search_memory_light ~262

Lexical FTS5 search across atomic memories. Returns compact candidate records only — not full content. USE WHEN: the summary tools above do not provide enough context AND the request includes a concrete search phrase (command name, symbol, past event). DO NOT USE WHEN: summaries already answer the question, the query is empty/too vague, or you only need the global/project/task summary. CALL ORDER: always call summary tools first. Then follow up this tool's top 1-3 results with get_memory_detail — never dump all candidates. RETURNS: { count, results: [{ id, title, summary, memory_type, level, importance, updated_at }] }.

NameTypeReqDescription
git_rootstring–Absolute path to the git repository root
limitinteger–Max candidate results, 1-20. Defaults to 10.
project_idstring–Explicit project id
querystringyesFree-text search query — a keyword, command, or phrase
remote_urlstring–Git remote URL
scopestring–Search scope: 'project' (scoped to resolved project) or 'global' (all projects).
workspace_pathstring–Absolute path to the workspace root
NameTypeReqDescription
countintegeryes–
resultsarrayyes–

No examples provided.

upsert_project_summary ~187

Idempotently create or replace the structured project summary node. USE WHEN: architecture, conventions, or key decisions changed enough that a fresh summary is worth storing. DO NOT USE WHEN: the change is a single fact / decision (use remember_fact or remember_decision). RETURNS: { project_id, summary_id }.

NameTypeReqDescription
display_namestring–Human-readable project name (displayed to users)
git_rootstring–Absolute path to the git repository root
project_idstring–Explicit project id
remote_urlstring–Git remote URL
summarystringyesStructured project summary: stack, key decisions, conventions, architecture (max 2000 chars)
titlestringyesProject summary title, e.g. 'MyApp Project Overview'
workspace_pathstring–Absolute path to the workspace root
NameTypeReqDescription
project_idstringyes–
summary_idstringyes–

No examples provided.

upsert_task_summary ~188

Idempotently create or replace the current task summary (progress, blockers, next steps). USE WHEN: meaningful progress was made, a blocker appeared, or the plan changed and the next session must resume. DO NOT USE WHEN: the update fits better as a single fact or decision. RETURNS: { project_id, summary_id }.

NameTypeReqDescription
git_rootstring–Absolute path to the git repository root
parent_task_idstring–Optional parent task node id for nesting
project_idstring–Explicit project id
remote_urlstring–Git remote URL
summarystringyesCurrent task state: what was done, blockers, next steps (max 2000 chars)
titlestringyesShort task title, e.g. 'Implement auth middleware'
workspace_pathstring–Absolute path to the workspace root
NameTypeReqDescription
project_idstringyes–
summary_idstringyes–

No examples provided.

Install

How do I install the io.github.thuupx/memory-mcp-lite server?

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

npm · memory-mcp-lite

# add to Claude Code
claude mcp add thuupx-memory-mcp-lite -- npx -y memory-mcp-lite
Common questions

What is the io.github.thuupx/memory-mcp-lite server?

io.github.thuupx/memory-mcp-lite is listed in the public MCP registry as io.github.thuupx/memory-mcp-lite. A lightweight, structured, token-efficient local-first MCP memory server. This page covers its npm package (memory-mcp-lite).

Is the io.github.thuupx/memory-mcp-lite server safe to use?

io.github.thuupx/memory-mcp-lite scores 75 out of 100 on VerifyMCP. We recorded 2 known advisories against it as of 21 November 2026. It declares no install or post-install scripts. 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 io.github.thuupx/memory-mcp-lite server expose?

io.github.thuupx/memory-mcp-lite exposes 9 tools: get_global_summary, get_project_summary, get_task_summary, search_memory_light, get_memory_detail, and 4 more. Their descriptions and schemas cost roughly 1,764 tokens of context every time the server is loaded.

Is the io.github.thuupx/memory-mcp-lite server still maintained?

io.github.thuupx/memory-mcp-lite is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the io.github.thuupx/memory-mcp-lite server?

VerifyMCP ran 16 checks on io.github.thuupx/memory-mcp-lite, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.