vanguard-memory-node
Related Servers
Alternatives to vanguard-memory-node
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceA searchable long-term memory server for AI agents using BM25 indexing over document chunks, enabling durable recall across sessions without cloud dependencies.1Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables AI agents and any MCP-compatible client to persist, search, update, and delete plain-text memories across sessions, using BM25 lexical ranking over SQLite FTS5 with namespace filtering, tags, free-form metadata, and JSONL export/import — entirely local, with zero external infrastructure.1MIT
- AlicenseAqualityBmaintenanceLocal-first agent memory & knowledge service (v2.4.4): hybrid retrieval (vector + BM25) + offline CSV/Excel row-level Q&A without LLM; REST + MCP dual protocol (13 tools incl. list/delete documents); memory governance; Python.13203 PyPI5Apache 2.0
- AlicenseNot gradedqualityDmaintenancePersistent, searchable memory for AI agents over the Model Context Protocol, enabling memory storage, full-text search with BM25 ranking, and retrieval across sessions.8 npmMIT
- AlicenseAqualityBmaintenanceEnables AI agents to store and retrieve self-hosted memories over MCP (stdio or Streamable HTTP) using local embeddings that work fully offline. Writes are redacted before they hit storage and every read is recorded in an exportable, append-only audit log.4AGPL 3.0
- AlicenseNot gradedqualityDmaintenanceLocal-first long-term memory database for AI systems, providing SQLite FTS5/BM25 retrieval and optional SentenceTransformer embeddings via MCP server.MIT
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.