memory-boost
PYPI · MEMORY-BOOST
Markdown memory for coding agents that audits itself: drift reports and session digests.
Available components
Last scanned (18 hours ago)
Scores higher than 90% 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 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
- 0 of 28 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to arnaugonzalez/memory-boost). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 19 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 762 tokens (~95/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management67
- Stability observed for 20 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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 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.
- 16 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 14 Oct 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.
- 13 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 12 Oct 26 +18
- Malware scan: unverified → pass ▲ security
- 6 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 33. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Oct 26 +4
- Stability: unverified → 0.27 ▲ functional
- 28 Sept 26 +10
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 −15
- Malware scan: pass → unverified ▼ security
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 16 Oct 2026 · Analysed pypi/memory-boost@0.1.1
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 | arnaugonzalez/memory-boost |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/arnaugonzalez/memory-boost/.github/workflows/release.yml@refs/tags/v0.1.1 |
| Rekor log index | 2969077858 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:0141f236ba26ee84ef9c4e2cb631c7f996c667d474baf653dc7427703cace131 |
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 28 packages
| Packages resolved | 28 |
|---|---|
| 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_brief ~81
Cheap orientation (~1k tokens): wiki catalog, the project's stable context and its latest sessions. Call it at the start of a session in harnesses without a SessionStart hook, or to reload a project's context mid-session. `project` is a project name or a directory path.
| Name | Type | Req | Description |
|---|---|---|---|
| budget | integer | – | – |
| project | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
memory_checkpoint ~173
Save this session's working state (a small JSON, no indexing) so it survives context compaction and parallel sessions on the same project can see it. Call it after each milestone: task = current goal (1 line), done = finished steps (accumulated), next_step = the concrete next step, files = files touched. session_id: the `checkpoint_session=` value injected at session start, or any stable id. Set status=done when the session ends (after memory_save).
| Name | Type | Req | Description |
|---|---|---|---|
| agent | string | – | – |
| done | – | – | – |
| files | – | – | – |
| next_step | – | – | – |
| notes | – | – | – |
| plan_ref | – | – | – |
| project | string | yes | – |
| session_id | string | yes | – |
| status | string | – | – |
| task | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
memory_drift ~64
What in the memory has drifted: decisions past review_by, superseded decisions without a successor, project pages with no session for weeks, busy projects with no recorded decisions, checkpoints left open. Whole wiki, or one project's findings.
| Name | Type | Req | Description |
|---|---|---|---|
| project | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
memory_lesson ~123
Record a lesson that should reach other projects: what worked (or failed), the tools involved and when it applies. `applies_when` are stack/situation tags (e.g. ["fastapi", "celery", "e2e-tests"]); projects whose page lists matching `tags:` get this lesson in their session brief. `learned_on` = this project's slug.
| Name | Type | Req | Description |
|---|---|---|---|
| applies_when | array | yes | – |
| body | string | yes | – |
| learned_on | – | – | – |
| name | string | yes | – |
| title | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
memory_page ~60
Read a wiki page by name (e.g. 'my-api'), or one section of it (a heading or the anchor returned by memory_recall). Prefer this over reading the whole file.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
| section | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
memory_recall ~83
Full-text search over wiki pages and log entries. Each hit is tagged [kind | date | freshness]; current knowledge is listed before historic and superseded. Historic hits are omitted unless include_historic=true.
| Name | Type | Req | Description |
|---|---|---|---|
| include_historic | boolean | – | – |
| limit | integer | – | – |
| project | – | – | – |
| query | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
memory_resume ~65
Return this session's checkpoint (if session_id is given) plus one line per other active session on the project. Use after a compaction or when picking up unfinished work; much cheaper than memory_recall.
| Name | Type | Req | Description |
|---|---|---|---|
| project | string | yes | – |
| session_id | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
memory_save ~113
Record what was done in a session: one raw JSONL event plus one compiled entry in wiki/log.md (creates the project page if it does not exist yet). `action` is a one-line summary; `detail` a longer bullet; `pending` what is left to do. Does not commit anything to git.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| agent | string | – | – |
| detail | – | – | – |
| pending | – | – | – |
| project | string | yes | – |
| result | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
How do I install the memory-boost MCP server?
memory-boost runs locally as a PyPI package, launched with uvx memory-boost. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · memory-boost
claude mcp add arnaugonzalez-memory-boost -- uvx memory-boost
What is the memory-boost MCP server?
memory-boost is an MCP server listed in the public MCP registry as io.github.arnaugonzalez/memory-boost. Markdown memory for coding agents that audits itself: drift reports and session digests. This page covers its PyPI package (memory-boost).
Is the memory-boost MCP server safe to use?
memory-boost scores 87 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 16 October 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 memory-boost MCP server expose?
memory-boost exposes 8 tools: memory_brief, memory_recall, memory_page, memory_save, memory_checkpoint, and 3 more. Their descriptions and schemas cost roughly 762 tokens of context every time the server is loaded.
Is the memory-boost MCP server still maintained?
memory-boost is still listed as active in the MCP registry. We last reached this channel on 16 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 memory-boost MCP server under?
memory-boost declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.