memnest-mcp@0.32.0
VERIFIED· not startedPublisher claims: "Persistent graph memory MCP server for AI agents using LadybugDB" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
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 kiro.dev, unpkg.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.
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-11 and scored it 88/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 deviationsStatic findings
out = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.…ontext, in a later session, with no human in the loop — so a memory containing `ignore previous instructions` is a persistent, cross-session injection carrier, and the only "injection" thi…Fix: Keep SKILL.md to visible, descriptive text. Remove comments and encoded text that address the agent.r = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.# Server-level kill switch for anything that removes or overwrites data.Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.…y "injection" this server screened for was Cypher. Flagged, never rewritten and never refused: the content may legitimately be *about* prompt injection (this project stores…Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct."""Server-level kill switch should reject DELETE when env disables it."""Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.p = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.Cost to the agent
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 memnest-mcp@0.32.0 as of 3d ago. This is the package itself, not its dependencies.