open-memex
Independent MCP server safety profile · methodology
Avoid · safety score 62/100 · runs install script
1,242npm downloads/wk
3dsince last publish
v0.10.0latest version
—provenance
Safety signals
Install script (code on
npm i)YES — runs arbitrary codeRepository (source to review)https://github.com/stoneskin/open-memex
LicenseApache-2.0
Direct dependencies4
Last audited2026-11-18
Flags
highThe package runs an install-time script (preinstall, install or postinstall): arbitrary code on `npm i`. A common attack vector; review the source.
Verify open-memex live right now — free:
Already installed it? That verdict is about today. Whether this package changed after you trusted it — install script added later, ownership swapped, repository removed — is tracked separately in Drift Watch:
GET /mcp/verify?package=open-memex. See the whole ecosystem in the State of MCP Security report, or browse all audited servers.Already installed it? That verdict is about today. Whether this package changed after you trusted it — install script added later, ownership swapped, repository removed — is tracked separately in Drift Watch:
GET /mcp/drift.json?packages=open-memexDO NOT INSTALL without reviewing the source: risk signals present. Data from PulseFeed's independent MCP audit (last crawl 2026-11-18). An install script is not automatically malicious — native builds use them — but each is an unreviewed code-execution vector worth checking. All audited MCP servers →