# @lnes/vanguard-memory-node

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

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the package rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 2.0.1
- **Author:** io.github.ezumba
- **License:** MIT
- **npm:** @lnes/vanguard-memory-node
- **Source:** https://github.com/ezumba/vanguard-memory-node
- **Compatible clients:** claude-code, cursor, copilot, gemini (basis: transport)

## Trust

60/100 (B), scored on the package rubric
- Publisher verified: no
- Install scripts: nothing suspicious found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 29 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-09-06T05:54:16.020Z
- **Version scanned:** 2.0.2
- **CVEs:** none found by OSV at scan time

## Tools

11 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `vmn_ingest` — Ingest text into the local Vanguard Memory Vault. Returns a SHA-256 shard hash.
- `vmn_recall` — Recall evidence from a local Vanguard Memory shard using deterministic xLMP lexical search.
- `vmn_list` — List all memory objects in the local vault. Optionally filter by namespace.
- `vmn_search` — 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.
- `vmn_inspect` — Inspect the catalog metadata for a specific memory shard by its SHA-256 root hash.
- `vmn_delete` — Delete a memory object from the local vault by its SHA-256 root hash. This is permanent.
- `vmn_stats` — Return statistics about the local Vanguard Memory Vault.
- `vmn_index_status` — Return the current status of the BM25 inverted index. Indicates if a rebuild is needed.
- `vmn_rebuild_index` — Rebuild the BM25 inverted index from existing vault objects. Safe to run at any time — objects are never modified.
- `vmn_sync_vault` — Sync a local memory object to the ExergyNet LNES-17 vault. Requires EXERGYNET_API_KEY env var.
- `vmn_ingest_file` — 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 d

## Install

**Verdict: review** — Installable, but 1 thing to check first: No publisher has proved control of this listing; it is indexed, not vouched for.
**Cautions** (coverage gaps and advisories — never blocking)
- No publisher has proved control of this listing; it is indexed, not vouched for.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"vanguard-memory-node\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"@lnes/vanguard-memory-node\"\n      ]\n    }\n  }\n}"
```

## Blast radius

Extensive to critical — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: deletes data; runs on your machine.
- Floor 36, ceiling 60 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/%40lnes%2Fvanguard-memory-node
- Install plan: https://forgeregistry.com/api/v1/packages/%40lnes%2Fvanguard-memory-node/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/%40lnes%2Fvanguard-memory-node
- HTML page: https://forgeregistry.com/registry/%40lnes%2Fvanguard-memory-node
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.