Skills/npm/mem-ai-mcp-server

mem-ai-mcp-server@0.2.0

VERIFIED

Publisher claims: "MCP server for mem.ai API integration" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry npm (MCP server)Publisher hskksk · publishing for 320 daysInstalls 649Last detonated 33 h ago
$claude mcp add mem-ai-mcp-server -- npx -y @hskksk/mem-ai-mcp-server
WatchReport an issue

Coverage

Started with a decoy MEM_API_KEY; tool list observed. Tool calls with a real credential not tested.
Tested
server startup with a tagged decoy in MEM_API_KEY · MCP initialize and tools/list · every tool description, for hidden instructions · where the decoy credential went · every file read, file written and host contacted by what ran
Not tested
what the tools do when called with a real credential
Needs
MEM_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.

Before you give it your token

It will ask for
MEM_API_KEYConfiguration, not credentials: MEM_API_BASE_URL
Where it talks to
no vendor host named in the codeAlso mem.ai — 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
what the tools do when called with a real credential

Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names mem.ai as well as its own vendor. The guard injects MEM_API_KEY only into requests to the host you bind (and its subdomains) and refuses the rest.

$vet-skills run --net declared -- npx -y @hskksk/mem-ai-mcp-server

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) on 2026-11-09 and scored it 95/100 (Verified). It did what it claims and nothing else we could detect: no undeclared network egress, no credential reads, no persistent instruction writes. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 49 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
8.6sprocessdependency install exit 0
29sprocessrelaunched with a decoy MEM_API_KEY (tagged; nothing real)
49sclaimed11 tools with a decoy MEM_API_KEY: mem_it, create_note, get_note, delete_note, list_notes, search_notes, create_collection, get_collection, delete_collection, list_collections, search_collections
49sprocessscript backend runs setup only
49sprocessno install scripts to re-run

Static findings

No findings across 1,633 lines in 43 files.

Cost to the agent

Instructions loaded
≈50 tok
1 file · 43 in bundle
Tool list per prompt
≈1,338 tok
11 tools · 122 per tool
Handshake
396 ms
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 59

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 @hskksk/mem-ai-mcp-server@0.2.0 as of 33 h ago. This is the package itself, not its dependencies.

mem-ai-mcp-server@0.2.0 safety verdict: Verified — KillerSkills