Anamnesis
PYPI · ANAMNESIS-MEMORY · SCANNED SEP 20
Cross-machine, file-first memory for Claude Code: markdown + SQLite FTS5, synced with git
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 1 of 17 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency32
- 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
- License check failed: the license (Apache Software License) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 76 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 577 tokens (~115/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 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 5 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
How do I install the Anamnesis MCP server?
Anamnesis runs locally as a PyPI package, launched with uvx anamnesis-memory. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · anamnesis-memory
claude mcp add oscardvs-anamnesis -- uvx anamnesis-memory
{
"mcpServers": {
"oscardvs-anamnesis": {
"command": "uvx",
"args": [
"anamnesis-memory"
]
}
}
} {
"servers": {
"oscardvs-anamnesis": {
"command": "uvx",
"args": [
"anamnesis-memory"
]
}
}
} codex mcp add oscardvs-anamnesis -- uvx anamnesis-memory
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"oscardvs-anamnesis": {
"type": "local",
"command": [
"uvx",
"anamnesis-memory"
],
"enabled": true
}
}
} openclaw mcp add oscardvs-anamnesis --command uvx --arg anamnesis-memory
mcp_servers:
oscardvs-anamnesis:
command: "uvx"
args: ["anamnesis-memory"] {
"McpServers": {
"oscardvs-anamnesis": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"anamnesis-memory"
]
}
}
} assistant mcp add oscardvs-anamnesis -t stdio -c uvx -a anamnesis-memory
{
"mcpServers": {
"oscardvs-anamnesis": {
"command": "uvx",
"args": [
"anamnesis-memory"
]
}
}
} 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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 −3
- Stability: pass → 0.83 functional
- 18 Sept 26 +1
- Stability: 0.97 → pass security
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 −3
- Stability: pass → 0.80 functional
- 11 Sept 26 +1
- Stability: 0.97 → pass security
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 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 20 Sept 2026 · Analysed pypi/anamnesis-memory@0.1.3
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
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 17 packages
| Packages resolved | 17 |
|---|---|
| Stale | 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_list Memory List ~95
List memory notes newest-first (titles + metadata, no bodies). Read-only. Optionally scoped by project, type, and/or scope ("portable" vs "machine-local"), and by user_id/workspace_id (default self/personal; set by the hosted relay, not local installs).
| Name | Type | Req | Description |
|---|---|---|---|
| project | – | – | – |
| scope | – | – | – |
| type | – | – | – |
| user_id | – | – | – |
| workspace_id | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
memory_search Memory Search ~155
Search memory by keyword (FTS5 BM25), optionally scoped by project/type/scope, and by user_id/workspace_id (default self/personal; set by the hosted relay, not local installs). Read-only. Returns up to ``k`` ranked notes, each with its body and metadata (id, type, project, machine of origin, scope, user_id, workspace_id, tags, timestamps). ``scope`` filters to "portable" (synced) or "machine-local" (this machine only).
| Name | Type | Req | Description |
|---|---|---|---|
| k | integer | – | – |
| project | – | – | – |
| query | string | yes | – |
| scope | – | – | – |
| type | – | – | – |
| user_id | – | – | – |
| workspace_id | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
memory_status Memory Status ~26
Report store health: counts by type/project, store paths, sync state. Read-only.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
memory_sync Memory Sync ~97
Sync memory across machines: commit local notes, pull --rebase, push. Uses git over the remote in ANAMNESIS_GIT_REMOTE (a bare repo on your Tailscale mesh); with no remote set it just commits locally. On a conflicting edit it surfaces the conflict and keeps local edits rather than dropping either side. The ``force`` flag is reserved for future use.
| Name | Type | Req | Description |
|---|---|---|---|
| force | boolean | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
memory_write Memory Write ~204
Create a durable memory note: write the markdown file and index it. Use ``type`` = procedural (verified how-tos, decisions, fixes), semantic (facts, preferences, conventions), or episodic (what happened). ``scope`` = "portable" (default; syncs to your other machines) or "machine-local" (stays on this machine only, never synced). ``user_id``/``workspace_id`` default to "self"/"personal" and are set by the hosted relay, not local installs. The note is tagged with this machine as its origin. Returns the created note's metadata. This modifies the store, so it is not auto-approved.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | – |
| project | string | – | – |
| scope | string | – | – |
| tags | – | – | – |
| title | string | yes | – |
| type | string | yes | – |
| user_id | string | – | – |
| workspace_id | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
What is the Anamnesis MCP server?
Anamnesis is an MCP server listed in the public MCP registry as io.github.oscardvs/anamnesis. Cross-machine, file-first memory for Claude Code: markdown + SQLite FTS5, synced with git. This page covers its PyPI package (anamnesis-memory).
Is the Anamnesis MCP server safe to use?
Anamnesis scores 77 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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 Anamnesis MCP server expose?
Anamnesis exposes 5 tools: memory_search, memory_list, memory_status, memory_write, memory_sync. Their descriptions and schemas cost roughly 577 tokens of context every time the server is loaded.
Is the Anamnesis MCP server still maintained?
Anamnesis 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.