io.github.alphaonedev/ai-memory
OCI · GHCR.IO/ALPHAONEDEV/AI-MEMORY:0.5.1
Persistent memory for any AI — zero token cost until recall
Available components
Last scanned (11 hours ago)
Scores higher than 77% 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 210 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability81
- 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 945 tokens (~55/item across 17 items; 17 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage82
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 47% of tool parameters carry a description.Partial
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; "memory_delete" implies "delete" 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 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
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.
Checks we ran (12)
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (4)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Malware scan in Supply Chain Security (scores 0 for this)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.
- Known CVEs in Supply Chain Security (scores 0 for this)Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
- Install scripts in Supply Chain Security (scores 0 for this)Install-script risk not yet assessed.
- Dependency health in Supply Chain Security (scores 0 for this)Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 5 Nov 26 0
- Stability: 0.97 → pass security
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 −1
- Stability: pass → 0.93 functional
- 28 Oct 26 0
- Stability: 0.97 → pass security
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 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/alphaonedev/ai-memory:0.5.1
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_auto_tag ~39
Use LLM to auto-generate tags for a memory. Requires smart or autonomous tier.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Memory ID to auto-tag |
No output schema declared.
No examples provided.
memory_capabilities ~26
Report the active feature tier, loaded models, and available capabilities of the memory system.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
memory_consolidate ~112
Consolidate multiple memories into one long-term summary. Deletes source memories and creates derived_from links. If summary is omitted and LLM is available (smart/autonomous tier), auto-generates a summary.
| Name | Type | Req | Description |
|---|---|---|---|
| ids | array | yes | Memory IDs to consolidate (minimum 2, maximum 100) |
| namespace | string | – | – |
| summary | string | – | Summary content (optional — auto-generated via LLM if omitted at smart/autonomous tier) |
| title | string | yes | Title for the consolidated memory |
No output schema declared.
No examples provided.
memory_delete ~21
Delete a memory by ID.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
memory_detect_contradiction ~51
Use LLM to check if two memories contradict each other. Requires smart or autonomous tier.
| Name | Type | Req | Description |
|---|---|---|---|
| id_a | string | yes | First memory ID |
| id_b | string | yes | Second memory ID |
No output schema declared.
No examples provided.
memory_expand_query ~42
Use LLM to expand a search query into additional semantically related terms. Requires smart or autonomous tier.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | The search query to expand |
No output schema declared.
No examples provided.
memory_forget ~42
Bulk delete memories matching a pattern, namespace, or tier.
| Name | Type | Req | Description |
|---|---|---|---|
| namespace | string | – | – |
| pattern | string | – | – |
| tier | string | – | – |
No output schema declared.
No examples provided.
memory_get ~30
Get a specific memory by ID, including its links.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Memory ID to retrieve |
No output schema declared.
No examples provided.
memory_get_links ~32
Get all links for a memory (both directions).
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Memory ID to get links for |
No output schema declared.
No examples provided.
memory_link ~44
Create a link between two memories.
| Name | Type | Req | Description |
|---|---|---|---|
| relation | string | – | – |
| source_id | string | yes | Source memory ID |
| target_id | string | yes | Target memory ID |
No output schema declared.
No examples provided.
memory_list ~67
List memories, optionally filtered by namespace or tier.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Response format. Default 'toon_compact' saves 79% tokens. 'json' for structured parsing. |
| limit | integer | – | – |
| namespace | string | – | – |
| tier | string | – | – |
No output schema declared.
No examples provided.
memory_promote ~26
Promote a memory to long-term (permanent).
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
memory_recall ~139
Recall memories relevant to a context. Uses fuzzy OR matching, ranks by relevance + priority + access frequency + tier.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | What you're trying to remember |
| format | string | – | Response format. Default 'toon_compact' saves 79% tokens vs JSON. 'toon' includes timestamps. 'json' for structured parsing. |
| limit | integer | – | – |
| namespace | string | – | Filter by namespace |
| since | string | – | Only memories created after this RFC3339 timestamp |
| tags | string | – | Filter by tag |
| until | string | – | Only memories created before this RFC3339 timestamp |
No output schema declared.
No examples provided.
memory_search ~74
Search memories by exact keyword match (AND semantics).
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Response format. Default 'toon_compact' saves 79% tokens. 'json' for structured parsing. |
| limit | integer | – | – |
| namespace | string | – | – |
| query | string | yes | – |
| tier | string | – | – |
No output schema declared.
No examples provided.
memory_stats ~13
Get memory store statistics.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
memory_store ~86
Store a new memory. Deduplicates by title+namespace.
| Name | Type | Req | Description |
|---|---|---|---|
| confidence | number | – | – |
| content | string | yes | Full memory content |
| namespace | string | – | Project/topic namespace |
| priority | integer | – | – |
| source | string | – | – |
| tags | array | – | – |
| tier | string | – | – |
| title | string | yes | Short descriptive title |
No output schema declared.
No examples provided.
memory_update ~101
Update an existing memory by ID. Only provided fields are changed.
| Name | Type | Req | Description |
|---|---|---|---|
| confidence | number | – | – |
| content | string | – | – |
| expires_at | string | – | Expiry timestamp (RFC3339), or null to clear |
| id | string | yes | Memory ID to update |
| namespace | string | – | – |
| priority | integer | – | – |
| tags | array | – | – |
| tier | string | – | – |
| title | string | – | – |
No output schema declared.
No examples provided.
How do I install the io.github.alphaonedev/ai-memory MCP server?
io.github.alphaonedev/ai-memory runs locally as a container image, launched with docker run --rm -i -e AI_MEMORY_DB ghcr.io/alphaonedev/ai-memory:0.5.1 mcp --tier semantic. 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/alphaonedev/ai-memory:0.5.1
claude mcp add alphaonedev-ai-memory -- docker run --rm -i -e AI_MEMORY_DB ghcr.io/alphaonedev/ai-memory:0.5.1 mcp --tier semantic
This image reads AI_MEMORY_DB. Set it in your client's env block for this server; docker run -e passes it through to the container.
What is the io.github.alphaonedev/ai-memory MCP server?
io.github.alphaonedev/ai-memory is an MCP server listed in the public MCP registry as io.github.alphaonedev/ai-memory. Persistent memory for any AI, zero token cost until recall. This page covers its container image (ghcr.io/alphaonedev/ai-memory:0.5.1).
Is the io.github.alphaonedev/ai-memory MCP server safe to use?
io.github.alphaonedev/ai-memory scores 50 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 io.github.alphaonedev/ai-memory MCP server expose?
io.github.alphaonedev/ai-memory exposes 17 tools: memory_store, memory_recall, memory_search, memory_list, memory_delete, and 12 more. Their descriptions and schemas cost roughly 945 tokens of context every time the server is loaded.
Is the io.github.alphaonedev/ai-memory MCP server still maintained?
io.github.alphaonedev/ai-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 io.github.alphaonedev/ai-memory MCP server under?
io.github.alphaonedev/ai-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.
What did VerifyMCP test on the io.github.alphaonedev/ai-memory MCP server?
VerifyMCP ran 12 checks on io.github.alphaonedev/ai-memory, covering Source repository, Provenance, License, Maintenance and 8 more. 4 items could not be completed, a gap on our side rather than a finding about io.github.alphaonedev/ai-memory: Malware scan, Known CVEs, Install scripts and Dependency health. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a container image, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.