@prom.codes/memory-mcp
npm
v0.16.0
Published by @prom.codes — no publish provenance and no vendor-owned scope, so the publisher could not be verified. The repository link below is self-declared.
Every server starts at 100. These are the exact deductions the deterministic engine applied — each one reproducible, none of it an opinion or an LLM's guess:
| Points | What was found | Category |
|---|---|---|
| −2.1 | Package has no source repository MTC-SUP-011 | supply-chain |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind the deduction.
In the server's implementation (`dist/bin.js:1995`): Reading private keys / cloud credentials, or serializing the whole environment, is a sensitive-data source that becomes exfiltration when combined with any egress. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: id_rsa
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/bin.js
In the server's implementation (`dist/bin.js:37`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: child_process
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/bin.js
"@prom.codes/memory-mcp" declares no repository URL, so its published artifact cannot be compared against reviewable source.
Fix: Prefer packages that link to public, reviewable source.
Location: package @prom.codes/memory-mcp
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.16.0 latest |
A 98/100 | 3 | 1.5.0 | 2026-07-22 |
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan @prom.codes/memory-mcp --online
Independent packages implementing the same tool, scanned with the same engine. Compare all 34 side by side →
The official knowledge-graph memory server: persistent entities, relations and observations.
Semantic memory and knowledge management for Claude Code.
Security scan results for the Memory (agentage) MCP server.
Security scan results for the Memory (mkusaka) MCP server.
Security scan results for the Memory (exaudeus) MCP server.
Hosted persistent memory for AI agents that reinforces useful facts and lets the rest fade, shared across Claude Code, Cursor, VS Code, and ChatGPT.
Security scan results for the Admin Contracts MCP server.
Security scan results for the Ads MCP server.
Security scan results for the Airflow MCP server.
Security scan results for the Alertmanager MCP server.
Security scan results for the Analytics MCP server.
Security scan results for the Analytics MCP server.