memory@2.2.1

VERIFIED· install only

Publisher claims: "Knowledge graph-based persistent memory system." Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry Docker MCP CatalogPublisher modelcontextprotocol · publishing for 731 daysInstalls 585KLast detonated 12 h ago
$docker run -i --rm mcp/memory
WatchReport an issue

Coverage

Bundled scripts ran with no arguments; no agent task scenario for this bundle.
Tested
1 of 1 bundled script run with no arguments, with decoy credentials in the environment · every file read, file written and host contacted by what ran
Not tested
use of the skill by an agent

What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.

Before you give it your token

It will ask for
no credential variables read in the code
Where it talks to
no vendor host named in the code
What we saw when it ran
no credential files read · no network
What we could not test
use of the skill by an agent

Connect it under the guard. Bundled scripts ran with no arguments; no agent task scenario for this bundle. The code names no credential variable; the guard pins the network to what the honeypot saw and logs every call.

$vet-skills run --net declared -- docker run -i --rm mcp/memory

Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; bundled scripts ran with no arguments; no agent task scenario for this bundle) on 2026-11-19 and scored it 89/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 0 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
0.0sprocessbundled script run in the sandbox with no arguments · not named in the instructions
0.1sprocessexited 1: Node.js v22.23.5
0.1sprocess1 of 1 bundled script run with no arguments
0.1sprocessscript backend runs setup only
0.1sprocessscript backend runs setup only
0.1sprocessno install scripts to re-run

Static findings

MEDIUM
File permission modification commandDockerfile:65 · File permission modification command — agent changes file ownership/permissionsRUN mkdir /data && chown node:node /dataFix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.
AST05
MEDIUM
npx invocation of non-well-known packageindex.ts:131 · npx invocation of non-well-known package — may execute untrusted code"which npm manages: reinstalling or updating the server, or clearing the npx cache, " +Fix: Pin versions and sources; vendor anything fetched at install time.
AST06
MEDIUM
npx invocation of non-well-known packageindex.ts:115 · npx invocation of non-well-known package — may execute untrusted code// and npm treats that tree as its own: a reinstall, an update or a cleared npxFix: Pin versions and sources; vendor anything fetched at install time.
AST06
MEDIUM
File permission modification commandpackage.json:25 · File permission modification command — agent changes file ownership/permissions"build": "tsc && shx chmod +x dist/*.js",Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.
AST05
MEDIUM
File permission modification commandindex.ts:865 · File permission modification command — agent changes file ownership/permissions// the umask can only narrow that. The chmod then restores any bits theFix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.
AST05
MEDIUM
npx invocation of non-well-known package__tests__/file-path.test.ts:299 · npx invocation of non-well-known package — may execute untrusted codeit("warns about a file inside an npx or npm install's node_modules", () => {Fix: Pin versions and sources; vendor anything fetched at install time.
AST06
MEDIUM
npx invocation of non-well-known packageindex.ts:113 · npx invocation of non-well-known package — may execute untrusted code// undefined for any other path. npx and npm install the server underFix: Pin versions and sources; vendor anything fetched at install time.
AST06
LOW
Refusal suppressionREADME.md:316 · Refusal suppression — attempting to prevent safety responses · informational: not an instruction file…ill answered, even when the graph is at or over a limit. - The delete tools are never refused, so a graph over a limit (one that grew before the limit was set, or lowered) …Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.
AST01

Cost to the agent

Instructions loaded
≈40 tok
1 file · 30 in bundle

Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.

Known vulnerabilities

Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.