SuperLocalMemory
PYPI · SUPERLOCALMEMORY · 2 COMPONENTS
Local-first memory for AI agents: recall with sources, answer checks, documents, mesh, governance.
Available components
Last scanned (4 hours ago)
Scores higher than 84% 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 Security82
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects nltk 3.10.3, a direct dependency. A fixed version is available. View diagnostics → Fail
- Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 17 of 156 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 qualixar/superlocalmemory). View diagnostics → Pass
- Clear OSI-approved license (AGPL-3.0-or-later).Pass
- Actively maintained (last published 7 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability74
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 9425 tokens (~145/item across 65 items; 58 tools + 7 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 Management57
- Stability observed for 17 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 (14% 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 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 59 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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Nov 26 0
- Dependency health: partial → 0.94 functional
- 3 Nov 26 +1
- CVE-2026-81726 affects this package: high ▼ security
- Dependency health: 0.94 → partial functional
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +16
- Malware scan: unverified → pass ▲ security
- 28 Oct 26 −4
- CVE-2026-109956 affects this package: high ▼ security
- Known CVEs: partial → fail ▼ security
- CVE-2026-81726 no longer affects this package ▲ security
- Destructive annotations: All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation. functional
- Package version: 4.2.11 → 4.2.13 functional
- Package version: 4.2.11 → 4.2.12 functional
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 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 5 Nov 2026 · Analysed pypi/superlocalmemory@4.2.13
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 | qualixar/superlocalmemory |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/qualixar/superlocalmemory/.github/workflows/pypi-publish.yml@refs/tags/v4.2.13 |
| Rekor log index | 3542550527 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:d20960ff83b0b58f49e782633cd24cf60bed6f4bf8159f9bc32b3ad4bfd8840c |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Vulnerabilities 2 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-8mgp-746c-j5xp | CVE-2026-81726 | high | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:L | yes |
| GHSA-j456-xh4h-cpf2 | CVE-2026-109956 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:L | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 156 packages
| Packages resolved | 156 |
|---|---|
| Stale | 16 |
| No linked repository | 3 |
| 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 →
slm_compress Compress Text ~89
Compress text with one tenant-scoped, TTL-bound recovery copy. mode: normalize, auto or aggressive (daemon configuration controls models). reversible keeps changed original bytes; ttl_seconds defaults to one day. Returned byte_exact distinguishes unchanged bytes from normalized prose.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | – |
| mode | string | – | – |
| reversible | boolean | – | – |
| ttl_seconds | integer | – | – |
No output schema declared.
No examples provided.
slm_loop_history List Bounded Loop Runs ~114
List recorded bounded-loop runs for a loop name, newest laps summarised. Reads the durable SLM-backed ledger (the same rows ``slm loop history`` and the dashboard show). Read-only. Args: name: Loop name to list runs for. limit: Maximum runs to return (1–200). profile_id: The profile whose runs to list (empty = the active one).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| name | string | yes | – |
| profile_id | string | – | – |
No output schema declared.
No examples provided.
slm_loop_run Run Bounded Loop ~267
Wait under hard bounds for independently executed verification. DONE requires gate_contract={"job_id": <operator registration nonce>}. The operator pins check files, declares mutable artifact paths/globs, watcher name and freshness via loops.receipt_jobs.register_job, then executes run_registered_check in a private copy. DONE copies and hashes current inputs again. Older caller-selected contracts fail closed. Hosts without secure no-follow directory handles refuse registration; the watcher exposes the platform or receipt reason in its result. Pre-start evidence requires explicit permission in that registration. Recall locates context; related text or support alone cannot pass. require_support additionally requires a supported answer check. Each lap recalls at most three memories and asks the answer check once; no reorder is requested. An online check may be billed for each lap. Missing, failed, stale or mismatched receipts halt at the configured bound.
| Name | Type | Req | Description |
|---|---|---|---|
| gate_contract | – | – | – |
| gate_min_score | number | – | – |
| gate_query | string | yes | – |
| max_iterations | integer | – | – |
| max_tokens | integer | – | – |
| max_wallclock_s | number | – | – |
| name | string | yes | – |
| no_progress_window | integer | – | – |
| poll_interval_s | number | – | – |
| require_support | boolean | – | – |
No output schema declared.
No examples provided.
slm_loop_show Show Bounded Loop Run ~127
Show every lap of one bounded-loop run, in order, from SLM memory. Read-only. Each lap carries the gate verdict plus the agent's recorded (advisory, never loop-terminating) done-claim. Args: run_id: Run identifier returned by ``slm_loop_run``. limit: Maximum laps to return (1–1000). profile_id: The profile the run was recorded in (empty = the active one).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| profile_id | string | – | – |
| run_id | string | yes | – |
No output schema declared.
No examples provided.
slm_optimize_stats Get Optimization Stats ~56
Return compression and cache statistics. Proxy/compress AND KV stats are daemon-persisted (accurate across restarts). KV counters fall back to this session's in-memory tally if the persisted counters can't be read.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
slm_retrieve Retrieve Compressed Text ~86
Retrieve original text stored during a lossy slm_compress call. Do not log or share ccr_ids — they are unguessable session tokens, but if exposed they allow retrieval by anyone with the daemon's decryption key. Args: ccr_id: UUID4 returned by slm_compress when reversible=True.
| Name | Type | Req | Description |
|---|---|---|---|
| ccr_id | string | yes | – |
No output schema declared.
No examples provided.
switch_profile Switch Memory Profile ~29
Switch the active memory profile. All operations scope to this profile.
| Name | Type | Req | Description |
|---|---|---|---|
| profile_id | string | yes | – |
No output schema declared.
No examples provided.
update_memory Update Memory ~135
Update the content of a specific memory by exact fact ID. Security note: All updates are logged with the calling agent_id. The fact_id must belong to the profile updated: ``profile_id``, or the active profile when it is empty. The active profile is not moved. Args: fact_id: Exact fact ID to update. content: New content for the memory (cannot be empty). agent_id: Identifier of the calling agent (logged for audit).
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | – | – |
| content | string | yes | – |
| fact_id | string | yes | – |
| profile_id | string | – | – |
No output schema declared.
No examples provided.
How do I install the SuperLocalMemory MCP server?
SuperLocalMemory runs locally as a PyPI package, launched with uvx superlocalmemory. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · superlocalmemory
claude mcp add qualixar-superlocalmemory -- uvx superlocalmemory
What is the SuperLocalMemory MCP server?
SuperLocalMemory is an MCP server listed in the public MCP registry as io.github.qualixar/superlocalmemory. Local-first memory for AI agents: recall with sources, answer checks, documents, mesh, governance. This page covers its PyPI package (superlocalmemory).
Is the SuperLocalMemory MCP server safe to use?
SuperLocalMemory scores 82 out of 100 on VerifyMCP. We recorded 2 known advisories against 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 SuperLocalMemory MCP server expose?
SuperLocalMemory exposes 58 tools: remember, recall, search, fetch, expand, and 53 more. Their descriptions and schemas cost roughly 9,215 tokens of context every time the server is loaded.
Is the SuperLocalMemory MCP server still maintained?
SuperLocalMemory 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 SuperLocalMemory MCP server under?
SuperLocalMemory declares the AGPL-3.0-or-later licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.