Skills/npm/install

install@0.0.2

VERIFIED· startup only

Publisher claims: "OpenMemory MCP server installation tool" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry npm (MCP server)Publisher openmemory · publishing for 529 daysInstalls 8,142Last detonated 1 h ago
$claude mcp add install -- npx -y @openmemory/install
WatchReport an issue

Coverage

Startup only; authenticated tool behavior not tested.
Tested
server startup over stdio (initialize sent) · every file read, file written and host contacted by what ran
Not tested
the tool list (the server exited before answering) · what the tools do when called with real credentials
Needs
OPENMEMORY_API_KEY — give it to the server where it runs, through vet-skills run --secrets, so the value never enters the server's environment. Never paste a credential into a chat, a ticket or a report.

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; at startup it asked for OPENMEMORY_API_KEY
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
the tool list (the server exited before answering) · what the tools do when called with real credentials

Connect it under the guard. Startup only; authenticated tool behavior not tested. 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 -- npx -y @openmemory/install

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; startup only; authenticated tool behavior not tested) on 2026-11-21 and scored it 95/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 (it asks for OPENMEMORY_API_KEY); 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 · 44 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
3.7sprocessdependency install exit 0
24sprocessrelaunched with a decoy OPENMEMORY_API_KEY (tagged; nothing real)
44sclaimedstartup only: exited before answering, asking for OPENMEMORY_API_KEY (a decoy value was refused)
44sprocessscript backend runs setup only
44sprocessno install scripts to re-run

Static findings

No findings across 470 lines in 7 files.

Cost to the agent

Instructions loaded
≈46 tok
1 file · 7 in bundle
Tool list per prompt
≈0 tok
0 tools · 0 per tool
Handshake
no reply
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 0

Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.

Known vulnerabilities

No advisories in OSV for @openmemory/install@0.0.2 as of 37 min ago. This is the package itself, not its dependencies.