vanguard-memory-node
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AUTO_SYNC_VAULT | No | Set to true to auto-sync every vmn_ingest to ExergyNet | false |
| EXERGYNET_API_KEY | No | API key for ExergyNet vault access (sk-exergy-*) | |
| EXERGYNET_NETWORK | No | Target substrate: mainnet → portal.exergynet.org, testnet → dt.portal.exergynet.org | testnet |
| EXERGYNET_VAULT_URL | No | Override vault base URL entirely |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| vmn_ingestB | Ingest text into the local Vanguard Memory Vault. Returns a SHA-256 shard hash. |
| vmn_recallB | Recall evidence from a local Vanguard Memory shard using deterministic xLMP lexical search. |
| vmn_listA | List all memory objects in the local vault. Optionally filter by namespace. |
| vmn_searchA | 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_inspectB | Inspect the catalog metadata for a specific memory shard by its SHA-256 root hash. |
| vmn_deleteA | Delete a memory object from the local vault by its SHA-256 root hash. This is permanent. |
| vmn_statsB | Return statistics about the local Vanguard Memory Vault. |
| vmn_index_statusA | Return the current status of the BM25 inverted index. Indicates if a rebuild is needed. |
| vmn_rebuild_indexA | Rebuild the BM25 inverted index from existing vault objects. Safe to run at any time — objects are never modified. |
| vmn_sync_vaultB | Sync a local memory object to the ExergyNet LNES-17 vault. Requires EXERGYNET_API_KEY env var. |
| vmn_ingest_fileA | 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| vmn-store | Store text or a note into the local Vanguard Memory Vault |
| vmn-find | Search the local Vanguard Memory Vault for relevant context |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| vault-stats | |
| vault-all |
TDQS
Scored across 11 tools
Each tool targets a distinct operation (ingest, search, recall, delete, index management), so selection is mostly clear. The search/recall and ingest/ingest_file pairs are related but descriptions differentiate candidate-root listing versus evidence retrieval and raw-text versus cursor-tracked file ingestion.
All tools share the vmn_ prefix and most use an imperative verb (recall, ingest, delete, rebuild, sync), which is easy to predict. vmn_stats and vmn_index_status break the verb-first pattern by using noun phrases, but this is a minor inconsistency.
Eleven tools is a reasonable size for a memory-vault server and every tool addresses a concrete function: storage, retrieval, deletion, stats, index health, and external sync. It avoids both bloat and minimalism for the stated scope.
The surface covers the core memory lifecycle: ingest text/files, list, search, recall evidence, inspect metadata, delete, index maintenance, stats, and sync. No critical dead ends appear, though there is no explicit update operation—probably appropriate because memory objects are addressed by immutable hashes.