io.github.zamansheikh/memory-lean
NPM · MEMORY-LEAN
Token-lean memory for AI agents: a knowledge graph searched cheaply. Drop-in for server-memory.
Available components
Last scanned (20 hours ago)
Scores higher than 87% 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 Security100
- 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
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to zamansheikh/memory-lean). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 18 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability60
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 497 tokens (~45/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 Management70
- Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage80
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 40% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_entities" 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
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 0
- Security disclosure: unverified → fail ▼ functional
- 1 Nov 26 +1
- Security disclosure: fail → unverified ▼ functional
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 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 4 Nov 2026 · Analysed npm/memory-lean@1.5.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 | zamansheikh/memory-lean |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/zamansheikh/memory-lean/.github/workflows/publish.yml@refs/tags/v1.5.0 |
| Rekor log index | 3279444551 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:345fec0d9d26d232304739a546bc955461100fc1fc7a05f046a63350781874a859e9d57173ac6f354300ace6f6756bb1d415f4509f06a8f0a0bd75a4b |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
add_observations ~61
Add observations to existing entities. One fact each, at most 300 characters. Replace stale facts with delete_observations rather than appending corrections. Entities over 15 observations have their oldest dated ones moved to archive/.
| Name | Type | Req | Description |
|---|---|---|---|
| observations | array | yes | – |
No output schema declared.
No examples provided.
archived_observations ~76
List the observations of an entity that were moved to archive/, oldest first. Pass 'restore' with exact texts to move them back onto the entity.
| Name | Type | Req | Description |
|---|---|---|---|
| entityName | string | yes | – |
| query | string | – | Only archived observations containing every term |
| restore | array | – | Exact texts to move back onto the entity |
No output schema declared.
No examples provided.
create_entities ~36
Create entities; existing names are skipped. Each observation must be one fact of at most 300 characters.
| Name | Type | Req | Description |
|---|---|---|---|
| entities | array | yes | – |
No output schema declared.
No examples provided.
create_relations ~37
Create relations (active voice, e.g. depends_on, blocks, applies_to); duplicates are skipped.
| Name | Type | Req | Description |
|---|---|---|---|
| relations | array | yes | – |
No output schema declared.
No examples provided.
delete_entities ~24
Delete entities and every relation touching them.
| Name | Type | Req | Description |
|---|---|---|---|
| entityNames | array | yes | – |
No output schema declared.
No examples provided.
delete_observations ~28
Delete specific observations (exact text) from entities.
| Name | Type | Req | Description |
|---|---|---|---|
| deletions | array | yes | – |
No output schema declared.
No examples provided.
delete_relations ~20
Delete specific relations.
| Name | Type | Req | Description |
|---|---|---|---|
| relations | array | yes | – |
No output schema declared.
No examples provided.
open_nodes ~28
Return full entities by exact name, with every relation touching them.
| Name | Type | Req | Description |
|---|---|---|---|
| names | array | yes | – |
No output schema declared.
No examples provided.
read_graph ~45
Index of the graph: entity names grouped by type, with observation counts. Does not return observations; use open_nodes for those.
| Name | Type | Req | Description |
|---|---|---|---|
| entityType | string | – | Only this type |
No output schema declared.
No examples provided.
rename_entity ~47
Rename an entity, keeping its observations and every relation touching it. Fails if the new name is taken.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Current name |
| newName | string | yes | – |
No output schema declared.
No examples provided.
search_nodes ~95
Find entities. Every whitespace-separated term must appear in the name, type, an observation, or the type of a relation touching the entity (case-insensitive). Returns a ranked list of names with counts and matching snippets, at most 'limit' (default 10); use open_nodes for full entities.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max results (default 10, max 50) |
| query | string | yes | Search terms |
No output schema declared.
No examples provided.
How do I install the io.github.zamansheikh/memory-lean MCP server?
io.github.zamansheikh/memory-lean runs locally as an npm package, launched with npx -y memory-lean. 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-lean
claude mcp add zamansheikh-memory-lean -- npx -y memory-lean
What is the io.github.zamansheikh/memory-lean MCP server?
io.github.zamansheikh/memory-lean is an MCP server listed in the public MCP registry as io.github.zamansheikh/memory-lean. Token-lean memory for AI agents: a knowledge graph searched cheaply. Drop-in for server-memory. This page covers its npm package (memory-lean).
Is the io.github.zamansheikh/memory-lean MCP server safe to use?
io.github.zamansheikh/memory-lean scores 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 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 io.github.zamansheikh/memory-lean MCP server expose?
io.github.zamansheikh/memory-lean exposes 11 tools: search_nodes, open_nodes, read_graph, create_entities, create_relations, and 6 more. Their descriptions and schemas cost roughly 497 tokens of context every time the server is loaded.
Is the io.github.zamansheikh/memory-lean MCP server still maintained?
io.github.zamansheikh/memory-lean 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.zamansheikh/memory-lean MCP server under?
io.github.zamansheikh/memory-lean declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.