Skills/PyPI/powermem-mcp

powermem-mcp@0.2.0

VERIFIED· not started

Publisher claims: "PowerMem MCP Server - Model Context Protocol server for PowerMem memory management" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry PyPI (MCP server)Publisher oceanbase · publishing for 438 daysInstalls 55Last detonated 3 h ago
$claude mcp add powermem-mcp -- uvx powermem-mcp
WatchReport an issue

Coverage

Not started: dependency install failed; the server itself was not observed.
Tested
install scripts, with decoy credentials in place · second launch with the clock 45 days ahead · 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
powermem.ai (its own)Also coscl.org.cn — 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 and talks to powermem.ai, its own; the guard pins the network to what the honeypot saw and logs every call.

$vet-skills run --net declared -- uvx powermem-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 (3 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-15 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 · 3 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessinstall script run in the sandbox
0.0sprocessexited 1: ModuleNotFoundError: No module named 'setuptools'
0.2sprocessdependency install exit 1 ·
0.2sclaimednot started: dependency install failed (exit 1); the server itself was not observed
0.2sprocessscript backend runs setup only
0.2sprocesssecond launch, clock +45 days, CI unset
0.3sprocessexited 1: ModuleNotFoundError: No module named 'setuptools'

Static findings

HIGH
Access to sensitive file pathspowermem_mcp/server.py:41 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files2. Project root directory's .envFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathspowermem_mcp/server.py:39 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filescreate_memory() will automatically call auto_config() to load configuration, searches for .env files in:Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathspowermem_mcp/server.py:36 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesUses singleton pattern, automatically loads configuration from .env and creates Memory instance on first callFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathspowermem_mcp/server.py:40 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files1. Current working directory's .envFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathspowermem_mcp/server.py:42 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files3. examples/configs/.envFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05

Cost to the agent

Instructions loaded
≈57 tok
1 file · 16 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 powermem-mcp@0.2.0 as of 2 h ago. This is the package itself, not its dependencies.