Memory Vault
OCI · GHCR.IO/MIHAIBUILDS/MEMORY-VAULT-MCP:1.6.0 · SCANNED SEP 20
Local-first AI memory layer with hybrid search. Postgres + pgvector. Self-hosted, MIT.
Available components
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. How we score → Why this is hard to score →
Supply Chain Security0
- Malware scan not yet available for this package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 9 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability83
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 813 tokens (~101/item across 8 items; 6 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
- Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "purge_forgotten" implies "purge" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
How do I install the Memory Vault MCP server?
Memory Vault runs locally as a container image, launched with docker run --rm -i ghcr.io/mihaibuilds/memory-vault-mcp:1.6.0. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/mihaibuilds/memory-vault-mcp:1.6.0
claude mcp add mihaibuilds-memory-vault -- docker run --rm -i ghcr.io/mihaibuilds/memory-vault-mcp:1.6.0
{
"mcpServers": {
"mihaibuilds-memory-vault": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/mihaibuilds/memory-vault-mcp:1.6.0"
]
}
}
} {
"servers": {
"mihaibuilds-memory-vault": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/mihaibuilds/memory-vault-mcp:1.6.0"
]
}
}
} codex mcp add mihaibuilds-memory-vault -- docker run --rm -i ghcr.io/mihaibuilds/memory-vault-mcp:1.6.0
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"mihaibuilds-memory-vault": {
"type": "local",
"command": [
"docker",
"run",
"--rm",
"-i",
"ghcr.io/mihaibuilds/memory-vault-mcp:1.6.0"
],
"enabled": true
}
}
} mcp_servers:
mihaibuilds-memory-vault:
command: "docker"
args: ["run", "--rm", "-i", "ghcr.io/mihaibuilds/memory-vault-mcp:1.6.0"] {
"McpServers": {
"mihaibuilds-memory-vault": {
"Transport": "stdio",
"Command": "docker",
"Arguments": [
"run",
"--rm",
"-i",
"ghcr.io/mihaibuilds/memory-vault-mcp:1.6.0"
]
}
}
} {
"mcpServers": {
"mihaibuilds-memory-vault": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/mihaibuilds/memory-vault-mcp:1.6.0"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 18 Sept 26 +4
- Stability: unverified → 0.27 ▲ functional
- 10 Sept 26 39
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed oci/ghcr.io/mihaibuilds/memory-vault-mcp:1.6.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
forget ~66
Soft-delete a memory chunk by ID. The chunk is removed from search results but stays in the database for potential recovery. Sets importance to 0 and marks it in metadata. Args: chunk_id: The UUID of the chunk to forget.
| Name | Type | Req | Description |
|---|---|---|---|
| chunk_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
memory_status ~32
Get the current status of the memory system. Returns database health, chunk counts per space, and embedding model info.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
move_memory ~120
Move a stored memory into a different space. The memory keeps its content and embedding; only the space it belongs to changes. Its knowledge-graph entries are rebuilt in the target space so the graph and search agree about where it lives. The target space must already exist — use the dashboard or the API to create one first. Args: chunk_id: The UUID of the chunk to move. target_space: Name of the space to move it into.
| Name | Type | Req | Description |
|---|---|---|---|
| chunk_id | string | yes | – |
| target_space | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
purge_forgotten ~175
Permanently delete memories that were forgotten a while ago. `forget` is a soft delete: the memory stops appearing in search but the row stays, so it can be recovered. Nothing removed it afterwards, so a vault that is edited often accumulated one dead row per edit forever. This is the deliberate, irreversible half. It is never automatic — there is no timer that quietly deletes your memories — and it only touches memories already marked forgotten, never active ones. Args: older_than_days: Only purge memories forgotten at least this many days ago. The default keeps a month of recovery, so purging right after an accidental forget still spares it. Pass 0 to purge every forgotten memory regardless of age.
| Name | Type | Req | Description |
|---|---|---|---|
| older_than_days | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
recall ~261
Search your memories for information relevant to a query. Returns chunks ranked by relevance using hybrid search (vector + full-text + RRF). Uses query enrichment (keyword extraction + variation) for better recall. Results are budgeted to fit within max_tokens to avoid flooding context. Args: query: The search query — a question, topic, or keyword phrase. spaces: Filter to specific memory spaces (e.g. ["default", "projects"]). If omitted, searches all spaces. since: Only return memories after this date (ISO format, e.g. "2025-01-01"). limit: Maximum number of results (default 10, max 50). max_tokens: Token budget for results (default 2000). ef_search: How much of the vector index to search, 1-1000. Omit to use the default (40). Raise it when a search should have found something and did not — better recall, slower query. Worth trying before concluding a memory is missing.
| Name | Type | Req | Description |
|---|---|---|---|
| ef_search | – | – | – |
| limit | integer | – | – |
| max_tokens | integer | – | – |
| query | string | yes | – |
| since | – | – | – |
| spaces | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
remember ~128
Store a new memory in the system. The text is embedded and stored as a searchable chunk. Use this to save important information, decisions, or knowledge. Args: text: The text content to remember. space: Which memory space to store it in (default "default"). source: Where this memory comes from (default "mcp"). speaker: Who said/wrote this — "human" or "assistant" (default "human").
| Name | Type | Req | Description |
|---|---|---|---|
| source | string | – | – |
| space | string | – | – |
| speaker | string | – | – |
| text | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
What is the Memory Vault MCP server?
Memory Vault is an MCP server listed in the public MCP registry as io.github.MihaiBuilds/memory-vault. Local-first AI memory layer with hybrid search. Postgres + pgvector. Self-hosted, MIT. This page covers its container image (ghcr.io/mihaibuilds/memory-vault-mcp:1.6.0).
Is the Memory Vault MCP server safe to use?
Memory Vault scores 43 out of 100 on VerifyMCP. 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 Memory Vault MCP server expose?
Memory Vault exposes 6 tools: recall, remember, forget, purge_forgotten, move_memory, memory_status. Their descriptions and schemas cost roughly 782 tokens of context every time the server is loaded.
Is the Memory Vault MCP server still maintained?
Memory Vault is still listed as active in the MCP registry. We last reached this channel on 20 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 Memory Vault MCP server under?
Memory Vault declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.