mcp@0.48.1

VERIFIED· not started

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

Registry npm (MCP server)Publisher codemem · publishing for 241 daysInstalls 5,656Last detonated 5d ago
$claude mcp add mcp -- npx -y @codemem/mcp
WatchReport an issue

Coverage

Not started: dependency install failed; the server itself was not observed.
Tested
the dependency install step · every file read, file written and host contacted by what ran
Not tested
server startup · the tool list · tool behavior

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 codeAlso claude.ai, chatgpt.com, googleusercontent.com — not the publisher's domain; check what for before connecting.
What the honeypot saw
no credential files read · no network
What we could not test
server startup · the tool list · tool behavior

Connect it under the guard. Not started: dependency install failed; the server itself was not observed. 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 @codemem/mcp

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; not started: dependency install failed; the server itself was not observed) on 2026-11-09 and scored it 90/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 · 25 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
24sprocessdependency install exit 1 · (Use `node --trace-warnings ...` to show where the warning was created) npm error Cannot read properties of null (reading 'edgesOut') npm error A complete log of this run can be found in: /tmp/ks-detonate-Bew0FV/task/home/.npm/_logs/2026-11-09T18_35_05_667Z-debug-0.log
24sclaimednot started: dependency install failed (exit 1); the server itself was not observed
24sprocessscript backend runs setup only
24sprocessno install scripts to re-run

Static findings

MEDIUM
File permission modification commanddist/http.js:14 · File permission modification command — agent changes file ownership/permissionsimport { chmod as E } from "node:fs/promises";Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.
AST05
HIGH
Credential pass-through configurationdist/audit.d.ts:25 · Credential pass-through configuration — agent relays sensitive credentials* leaks in; callers should never need to pass token/code material here.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST02
LOW
Instructs the agent to modify its persistent memory or instruction filesdist/tool-context.d.ts:8 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file* project, the write session's cwd, and distill's AGENTS.md lookup, so aFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.
AST01

Cost to the agent

Instructions loaded
≈34 tok
1 file · 32 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 @codemem/mcp@0.48.1 as of 5d ago. This is the package itself, not its dependencies.