MCP Memory
OCI · GHCR.IO/GERMANIU/MCP-MEMORY
Local persistent memory for AI agents: SQLite + FTS5 (BM25) lexical search, zero external infra.
Available components
Last scanned (12 hours ago)
Scores higher than 60% of OCI servers
Category Memory and Knowledge
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
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.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 18 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability51
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 362 tokens (~40/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management63
- Stability observed for 19 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 Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 10 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.
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
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 5 Nov 2026 · Analysed oci/ghcr.io/germaniu/mcp-memory@0.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 →
memory_delete Memory Delete ~21
Delete a memory by id.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| deleted | boolean | yes | – |
| id | string | yes | – |
No examples provided.
memory_export Memory Export ~28
Export memories (all, or one namespace) as a JSONL string.
| Name | Type | Req | Description |
|---|---|---|---|
| namespace | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | – |
| jsonl | string | yes | – |
No examples provided.
memory_import Memory Import ~35
Import memories from JSONL (skips ids that already exist).
| Name | Type | Req | Description |
|---|---|---|---|
| jsonl | string | yes | – |
| namespace_override | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| errors | array | yes | – |
| imported | integer | yes | – |
| skipped | integer | yes | – |
No examples provided.
memory_list Memory List ~32
List memories with pagination.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| namespace | – | – | – |
| offset | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
memory_recent Memory Recent ~25
Most recently updated memories.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| namespace | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
memory_save Memory Save ~40
Persist a new memory. Returns the saved entry.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | – |
| metadata | – | – | – |
| namespace | – | – | – |
| tags | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | – |
| created_at | string | yes | – |
| id | string | yes | – |
| metadata | object | – | – |
| namespace | string | yes | – |
| score | – | – | Relevancia normalizada [0,1] dentro del result set de una llamada a memory_search (BM25 vía SQLite FTS5). No es un score absoluto: no es comparable entre llamadas distintas ni entre namespaces. |
| tags | array | – | – |
| updated_at | string | yes | – |
No examples provided.
memory_search Memory Search ~42
Lexical (BM25/FTS5) search across stored memories.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| namespace | – | – | – |
| query | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
memory_stats Memory Stats ~18
Counts and namespace summary.
| Name | Type | Req | Description |
|---|---|---|---|
| namespace | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
memory_update Memory Update ~41
Update content/tags/metadata of an existing memory.
| Name | Type | Req | Description |
|---|---|---|---|
| content | – | – | – |
| id | string | yes | – |
| metadata | – | – | – |
| tags | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
How do I install the MCP Memory server?
MCP Memory runs locally as a container image, launched with docker run --rm -i -e DB_PATH ghcr.io/germaniu/mcp-memory:0.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/germaniu/mcp-memory
claude mcp add germaniu-mcp-memory -- docker run --rm -i -e DB_PATH ghcr.io/germaniu/mcp-memory:0.6.0
This image reads DB_PATH. Set it in your client's env block for this server; docker run -e passes it through to the container.
What is the MCP Memory server?
MCP Memory is listed in the public MCP registry as io.github.GermaniU/mcp-memory. Local persistent memory for AI agents: SQLite + FTS5 (BM25) lexical search, zero external infra. This page covers its container image (ghcr.io/germaniu/mcp-memory).
Is the MCP Memory server safe to use?
MCP Memory 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 MCP Memory server expose?
MCP Memory exposes 9 tools: memory_save, memory_search, memory_delete, memory_list, memory_update, and 4 more. Their descriptions and schemas cost roughly 282 tokens of context every time the server is loaded.
Is the MCP Memory server still maintained?
MCP Memory is still listed as active in the MCP registry. We last reached this channel on 5 November 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 MCP Memory server under?
MCP Memory declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.