Living Memory
NPM · @NATURE-LABS/LME-MCP · 2 COMPONENTS · SCANNED OCT 8
An MCP memory server. One memory your agents share — across models, devices and apps.
Available components
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
- Known CVEs were checked across the 93 of 94 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Dependency health was assessed across the 93 of 94 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 5 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability74
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 699 tokens (~174/item across 4 items; 4 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 Management87
- Stability observed for 26 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 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 5 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
How do I install the Living Memory MCP server?
Living Memory runs locally as an npm package, launched with npx -y @nature-labs/lme-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 · @nature-labs/lme-mcp
claude mcp add to-viibe-living-memory -- npx -y @nature-labs/lme-mcp
{
"mcpServers": {
"to-viibe-living-memory": {
"command": "npx",
"args": [
"-y",
"@nature-labs/lme-mcp"
]
}
}
} {
"servers": {
"to-viibe-living-memory": {
"command": "npx",
"args": [
"-y",
"@nature-labs/lme-mcp"
]
}
}
} codex mcp add to-viibe-living-memory -- npx -y @nature-labs/lme-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"to-viibe-living-memory": {
"type": "local",
"command": [
"npx",
"-y",
"@nature-labs/lme-mcp"
],
"enabled": true
}
}
} openclaw mcp add to-viibe-living-memory --command npx --arg -y --arg @nature-labs/lme-mcp
mcp_servers:
to-viibe-living-memory:
command: "npx"
args: ["-y", "@nature-labs/lme-mcp"] {
"McpServers": {
"to-viibe-living-memory": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@nature-labs/lme-mcp"
]
}
}
} assistant mcp add to-viibe-living-memory -t stdio -c npx -a -y @nature-labs/lme-mcp
{
"mcpServers": {
"to-viibe-living-memory": {
"command": "npx",
"args": [
"-y",
"@nature-labs/lme-mcp"
]
}
}
} 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.
- 8 Oct 26 −1
No change was recorded against any check on this day. Stability & Change Management went from 97 to 87.
- 3 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Sept 26 −3
- Stability: pass → 0.80 functional
- 28 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 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 8 Oct 2026 · Analysed npm/@nature-labs/lme-mcp@0.1.2
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 →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 31 |
| Tree resolution | Partial |
The dependency tree was only partially resolved, so these counts may be incomplete.
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 →
memory_add Remember a fact ~103
Store a durable fact, preference, decision, or correction so FUTURE sessions remember it. Call this whenever the user states something worth carrying forward — a preference, a project fact, a decision, a correction — without being asked. Memory persists across sessions and processes.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The fact to remember, as a short natural-language statement |
| importance | number | – | 0–10, default 7 |
| tags | array | – | optional tags |
No output schema declared.
No examples provided.
memory_forget Forget a memory ~95
DESTRUCTIVE. Deletes EVERY memory whose content contains the query as a case-insensitive substring — not semantic, not a single-item delete, and there is no undo. A short query deletes broadly. Use only when the user corrects a stored fact or explicitly asks you to forget something, and prefer a long distinctive phrase; check memory_state first if unsure.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Text to match against memories to delete |
No output schema declared.
No examples provided.
memory_search Recall relevant memory ~75
Recall what you already know before answering. Call this at the START of a session, and whenever the user refers to past context, their preferences, or the project history. Returns relevant memories via MMR retrieval (not a text match). If unsure whether you know something, search first.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | What to recall |
No output schema declared.
No examples provided.
memory_state Memory status ~80
Summarize what is currently in memory: counts plus the most recently stored facts. Reads the store directly — no embedding call, no network. Use to orient yourself at session start, or when the user asks what you remember. (selfFacets is always 0: this server does not run the engine's consolidation pass, so crystallization never happens.)
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the Living Memory MCP server?
Living Memory is an MCP server listed in the public MCP registry as to.viibe/living-memory. An MCP memory server. One memory your agents share, across models, devices and apps. This page covers its npm package (@nature-labs/lme-mcp).
Is the Living Memory MCP server safe to use?
Living Memory scores 82 out of 100 on VerifyMCP. 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 Living Memory MCP server expose?
Living Memory exposes 4 tools: memory_add, memory_search, memory_state, memory_forget. Their descriptions and schemas cost roughly 353 tokens of context every time the server is loaded.
Is the Living Memory MCP server still maintained?
Living Memory is still listed as active in the MCP registry. We last reached this channel on 8 October 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 Living Memory MCP server under?
Living Memory 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.