# io.github.ezumba/vanguard-memory-node (npm · @lnes/vanguard-memory-node)

Local deterministic BM25 memory for AI agents. Offline-first, no API key, SHA-256 shards, stdio.

- Trust score: 79/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-24

## Components

- npm · `@lnes/vanguard-memory-node`: 79/100 (this document), [markdown](https://verifymcp.io/servers/ezumba-vanguard-memory-node/lnes-vanguard-memory-node.md), [page](https://verifymcp.io/servers/ezumba-vanguard-memory-node/lnes-vanguard-memory-node)

## Channel facts

- Registry: `npm`
- Package: `@lnes/vanguard-memory-node`
- Version: `2.0.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-24.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 97 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 15 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 80/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 670 tokens (~60/item across 11 items; 11 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 70/100
  - Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 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.
  - An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add ezumba-vanguard-memory-node -- npx -y @lnes/vanguard-memory-node
```

### Cursor

```json
{
  "mcpServers": {
    "ezumba-vanguard-memory-node": {
      "command": "npx",
      "args": [
        "-y",
        "@lnes/vanguard-memory-node"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ezumba-vanguard-memory-node": {
      "command": "npx",
      "args": [
        "-y",
        "@lnes/vanguard-memory-node"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add ezumba-vanguard-memory-node -- npx -y @lnes/vanguard-memory-node
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ezumba-vanguard-memory-node": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@lnes/vanguard-memory-node"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ezumba-vanguard-memory-node --command npx --arg -y --arg @lnes/vanguard-memory-node
```

### Hermes

```yaml
mcp_servers:
  ezumba-vanguard-memory-node:
    command: "npx"
    args: ["-y", "@lnes/vanguard-memory-node"]
```

### Netclaw

```json
{
  "McpServers": {
    "ezumba-vanguard-memory-node": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@lnes/vanguard-memory-node"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add ezumba-vanguard-memory-node -t stdio -c npx -a -y @lnes/vanguard-memory-node
```

### Other

```json
{
  "mcpServers": {
    "ezumba-vanguard-memory-node": {
      "command": "npx",
      "args": [
        "-y",
        "@lnes/vanguard-memory-node"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-24 (score 79, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-09-23 (score 79, +1)

- [functional regression] Security disclosure: fail → unverified

### 2026-09-21 (score 78, +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.

### 2026-09-19 (score 77, +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.

### 2026-09-17 (score 76, +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.

### 2026-09-15 (score 75, +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.

### 2026-09-12 (score 74, +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.

### 2026-09-10 (score 73, +4)

- [functional improvement] Stability: unverified → 0.23

## MCP tools (11)

### `vmn_ingest` (~104 tokens)

Ingest text into the local Vanguard Memory Vault. Returns a SHA-256 shard hash.

Input parameters:

- `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, required): The text content to ingest and shard locally
- `title` (string): Optional human-readable title

### `vmn_recall` (~59 tokens)

Recall evidence from a local Vanguard Memory shard using deterministic xLMP lexical search.

Input parameters:

- `hash` (string, required): The SHA-256 shard hash returned by vmn_ingest
- `query` (string, required): The query to search within the shard

### `vmn_list` (~34 tokens)

List all memory objects in the local vault. Optionally filter by namespace.

Input parameters:

- `namespace` (string): Optional namespace filter

### `vmn_search` (~82 tokens)

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.

Input parameters:

- `limit` (number): Maximum number of results (default 10)
- `namespace` (string): Restrict search to this namespace only
- `query` (string, required): Search query to find relevant memory objects

### `vmn_inspect` (~46 tokens)

Inspect the catalog metadata for a specific memory shard by its SHA-256 root hash.

Input parameters:

- `hash` (string, required): The SHA-256 root hash of the memory object to inspect

### `vmn_delete` (~48 tokens)

Delete a memory object from the local vault by its SHA-256 root hash. This is permanent.

Input parameters:

- `hash` (string, required): The SHA-256 root hash of the memory object to delete

### `vmn_stats` (~18 tokens)

Return statistics about the local Vanguard Memory Vault.

### `vmn_index_status` (~28 tokens)

Return the current status of the BM25 inverted index. Indicates if a rebuild is needed.

### `vmn_rebuild_index` (~35 tokens)

Rebuild the BM25 inverted index from existing vault objects. Safe to run at any time — objects are never modified.

### `vmn_sync_vault` (~74 tokens)

Sync a local memory object to the ExergyNet LNES-17 vault. Requires EXERGYNET_API_KEY env var.

Input parameters:

- `intent` (string): Sync intent label (default: "manual-sync")
- `xlmp_root` (string, required): The SHA-256 root hash of the local memory object to sync

### `vmn_ingest_file` (~142 tokens)

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.

Input parameters:

- `file_path` (string, required): 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

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/ezumba-vanguard-memory-node/lnes-vanguard-memory-node#diagnostics

## Score history

- 2026-09-24: 79
- 2026-09-23: 79
- 2026-09-22: 78
- 2026-09-21: 78
- 2026-09-20: 77
- 2026-09-19: 77
- 2026-09-18: 76
- 2026-09-17: 76
- 2026-09-16: 75
- 2026-09-15: 75
- 2026-09-14: 74
- 2026-09-13: 74
- 2026-09-12: 74
- 2026-09-11: 73
- 2026-09-10: 73
- 2026-09-09: 69
- 2026-09-08: 69
- 2026-09-07: 69
- 2026-09-06: 69
- 2026-09-05: 69
- 2026-09-04: 69
- 2026-09-03: 69

## Common questions

### 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.

## Links

- npm package: https://www.npmjs.com/package/@lnes/vanguard-memory-node
- Socket report: https://socket.dev/npm/package/@lnes/vanguard-memory-node
- Repository: https://github.com/ezumba/vanguard-memory-node
- Changelog RSS feed: https://verifymcp.io/servers/ezumba-vanguard-memory-node/lnes-vanguard-memory-node.xml
- Changelog JSON feed: https://verifymcp.io/servers/ezumba-vanguard-memory-node/lnes-vanguard-memory-node.json
- HTML version of this page: https://verifymcp.io/servers/ezumba-vanguard-memory-node/lnes-vanguard-memory-node