Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Anamnesis

PYPI · ANAMNESIS-MEMORY

Cross-machine, file-first memory for Claude Code: markdown + SQLite FTS5, synced with git

Available components

−2 this week 89 Trust /100

Last scanned (9 hours ago)

Scores higher than 91% of PyPI servers

Category Memory and Knowledge

Trust breakdown (7 categories)

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 build step with no custom scripting around it. View diagnostics → Pass
  • 1 of 17 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to oscardvs/anamnesis). View diagnostics → Pass
  • Clear OSI-approved license (Apache-2.0).Pass
  • Actively maintained (last published 122 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 Management83
  • Stability observed for 25 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
Changelog

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 −3
    • Stability: pass → 0.83 functional
  • 30 Oct 26 +1
    • Stability: 0.97 → pass security
  • 29 Oct 26 −1
    • Stability: pass → 0.97 functional
  • 23 Oct 26 +1
    • Stability: 0.97 → pass security
  • 22 Oct 26 −1
    • Stability: pass → 0.97 functional
  • 16 Oct 26 +1
    • Stability: 0.97 → pass security
  • 14 Oct 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.

  • 5 Oct 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.

Diagnostics

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 pypi/anamnesis-memory@0.1.3

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo oscardvs/anamnesis
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/oscardvs/anamnesis/.github/workflows/publish.yml@refs/tags/v0.1.3
Rekor log index 2079354380
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:74274d925b684228e6623e6a4cb3a03d15d09d12226fc87d5c858158283d23c4

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 →

MCP tools · 5 exposed · ~577 tokens

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 →

Tool Tokens
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).

NameTypeReqDescription
project–––
scope–––
type–––
user_id–––
workspace_id–––
NameTypeReqDescription
resultarrayyes–

No examples provided.

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).

NameTypeReqDescription
kinteger––
project–––
querystringyes–
scope–––
type–––
user_id–––
workspace_id–––
NameTypeReqDescription
resultarrayyes–

No examples provided.

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 ~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.

NameTypeReqDescription
forceboolean––

Structured output declared, but exposes no named fields.

No examples provided.

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.

NameTypeReqDescription
bodystringyes–
projectstring––
scopestring––
tags–––
titlestringyes–
typestringyes–
user_idstring––
workspace_idstring––

Structured output declared, but exposes no named fields.

No examples provided.

Install

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

# add to Claude Code
claude mcp add oscardvs-anamnesis -- uvx anamnesis-memory
Common questions

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 89 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. Its build provenance is signed and verified. 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 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 Anamnesis MCP server under?

Anamnesis 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.