Skills/PyPI/mem-forensics-mcp

mem-forensics-mcp@1.2.1

VERIFIED· install only

Publisher claims: "Unified Memory Forensics MCP Server - Multi-tier engine (Rust + Python + Vol3)" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry PyPI (MCP server)Publisher x746b · publishing for 278 daysInstalls 50Last detonated 3d ago
$claude mcp add mem-forensics-mcp -- uvx mem-forensics-mcp
WatchReport an issue

Coverage

Nothing executable in the bundle ran; the trace covers the install step only.
Tested
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
VIRUSTOTAL_API_KEYConfiguration, not credentials: VOLATILITY3_PATH
Where it talks to
no vendor host named in the codeAlso microsoft.com, evil.com, sans.org, mitre.org — 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 microsoft.com, evil.com, sans.org, mitre.org as well as its own vendor. The guard injects VIRUSTOTAL_API_KEY only into requests to the host you bind (and its subdomains) and refuses the rest.

$vet-skills run --net declared -- uvx mem-forensics-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 (1 scenario; nothing executable in the bundle ran; the trace covers the install step only) on 2026-11-11 and scored it 91/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 · 1 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
0.0sprocessscript backend runs setup only
0.0sprocessscript backend runs setup only
0.0sprocessno install scripts to re-run

Static findings

MEDIUM
Python subprocess execution detectedmem_forensics_mcp/core/vol3_runner.py:612 · Python subprocess execution detectedresult = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
AST05

No other findings across 20,703 lines in 81 files.

Cost to the agent

Instructions loaded
≈1,251 tok
2 files · 81 in bundle

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 mem-forensics-mcp@1.2.1 as of 3d ago. This is the package itself, not its dependencies.