@lnes/vanguard-memory-node

MCPcommunity
v2.0.1io.github.ezumbaMITUpdated 1mo agonpmGitHub

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

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
18Downloads/wk
1mo agoLast update
Package
Authorio.github.ezumba
LicenseMIT
Version2.0.1
Sourcenpm+mcp-registry
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface11 tools · 1 privileged
Security scan✓ Cleanv2.0.2 · 29d agoHow well does this scan work?
EvalsNone
IndexedSep 6, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

11 tools · 1 privileged
Statically extracted from the published packagev2.0.2 · 29d ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

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

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

No input schema was published for this tool.

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

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

No input schema was published for this tool.

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

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

No input schema was published for this tool.

vmn_searchSearch across all memory objects in the vault by keyword query. Returns candidate roots. Use vmn_recall with a specific root to retrieve full evidence.

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.

No input schema was published for this tool.

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

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

No input schema was published for this tool.

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

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

No input schema was published for this tool.

vmn_statsReturn statistics about the local Vanguard Memory Vault.

Return statistics about the local Vanguard Memory Vault.

No input schema was published for this tool.

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

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

No input schema was published for this tool.

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

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

No input schema was published for this tool.

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

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

No input schema was published for this tool.

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

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.

No input schema was published for this tool.

11 of 11 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

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

Keywords
mcp
Alternatives
Comparing tool surfaces…

Dependency tree

What one Forge scan resolved from npm metadata on 2026-09-06 — observed resolution, not a publisher declaration.

60 packages resolved · 3 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the depth-4 limit. Anything below that level was never resolved.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

55 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+43 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.

Topics

Related in memory & knowledge graphs