Memory Service MCP Server
mcp-memory-service
PyPI
v11.5.4
Published by an unidentified publisher — 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 |
|---|---|---|
| −23.1 | Dynamic evaluation of a non-literal value ×2 MTC-SRC-010 | injection |
| −15.4 | Assembled command execution and dynamic evaluation in the same server MTC-SRC-011 | injection |
| −6.3 | Untrusted input concatenated into a command sink MTC-SRC-009 | injection |
| −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.
Findings 24
high Dynamic evaluation of a non-literal value (claude-hooks/core/topic-change.js)MTC-SRC-010
In the server's implementation (`claude-hooks/core/topic-change.js:155`): Evaluating a runtime value as code (rather than a fixed literal) executes whatever reaches it — a direct RCE primitive, and almost never necessary in legitimate code. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: eval(
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 claude-hooks/core/topic-change.js
high Dynamic evaluation of a non-literal value (claude-hooks/utilities/dynamic-context-updater.js)MTC-SRC-010
In the server's implementation (`claude-hooks/utilities/dynamic-context-updater.js:377`): Evaluating a runtime value as code (rather than a fixed literal) executes whatever reaches it — a direct RCE primitive, and almost never necessary in legitimate code. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: eval(
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 claude-hooks/utilities/dynamic-context-updater.js
high Assembled command execution and dynamic evaluation in the same serverMTC-SRC-011
The implementation builds shell commands out of runtime values AND evaluates runtime values as code. Each is a separate arbitrary-execution primitive; a server exposing both gives anything that reaches either one a direct path to running attacker-chosen code.
Fix: Remove the dynamic eval, and pass command arguments as an argv array instead of building a shell string. If both are genuinely required, constrain and validate every value that can reach them.
Location: server implementation
high Dynamic code execution in server code (claude-hooks/core/topic-change.js)MTC-SRC-001
In the server's implementation (`claude-hooks/core/topic-change.js:155`): Evaluating strings as code is the most direct RCE primitive; if any tool input reaches it, the server executes attacker-chosen code. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: eval(
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 claude-hooks/core/topic-change.js
high Dynamic code execution in server code (claude-hooks/utilities/dynamic-context-updater.js)MTC-SRC-001
In the server's implementation (`claude-hooks/utilities/dynamic-context-updater.js:377`): Evaluating strings as code is the most direct RCE primitive; if any tool input reaches it, the server executes attacker-chosen code. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: eval(
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 claude-hooks/utilities/dynamic-context-updater.js
high Dynamic code execution in server code (scripts/maintenance/update_graph_relationship_types.py)MTC-SRC-001
In the server's implementation (`scripts/maintenance/update_graph_relationship_types.py:141`): Evaluating strings as code is the most direct RCE primitive; if any tool input reaches it, the server executes attacker-chosen code. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: eval(
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 scripts/maintenance/update_graph_relationship_types.py
high Dynamic code execution in server code (scripts/run_memory_server.py)MTC-SRC-001
In the server's implementation (`scripts/run_memory_server.py:36`): Evaluating strings as code is the most direct RCE primitive; if any tool input reaches it, the server executes attacker-chosen code. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: exec(compile(
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 scripts/run_memory_server.py
high Dynamic code execution in server code (src/mcp_memory_service/quality/onnx_ranker.py)MTC-SRC-001
In the server's implementation (`src/mcp_memory_service/quality/onnx_ranker.py:235`): Evaluating strings as code is the most direct RCE primitive; if any tool input reaches it, the server executes attacker-chosen code. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: eval(
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 src/mcp_memory_service/quality/onnx_ranker.py
high Shell/command execution in server code (claude-hooks/core/session-start.js)MTC-SRC-002
In the server's implementation (`claude-hooks/core/session-start.js:326`): 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 claude-hooks/core/session-start.js
high Shell/command execution in server code (claude-hooks/install_hooks.py)MTC-SRC-002
In the server's implementation (`claude-hooks/install_hooks.py:122`): 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: subprocess.run(
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 claude-hooks/install_hooks.py
high Shell/command execution in server code (claude-hooks/scripts/ensure-server.js)MTC-SRC-002
In the server's implementation (`claude-hooks/scripts/ensure-server.js:15`): 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 claude-hooks/scripts/ensure-server.js
high Shell/command execution in server code (claude-hooks/tests/ensure-server.test.js)MTC-SRC-002
In the server's implementation (`claude-hooks/tests/ensure-server.test.js:11`): 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 claude-hooks/tests/ensure-server.test.js
high Shell/command execution in server code (claude-hooks/tests/integration-test.js)MTC-SRC-002
In the server's implementation (`claude-hooks/tests/integration-test.js:477`): 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 claude-hooks/tests/integration-test.js
high Shell/command execution in server code (claude-hooks/tests/test-code-execution.js)MTC-SRC-002
In the server's implementation (`claude-hooks/tests/test-code-execution.js:8`): 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 claude-hooks/tests/test-code-execution.js
high Shell/command execution in server code (claude-hooks/tests/test-permission-request.js)MTC-SRC-002
In the server's implementation (`claude-hooks/tests/test-permission-request.js:9`): 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 claude-hooks/tests/test-permission-request.js
high Shell/command execution in server code (claude-hooks/utilities/git-analyzer.js)MTC-SRC-002
In the server's implementation (`claude-hooks/utilities/git-analyzer.js:8`): 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 claude-hooks/utilities/git-analyzer.js
high Shell/command execution in server code (claude-hooks/utilities/mcp-client.js)MTC-SRC-002
In the server's implementation (`claude-hooks/utilities/mcp-client.js:6`): 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 claude-hooks/utilities/mcp-client.js
high Shell/command execution in server code (claude-hooks/utilities/project-detector.js)MTC-SRC-002
In the server's implementation (`claude-hooks/utilities/project-detector.js:8`): 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 claude-hooks/utilities/project-detector.js
medium Untrusted input concatenated into a command sink (claude-hooks/utilities/git-analyzer.js)MTC-SRC-009
In the server's implementation (`claude-hooks/utilities/git-analyzer.js:59`): A shell/process command assembled from concatenated or interpolated values is command injection when any part is attacker-influenced — the OWASP canonical RCE flow. Verify what reaches the interpolated value. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: execSync(`git show --name-only --pretty="" ${
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 claude-hooks/utilities/git-analyzer.js
medium Dynamic module load from a non-literal (claude-hooks/tests/integration-test.js)MTC-SRC-005
In the server's implementation (`claude-hooks/tests/integration-test.js:481`): Loading a module chosen at runtime (from a variable) can pull in and run attacker-influenced code paths. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: require(module)
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 claude-hooks/tests/integration-test.js
medium Dynamic module load from a non-literal (scripts/service/service_utils.py)MTC-SRC-005
In the server's implementation (`scripts/service/service_utils.py:128`): Loading a module chosen at runtime (from a variable) can pull in and run attacker-influenced code paths. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: __import__(
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 scripts/service/service_utils.py
medium Dynamic module load from a non-literal (scripts/utils/smithery_wrapper.py)MTC-SRC-005
In the server's implementation (`scripts/utils/smithery_wrapper.py:50`): Loading a module chosen at runtime (from a variable) can pull in and run attacker-influenced code paths. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: __import__(
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 scripts/utils/smithery_wrapper.py
medium Dynamic module load from a non-literal (src/mcp_memory_service/dependency_check.py)MTC-SRC-005
In the server's implementation (`src/mcp_memory_service/dependency_check.py:100`): Loading a module chosen at runtime (from a variable) can pull in and run attacker-influenced code paths. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: __import__(
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 src/mcp_memory_service/dependency_check.py
low Package has no source repositoryMTC-SUP-011
"mcp-memory-service" 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 mcp-memory-service
What this scan could not see
- No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
Versions
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 |
|---|---|---|---|---|
v11.5.4 latest |
F 53/100 | 24 | 1.5.0 | 2026-07-22 |
Embed this score
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.
Verify this score yourself
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 mcp-memory-service --online --registry pypiMore in Developer Tools
Security scan results for the 199bio Mcp Limitless MCP server.
Security scan results for the 1mcp MCP server.
Security scan results for the 1stay MCP server.
Generates production-ready UI components from natural language, inspired by v0.
Security scan results for the 2slides MCP server.
Security scan results for the 3d MCP server.