OpenMyMemo
PYPI · OPENMYMEMO
Your AI memory as a local folder you own. Every app shares it; you see and can undo each change.
Available components
Last scanned (3 hours ago)
Scores higher than 61% of PyPI 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 Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 4 of 42 dependencies flagged as unhealthy. View diagnostics → Partial
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 (Apache-2.0).Pass
- Actively maintained (last published 0 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability72
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (fair).Partial
- Context-footprint check failed: tool/resource definitions use about 859 tokens (~143/item across 6 items; 5 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 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
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- 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
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.
- 17 Oct 26 0
- Malware scan: unverified → pass ▲ security
- Package version: 0.2.5 → 0.2.6 functional
- 16 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- Package version: 0.2.4 → 0.2.5 functional
- 15 Oct 26 53
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 17 Oct 2026 · Analysed pypi/openmymemo@0.2.6
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 42 packages
| Packages resolved | 42 |
|---|---|
| Stale | 3 |
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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_context Read memory ~78
Get the user's memory as Markdown: who they are, how they want you to work, what they're doing. Call this once at the start of a conversation. `topics` limits it to some topic slugs; `max_chars` caps its length (most important memories come first).
| Name | Type | Req | Description |
|---|---|---|---|
| max_chars | integer | – | – |
| topics | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
memory_get Get memories ~31
Fetch specific memories by id, with their topic, kind, source and timestamps.
| Name | Type | Req | Description |
|---|---|---|---|
| ids | array | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
memory_proposals Check proposed changes ~114
List the proposals this app made and what happened to them, so you don't repeat rejected or undone ones. Statuses: applied (saved; the user may still undo it), pending (waiting for the user; `hold` says why), accepted or edited_accepted (the user approved it, perhaps reworded), rejected, undone, expired. A proposal that waited in MyMemo Cloud's offline queue also has the `queue_id` it was given then.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| status | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
memory_propose Propose a memory change ~329
Add, correct or retire a memory of the user's. Returns at once; it never waits for the user. - op="add": `content` is one self-contained statement about the user, written in the third person or as the user would say it (e.g. "Prefers answers in Chinese"). Optional `topic` is a topic slug from memory_context; leave it out to let OpenMyMemo file it. - op="update": `memory_id` plus the full corrected `content`. - op="archive": `memory_id` of a memory that is no longer true. `reason` says why; `evidence` quotes what the user said. Reuse an `idempotency_key` when retrying. Returns `status`: - "applied": saved now. The user sees it in their OpenMyMemo digest and can undo it. - "pending": waiting for the user, and `hold` says why: "protected" (they wrote that memory themselves), "private" (it is in a private topic) or "approval" (they review every change first). - "duplicate": they already have this memory; nothing was saved. An add that resembles an existing memory becomes an update of that memory (see `note`). Don't ask the user to approve anything in the chat.
| Name | Type | Req | Description |
|---|---|---|---|
| content | – | – | – |
| evidence | – | – | – |
| idempotency_key | – | – | – |
| kind | – | – | – |
| memory_id | – | – | – |
| op | string | yes | – |
| reason | – | – | – |
| topic | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
memory_search Search memory ~44
Search the user's memory by keywords (any language). Returns matching memories with their ids.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | – |
| topics | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the OpenMyMemo MCP server?
OpenMyMemo runs locally as a PyPI package, launched with uvx openmymemo. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · openmymemo
claude mcp add mymemoai-openmymemo -- uvx openmymemo
What is the OpenMyMemo MCP server?
OpenMyMemo is an MCP server listed in the public MCP registry as io.github.MyMemoAI/openmymemo. Your AI memory as a local folder you own. Every app shares it; you see and can undo each change. This page covers its PyPI package (openmymemo).
Is the OpenMyMemo MCP server safe to use?
OpenMyMemo scores 54 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 17 October 2026. 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 OpenMyMemo MCP server expose?
OpenMyMemo exposes 5 tools: memory_context, memory_search, memory_get, memory_propose, memory_proposals. Their descriptions and schemas cost roughly 596 tokens of context every time the server is loaded.
Is the OpenMyMemo MCP server still maintained?
OpenMyMemo is still listed as active in the MCP registry. We last reached this channel on 17 October 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 OpenMyMemo MCP server under?
OpenMyMemo declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.