io.github.ignatenkofi/memshelf-mcp
PYPI · MEMSHELF-MCP
Working memory for AI agents: digest-indexed episodes on a git shelf, recalled a section at a time.
Available components
Last scanned (21 hours ago)
Scores higher than 74% 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
- 1 of 30 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to ignatenkofi/memshelf-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 27 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability67
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 937 tokens (~62/item across 15 items; 15 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 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
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 16 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.
- 29 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 24 Oct 26 +1
- Stability: 0.97 → pass security
- 23 Oct 26 −1
- Stability: pass → 0.97 functional
- 18 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 17 Oct 26 −14
- Malware scan: pass → unverified ▼ security
- Stability: 0.97 → pass security
- 15 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.
- 14 Oct 26 +55
- Injection markers: unverified → pass ▲ security
- Malware scan: unverified → pass ▲ security
- Schema quality: 52 → 62 ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Stability: unverified → 0.90 ▲ functional
- Package version: 0.3.0 → 0.4.0 functional
- 13 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- Package version: 0.3.0 → 0.4.0 functional
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 4 Nov 2026 · Analysed pypi/memshelf-mcp@0.4.0
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 | ignatenkofi/memshelf-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/ignatenkofi/memshelf-mcp/.github/workflows/release.yml@refs/tags/v0.4.0 |
| Rekor log index | 3131270367 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:6e5d8abcf27adbe785bbe367619b8f2c097772c14e2c8a485b500a71b62a0de4 |
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 30 packages
| Packages resolved | 30 |
|---|---|
| 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 →
memshelf_advise ~64
Report what your context window is made of and what you could put down — breakdown plus ranked proposals; writes nothing. Pass your window's occupants (label, size, live or not); with none it reports the shelf alone.
| Name | Type | Req | Description |
|---|---|---|---|
| params | – | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
memshelf_doctor ~58
Diagnose shelf integrity: episode schema, digest contract at rest, leaked secrets, ledger consistency, INDEX budget. Read-only; fixes nothing. `check_remote` adds the network probe for a public remote.
| Name | Type | Req | Description |
|---|---|---|---|
| params | – | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
memshelf_import ~56
Retro-shelve an exported dialog without pulling it through context: `discover` lists conversations by content markers, `extract` writes one cleaned conversation to a working file for segmenting and shelving.
| Name | Type | Req | Description |
|---|---|---|---|
| params | – | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
memshelf_index ~44
Return the shelf INDEX — the small recall entry point. Read it before answering anything about past work, then recall only what you need.
| Name | Type | Req | Description |
|---|---|---|---|
| params | – | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
memshelf_init ~50
Create (or top up) a memory shelf: layout, categories, INDEX preamble, POLICY.md, shelf.yml. Idempotent; never overwrites existing files.
| Name | Type | Req | Description |
|---|---|---|---|
| params | – | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
memshelf_lint_digest ~55
Check a digest against the contract while it is still being written — the same validator `memshelf_shelve` runs, writing nothing. `strict` turns warnings into failures.
| Name | Type | Req | Description |
|---|---|---|---|
| params | – | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
memshelf_purge ~46
Drop episodes past `retain_until`, then reindex. Dry run unless `apply=true`; removes working-tree files only, git history keeps them.
| Name | Type | Req | Description |
|---|---|---|---|
| params | – | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
memshelf_rebuild ~61
Regenerate the derived files (ledger.tsv, .meta.json, INDEX.md, stats.svg) from the episodes; `check=true` only reports drift. Hand-run it only on a shelf whose bot is not rendering.
| Name | Type | Req | Description |
|---|---|---|---|
| params | – | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
memshelf_recall ~49
Fetch a shelved episode by id, or one `## Section` of it, as a data envelope. Prefer the section when it answers the question.
| Name | Type | Req | Description |
|---|---|---|---|
| params | – | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
memshelf_resolve ~57
Settle the two-writers-on-parallel-branches conflict: union derived rows, rebuild INDEX, run doctor. Episode conflicts are reported, never auto-merged; safe outside a conflict too.
| Name | Type | Req | Description |
|---|---|---|---|
| params | – | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
memshelf_rollup ~48
Archive a period's episodes behind one digest-of-digests you write, shrinking INDEX; nothing is deleted. Not the answer to `index-bloat`.
| Name | Type | Req | Description |
|---|---|---|---|
| params | – | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
memshelf_search ~40
Grep the shelf for episodes matching every query token; returns addresses and snippets. Use when the episode id is unknown.
| Name | Type | Req | Description |
|---|---|---|---|
| params | – | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
memshelf_shelve ~73
Offload one closed topic to the shelf as a durable, indexed episode — redaction, digest contract and git commit included. Derived files are not written here — they are rendered by `memshelf_rebuild` or the shelf's bot. Details: docs/tools.md.
| Name | Type | Req | Description |
|---|---|---|---|
| params | – | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
memshelf_stats ~39
Report the shelf's token economy: standing cost vs shelved mass, claimed compression, realized savings from logged recalls.
| Name | Type | Req | Description |
|---|---|---|---|
| params | – | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
memshelf_sync ~62
Fetch and fast-forward the shelf clone to its remote, writing nothing else — for a clone behind the bot's render or another session's shelve. Refuses on a dirty tree or a diverged branch, with the fix.
| Name | Type | Req | Description |
|---|---|---|---|
| params | – | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
How do I install the io.github.ignatenkofi/memshelf-mcp server?
io.github.ignatenkofi/memshelf-mcp runs locally as a PyPI package, launched with uvx memshelf-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · memshelf-mcp
claude mcp add ignatenkofi-memshelf-mcp -- uvx memshelf-mcp
What is the io.github.ignatenkofi/memshelf-mcp server?
io.github.ignatenkofi/memshelf-mcp is listed in the public MCP registry as io.github.ignatenkofi/memshelf-mcp. Working memory for AI agents: digest-indexed episodes on a git shelf, recalled a section at a time. This page covers its PyPI package (memshelf-mcp).
Is the io.github.ignatenkofi/memshelf-mcp server safe to use?
io.github.ignatenkofi/memshelf-mcp scores 77 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 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 io.github.ignatenkofi/memshelf-mcp server expose?
io.github.ignatenkofi/memshelf-mcp exposes 15 tools: memshelf_shelve, memshelf_lint_digest, memshelf_recall, memshelf_index, memshelf_search, and 10 more. Their descriptions and schemas cost roughly 802 tokens of context every time the server is loaded.
Is the io.github.ignatenkofi/memshelf-mcp server still maintained?
io.github.ignatenkofi/memshelf-mcp is still listed as active in the MCP registry. We last reached this channel on 4 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.ignatenkofi/memshelf-mcp server under?
io.github.ignatenkofi/memshelf-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.