io.github.drQedwards/pmll-memory-mcp
NPM · PMLL-MEMORY-MCP
PMLL Memory MCP — persistent KV context memory and Q-promise deduplication.
Available components
Last scanned (9 hours ago)
Scores higher than 61% of npm 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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- 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
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 63 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability75
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 531 tokens (~106/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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.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 6 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.
- 5 Nov 26 +1
- Stability: 0.97 → pass security
- 3 Nov 26 −1
- Stability: pass → 0.93 functional
- 28 Oct 26 +1
- Stability: 0.97 → pass security
- 27 Oct 26 −1
- Stability: pass → 0.97 functional
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 21 Oct 26 +1
- Stability: 0.97 → pass security
- 20 Oct 26 −1
- Stability: pass → 0.97 functional
- 17 Oct 26 +2
- Stability: 0.83 → pass 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 npm/pmll-memory-mcp@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| 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 →
flush ~63
Clear all short-term KV slots for a session. Call at agent task completion to free memory. Mirrors the teardown of a memory_silo_t allocation (PMLL.c::free_pml).
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | string | yes | The session identifier (from `init`). |
No output schema declared.
No examples provided.
init ~98
Initialise the PMLL memory silo for an agent session. Call this once at the start of every agent task, as the 3rd initializer alongside Playwright. Sets up the KV silo and prepares the Q-promise chain for the session.
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | string | yes | Unique identifier for this agent task (e.g. a UUID). |
| silo_size | integer | – | Maximum number of KV slots (mirrors memory_silo_t.size). |
No output schema declared.
No examples provided.
peek ~84
Non-destructive context check — the core deduplication primitive. Call this before any Playwright or other MCP tool invocation to check whether the required context already exists in the PMLL silo or is in-flight as a Q-promise.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | The context key to look up. |
| session_id | string | yes | The session identifier (from `init`). |
No output schema declared.
No examples provided.
resolve ~109
Check or resolve a Q-promise continuation. Mirrors the `QThenCallback` mechanism in Q_promise_lib/Q_promises.h — the callback is invoked when a QMemNode's payload becomes available. If the promise is already resolved, returns its payload immediately. If still pending, returns `{status: "pending", payload: null}`.
| Name | Type | Req | Description |
|---|---|---|---|
| promise_id | string | yes | The promise identifier previously registered. |
| session_id | string | yes | The session identifier (for context; not used to namespace promises). |
No output schema declared.
No examples provided.
set ~105
Store a KV pair in the session's PMLL memory silo. Call after a successful (non-cached) MCP tool invocation to populate the silo so future `peek` calls return a cache hit. Mirrors PMLL.c::update_silo() writing a var/value pair into the silo.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | The context key. |
| session_id | string | yes | The session identifier (from `init`). |
| value | string | yes | The string value to cache. |
No output schema declared.
No examples provided.
How do I install the io.github.drQedwards/pmll-memory-mcp server?
io.github.drQedwards/pmll-memory-mcp runs locally as an npm package, launched with npx -y pmll-memory-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · pmll-memory-mcp
claude mcp add drqedwards-pmll-memory-mcp -- npx -y pmll-memory-mcp
What is the io.github.drQedwards/pmll-memory-mcp server?
io.github.drQedwards/pmll-memory-mcp is listed in the public MCP registry as io.github.drQedwards/pmll-memory-mcp. PMLL Memory MCP, persistent KV context memory and Q-promise deduplication. This page covers its npm package (pmll-memory-mcp).
Is the io.github.drQedwards/pmll-memory-mcp server safe to use?
io.github.drQedwards/pmll-memory-mcp scores 79 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares no install or post-install scripts. 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.drQedwards/pmll-memory-mcp server expose?
io.github.drQedwards/pmll-memory-mcp exposes 5 tools: init, peek, set, resolve, flush. Their descriptions and schemas cost roughly 459 tokens of context every time the server is loaded.
Is the io.github.drQedwards/pmll-memory-mcp server still maintained?
io.github.drQedwards/pmll-memory-mcp 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 io.github.drQedwards/pmll-memory-mcp server under?
io.github.drQedwards/pmll-memory-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.