io.github.ezumba/vanguard-memory-node
NPM · @LNES/VANGUARD-MEMORY-NODE · SCANNED SEP 24
Local deterministic BM25 memory for AI agents. Offline-first, no API key, SHA-256 shards, stdio.
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
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 97 dependencies flagged as unhealthy. 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 (MIT).Pass
- Actively maintained (last published 15 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 670 tokens (~60/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 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; "vmn_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 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
How do I install the io.github.ezumba/vanguard-memory-node MCP server?
io.github.ezumba/vanguard-memory-node runs locally as an npm package, launched with npx -y @lnes/vanguard-memory-node. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @lnes/vanguard-memory-node
claude mcp add ezumba-vanguard-memory-node -- npx -y @lnes/vanguard-memory-node
{
"mcpServers": {
"ezumba-vanguard-memory-node": {
"command": "npx",
"args": [
"-y",
"@lnes/vanguard-memory-node"
]
}
}
} {
"servers": {
"ezumba-vanguard-memory-node": {
"command": "npx",
"args": [
"-y",
"@lnes/vanguard-memory-node"
]
}
}
} codex mcp add ezumba-vanguard-memory-node -- npx -y @lnes/vanguard-memory-node
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ezumba-vanguard-memory-node": {
"type": "local",
"command": [
"npx",
"-y",
"@lnes/vanguard-memory-node"
],
"enabled": true
}
}
} openclaw mcp add ezumba-vanguard-memory-node --command npx --arg -y --arg @lnes/vanguard-memory-node
mcp_servers:
ezumba-vanguard-memory-node:
command: "npx"
args: ["-y", "@lnes/vanguard-memory-node"] {
"McpServers": {
"ezumba-vanguard-memory-node": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@lnes/vanguard-memory-node"
]
}
}
} assistant mcp add ezumba-vanguard-memory-node -t stdio -c npx -a -y @lnes/vanguard-memory-node
{
"mcpServers": {
"ezumba-vanguard-memory-node": {
"command": "npx",
"args": [
"-y",
"@lnes/vanguard-memory-node"
]
}
}
} 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.
- 24 Sept 26 0
- Security disclosure: unverified → fail ▼ functional
- 23 Sept 26 +1
- Security disclosure: fail → unverified ▼ functional
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 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.
- 17 Sept 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.
- 15 Sept 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.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +4
- Stability: unverified → 0.23 ▲ 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 24 Sept 2026 · Analysed npm/@lnes/vanguard-memory-node@2.0.1
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 97 packages
| Packages resolved | 97 |
|---|---|
| Stale | 31 |
| 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 →
vmn_delete ~48
Delete a memory object from the local vault by its SHA-256 root hash. This is permanent.
| Name | Type | Req | Description |
|---|---|---|---|
| hash | string | yes | The SHA-256 root hash of the memory object to delete |
No output schema declared.
No examples provided.
vmn_index_status ~28
Return the current status of the BM25 inverted index. Indicates if a rebuild is needed.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
vmn_ingest ~104
Ingest text into the local Vanguard Memory Vault. Returns a SHA-256 shard hash.
| Name | Type | Req | Description |
|---|---|---|---|
| content_type | string | – | Optional content type (default: "text/plain") |
| namespace | string | – | Optional namespace (default: "default") |
| source | string | – | Optional source label |
| tags | array | – | Optional tags |
| text | string | yes | The text content to ingest and shard locally |
| title | string | – | Optional human-readable title |
No output schema declared.
No examples provided.
vmn_ingest_file ~142
Ingest new content from a file into the vault, tracking progress with a cursor so only new lines are ingested on each call. Safe to call repeatedly — only the delta since the last call is stored.
| Name | Type | Req | Description |
|---|---|---|---|
| file_path | string | yes | Absolute path to the file to ingest |
| namespace | string | – | Namespace for the ingested content (default: "file_ingest") |
| session_id | string | – | Cursor key — defaults to the file path. Use a stable ID (e.g. session ID) to track the same file across calls |
| tags | array | – | Optional tags |
| title | string | – | Optional title override |
No output schema declared.
No examples provided.
vmn_inspect ~46
Inspect the catalog metadata for a specific memory shard by its SHA-256 root hash.
| Name | Type | Req | Description |
|---|---|---|---|
| hash | string | yes | The SHA-256 root hash of the memory object to inspect |
No output schema declared.
No examples provided.
vmn_list ~34
List all memory objects in the local vault. Optionally filter by namespace.
| Name | Type | Req | Description |
|---|---|---|---|
| namespace | string | – | Optional namespace filter |
No output schema declared.
No examples provided.
vmn_rebuild_index ~35
Rebuild the BM25 inverted index from existing vault objects. Safe to run at any time — objects are never modified.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
vmn_recall ~59
Recall evidence from a local Vanguard Memory shard using deterministic xLMP lexical search.
| Name | Type | Req | Description |
|---|---|---|---|
| hash | string | yes | The SHA-256 shard hash returned by vmn_ingest |
| query | string | yes | The query to search within the shard |
No output schema declared.
No examples provided.
vmn_search ~82
Search across all memory objects in the vault by keyword query. Returns candidate roots. Use vmn_recall with a specific root to retrieve full evidence.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum number of results (default 10) |
| namespace | string | – | Restrict search to this namespace only |
| query | string | yes | Search query to find relevant memory objects |
No output schema declared.
No examples provided.
vmn_stats ~18
Return statistics about the local Vanguard Memory Vault.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
vmn_sync_vault ~74
Sync a local memory object to the ExergyNet LNES-17 vault. Requires EXERGYNET_API_KEY env var.
| Name | Type | Req | Description |
|---|---|---|---|
| intent | string | – | Sync intent label (default: "manual-sync") |
| xlmp_root | string | yes | The SHA-256 root hash of the local memory object to sync |
No output schema declared.
No examples provided.
What is the io.github.ezumba/vanguard-memory-node MCP server?
io.github.ezumba/vanguard-memory-node is an MCP server listed in the public MCP registry as io.github.ezumba/vanguard-memory-node. Local deterministic BM25 memory for AI agents. Offline-first, no API key, SHA-256 shards, stdio. This page covers its npm package (@lnes/vanguard-memory-node).
Is the io.github.ezumba/vanguard-memory-node MCP server safe to use?
io.github.ezumba/vanguard-memory-node scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 24 September 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.ezumba/vanguard-memory-node MCP server expose?
io.github.ezumba/vanguard-memory-node exposes 11 tools: vmn_ingest, vmn_recall, vmn_list, vmn_search, vmn_inspect, and 6 more. Their descriptions and schemas cost roughly 670 tokens of context every time the server is loaded.
Is the io.github.ezumba/vanguard-memory-node MCP server still maintained?
io.github.ezumba/vanguard-memory-node is still listed as active in the MCP registry. We last reached this channel on 24 September 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.ezumba/vanguard-memory-node MCP server under?
io.github.ezumba/vanguard-memory-node declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.