Living Memory
NPM · @NATURE-LABS/LME-MCP · 2 COMPONENTS · SCANNED AUG 18
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 →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- Known CVEs were checked across the 96 of 97 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 96 of 97 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 3 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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @nature-labs/lme-mcp
claude mcp add to-viibe-living-memory -- npx -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": {
"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.
- 15 Aug 26 68
First indexed and scored.
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 18 Aug 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 |
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 30 |
| Tree resolution | Partial |
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
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.