io.github.kael-bit/engram
NPM · ENGRAM-RS-MCP
Hierarchical memory for AI agents. Three-layer (buffer/working/core) with decay and promotion.
Available components
Last scanned (3 hours ago)
Scores higher than 58% 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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency44
- 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 (MIT).Pass
- Actively maintained (last published 250 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1393 tokens (~92/item across 15 items; 15 tools + 0 resources), lean.Pass
- 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
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "engram_delete" 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 15 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.
- 1 Nov 26 0
- Security disclosure: unverified → fail ▼ functional
- 31 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
- 28 Oct 26 +1
- Stability: 0.97 → pass security
- 27 Oct 26 −1
- Stability: pass → 0.97 functional
- 25 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- Security disclosure: fail → unverified ▼ functional
- 21 Oct 26 0
- Stability: 0.97 → pass security
- 20 Oct 26 0
- Stability: pass → 0.97 functional
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 5 Nov 2026 · Analysed npm/engram-rs-mcp@0.10.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 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| 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 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| 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 →
engram_consolidate ~111
Run a memory consolidation cycle. Promotes important memories upward, drops decayed entries. With merge=true, uses LLM to merge similar memories.
| Name | Type | Req | Description |
|---|---|---|---|
| decay_drop_threshold | number | – | Drop below this recency (default 0.01) |
| merge | boolean | – | Use LLM to merge similar memories |
| promote_min_importance | number | – | Min importance to promote (default 0.6) |
| promote_threshold | integer | – | Min access count to promote (default 3) |
No output schema declared.
No examples provided.
engram_delete ~38
Delete a memory by ID. Use when a memory is outdated, incorrect, or redundant.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Memory ID to delete |
No output schema declared.
No examples provided.
engram_extract ~55
Extract structured memories from raw text using LLM. Feed conversation logs or notes and get individual memories.
| Name | Type | Req | Description |
|---|---|---|---|
| auto_embed | boolean | – | Generate embeddings (default true) |
| text | string | yes | Raw text to extract memories from |
No output schema declared.
No examples provided.
engram_health ~26
Detailed health check: uptime, RSS memory, embed cache stats, AI config status.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
engram_recall ~291
Hybrid semantic + keyword search with budget-aware retrieval. Fast by default (~30ms cached, ~1s first query). Optional rerank/expand add LLM calls (+2-4s each) — only use when needed.
| Name | Type | Req | Description |
|---|---|---|---|
| budget_tokens | integer | – | Max token budget |
| dry | boolean | – | Skip touch/reinforcement on results (for background queries) |
| expand | boolean | – | LLM query expansion (+1-2s). Use for short/vague queries like single words |
| layers | array | – | Filter by layers |
| limit | integer | – | Max results |
| min_importance | number | – | Min importance threshold |
| min_score | number | – | Drop results below this score (0-1) |
| namespace | string | – | Filter by namespace (also includes "default" namespace automatically) |
| query | string | yes | Search query |
| rerank | boolean | – | Re-rank via LLM (+2-4s). Use only when result ordering is critical |
| since | integer | – | Only memories created after this unix ms timestamp |
| sort_by | string | – | Sort order (default: score) |
| source | string | – | Filter by source (e.g. session, extract, api) |
| tags | array | – | Filter by tags (must have ALL specified) |
| until | integer | – | Only memories created before this unix ms timestamp |
No output schema declared.
No examples provided.
engram_recent ~105
List recent memories by creation time. Good for session context recovery.
| Name | Type | Req | Description |
|---|---|---|---|
| hours | number | – | Look back N hours (default 2) |
| layer | integer | – | Filter by layer |
| limit | integer | – | Max results (default 20) |
| min_importance | number | – | Minimum importance threshold |
| namespace | string | – | Filter by namespace (also includes "default" namespace automatically) |
| source | string | – | Filter by source (e.g. session) |
No output schema declared.
No examples provided.
engram_repair ~35
Repair FTS search index. Removes orphaned entries and rebuilds missing ones. Safe to run anytime — idempotent.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
engram_restore ~36
Restore a soft-deleted memory from trash back to its original layer.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Memory ID to restore from trash |
No output schema declared.
No examples provided.
engram_resume ~182
Full memory bootstrap for session recovery. Returns core (permanent knowledge), working (ongoing context/decisions), buffer (transient), recent activity, and session notes. Use workspace tags to filter by current work context. Compact mode (default) minimizes token usage.
| Name | Type | Req | Description |
|---|---|---|---|
| budget | number | – | Max chars across all sections (default 8000, 0=unlimited) |
| compact | boolean | – | Compact output: content+tags only (default true) |
| hours | number | – | Look back N hours for recent/sessions (default 4) |
| limit | number | – | Max memories per layer (default 100) |
| namespace | string | – | Filter by namespace (also includes "default" namespace automatically) |
| workspace | string | – | Comma-separated workspace tags to filter core/working memories (e.g. 'engram,rust') |
No output schema declared.
No examples provided.
engram_search ~64
Quick keyword search. Lighter than recall — no scoring or budget logic.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max results (default 10) |
| namespace | string | – | Filter by namespace (also includes "default" namespace automatically) |
| q | string | yes | Search query |
No output schema declared.
No examples provided.
engram_stats ~22
Get memory statistics: counts per layer, AI status, version.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
engram_store ~222
Store a memory. All memories start in Buffer and promote to Working/Core through access frequency and LLM quality gating. Procedural memories and lessons (tag=lesson) auto-promote to Working after 2h. Use supersedes to replace outdated memories by their ids.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | Memory content text |
| importance | number | – | Importance 0-1 (default 0.5, bumps +0.02 on each recall) |
| kind | string | – | Memory type: semantic (facts, default), episodic (events), procedural (how-to, persists indefinitely) |
| namespace | string | – | Override namespace. Use "default" for cross-project knowledge (user identity, preferences, universal lessons) |
| skip_dedup | boolean | – | Skip near-duplicate detection |
| source | string | – | Source identifier |
| supersedes | array | – | IDs of old memories this one replaces |
| sync_embed | boolean | – | Wait for embedding generation before returning (default: false) |
| tags | array | – | Tags for categorization |
No output schema declared.
No examples provided.
engram_trash ~36
List soft-deleted memories. Recently deleted items can be restored.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max results (default 100) |
No output schema declared.
No examples provided.
engram_triggers ~61
Fetch trigger memories for a specific action. Call before performing an action (e.g. git-push, deploy) to recall relevant lessons and rules.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Action name (e.g. git-push, deploy, send-message) |
No output schema declared.
No examples provided.
engram_update ~109
Update a memory's content, metadata (importance, tags, layer, kind). Use supersedes on store to replace with history.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | – | New content text |
| id | string | yes | Memory ID to update |
| importance | number | – | New importance value |
| kind | string | – | Memory type |
| layer | integer | – | Move to layer: 1=buffer, 2=working, 3=core |
| tags | array | – | Replace tags |
No output schema declared.
No examples provided.
How do I install the io.github.kael-bit/engram MCP server?
io.github.kael-bit/engram runs locally as an npm package, launched with npx -y engram-rs-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 · engram-rs-mcp
claude mcp add kael-bit-engram -- npx -y engram-rs-mcp
What is the io.github.kael-bit/engram MCP server?
io.github.kael-bit/engram is an MCP server listed in the public MCP registry as io.github.kael-bit/engram. Hierarchical memory for AI agents. Three-layer (buffer/working/core) with decay and promotion. This page covers its npm package (engram-rs-mcp).
Is the io.github.kael-bit/engram MCP server safe to use?
io.github.kael-bit/engram scores 78 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 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.kael-bit/engram MCP server expose?
io.github.kael-bit/engram exposes 15 tools: engram_store, engram_recall, engram_recent, engram_resume, engram_extract, and 10 more. Their descriptions and schemas cost roughly 1,393 tokens of context every time the server is loaded.
Is the io.github.kael-bit/engram MCP server still maintained?
io.github.kael-bit/engram is still listed as active in the MCP registry. We last reached this channel on 5 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.kael-bit/engram MCP server under?
io.github.kael-bit/engram declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.