smartmemory-mcp@2.0.2
VERIFIED· install onlyPublisher claims: "Unified SmartMemory MCP server — tiered tools, local + remote backends" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Bundled scripts ran with no arguments; no agent task scenario for this bundle.- Tested
- 8 of 57 bundled scripts run with no arguments (the rest were not run: per-bundle cap), 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
SMARTMEMORY_API_KEYConfiguration, not credentials: EVAL_DATA_DIR, EVAL_LOGGING, SMARTMEMORY_API_URL, SMARTMEMORY_DATA_DIR, SMARTMEMORY_MCP_FULL_TOOLS, SMARTMEMORY_MCP_MODE, SMARTMEMORY_RECALL_FLOOR, SMARTMEMORY_RULES_DIR, SMARTMEMORY_TRANSCRIPTS_DIR, SMARTMEMORY_WARM_RERANKER- Where it talks to
- smartmemory.ai (its own)Also claude.ai, grok.com, chatgpt.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
- use of the skill by an agent
Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names claude.ai, grok.com, chatgpt.com as well as its own vendor. The guard injects SMARTMEMORY_API_KEY only into requests to smartmemory.ai (and its subdomains) and refuses the rest.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
What changed since 1.5.28
vet-skills diff smartmemory-mcp 1.5.28 2.0.2In the sandbox, this version reached for nothing 1.5.28 did not. Compared from the two recorded runs, not from source.
The guard can hold an update like this until someone approves it (runtime.on_change: hold). A change that only shows with a real credential, or on a path the run did not reach, is not in a trace and so not in this comparison.
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-18 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 · 1 s · 2 scenarios · 0 deviationsStatic findings
result = subprocess.run(Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.False, "No API key. Pass api_key or set SMARTMEMORY_API_KEY env var."Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.result = subprocess.run(Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.Cost to the agent
Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.
Known vulnerabilities
No advisories in OSV for smartmemory-mcp@2.0.2 as of 48 min ago. This is the package itself, not its dependencies.