Memento (JoyciAkira) MCP Server

memento-mcp PyPI v1.2.1

Published by joyciakira — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

The Autonomous Nervous System for AI Agents — local-first MCP middleware with temporal graph memory, active coercion, and proactive goal alignment.

Trust grade
A
93/100
Last scanned get badge →
Trust
A · 93/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 93/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 7 = 93. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−6 capability blast radius (high) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

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 a deduction.

Findings 10

high Shell/command execution in server code (memento/active_coercion_hook.py)MTC-SRC-002

In the server's implementation (`memento/active_coercion_hook.py:30`): 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: return 0 paths = subprocess.check_output( ["git", "diff", "--cached", "--name-only", "--diff-filter=ACMR"

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 memento/active_coercion_hook.py

high Shell/command execution in server code (memento/git_context.py)MTC-SRC-002

In the server's implementation (`memento/git_context.py:19`): 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: dProcess.""" return subprocess.run( # noqa: S603 ["git", *args], capture_output=True, text=

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 memento/git_context.py

high Shell/command execution in server code (memento/git_ingestion.py)MTC-SRC-002

In the server's implementation (`memento/git_ingestion.py:17`): 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: r: try: r = subprocess.run( ["git", *args], capture_output=True, text=True, timeout=15, cwd=cwd

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 memento/git_ingestion.py

high Shell/command execution in server code (memento/tools/coercion.py)MTC-SRC-002

In the server's implementation (`memento/tools/coercion.py:113`): 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: "message": "exec() is a security risk and makes code hard to analyze.", "severity": "block",

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 memento/tools/coercion.py

high Shell/command execution in server code (memento/updater.py)MTC-SRC-002

In the server's implementation (`memento/updater.py:40`): 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: try: result = subprocess.run( cmd, capture_output=True, text=True,

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 memento/updater.py

low Shell/command execution in packaging/dev tooling (benchmarks/run_benchmarks.py)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`benchmarks/run_benchmarks.py:26`): 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: --tb=short"] return subprocess.call(cmd, cwd=root) if __name__ == "__main__": raise SystemExit(main())

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 benchmarks/run_benchmarks.py

low Shell/command execution in packaging/dev tooling (tests/test_active_coercion.py)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`tests/test_active_coercion.py:135`): 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: epo_root) blocked = subprocess.run( [sys.executable, "-m", "memento.active_coercion_hook"], cwd=repo

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 tests/test_active_coercion.py

low Shell/command execution in packaging/dev tooling (tests/test_active_coercion_hook.py)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`tests/test_active_coercion_hook.py:32`): 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: ]}}, f) os.system(f"cd {repo} && git init && git add . && git commit -m 'init'") bad_file =

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 tests/test_active_coercion_hook.py

low Shell/command execution in packaging/dev tooling (tests/test_mcp_tool_contracts.py)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`tests/test_mcp_tool_contracts.py:27`): 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: ws = tmp_path subprocess.run( ["git", "init"], cwd=str(ws), check=False, stdou

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 tests/test_mcp_tool_contracts.py

low Shell/command execution in packaging/dev tooling (tests/test_tools_smoke.py)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`tests/test_tools_smoke.py:44`): 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: ws = tmp_path subprocess.run( ["git", "init"], cwd=str(ws), check=False,

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 tests/test_tools_smoke.py

Tools 74

Each tool and what it can reach — statically extracted from the published source.

  • mementono sensitive capability
  • memento_add_active_coercion_ruleno sensitive capability
  • memento_add_memoryno sensitive capability
  • memento_apply_active_coercion_presetno sensitive capability
  • memento_audit_dependenciesno sensitive capability
  • memento_autonomy_decisionsno sensitive capability
  • memento_autonomy_statusno sensitive capability
  • memento_begin_sessionno sensitive capability
  • memento_check_goal_alignmentno sensitive capability
  • memento_coercionno sensitive capability
Show 64 more tools ↓
  • memento_cognitiveno sensitive capability
  • memento_compactno sensitive capability
  • memento_configureno sensitive capability
  • memento_configure_enforcementno sensitive capability
  • memento_configure_notificationsno sensitive capability
  • memento_consolidate_memoriesno sensitive capability
  • memento_delete_project_stateno sensitive capability
  • memento_dismiss_notificationno sensitive capability
  • memento_explain_retrievalno sensitive capability
  • memento_explain_searchno sensitive capability
  • memento_extract_kgno sensitive capability
  • memento_generate_tasksno sensitive capability
  • memento_get_cross_workspace_statsno sensitive capability
  • memento_get_pending_notificationsno sensitive capability
  • memento_get_predictive_cache_statsno sensitive capability
  • memento_get_project_stateno sensitive capability
  • memento_get_quality_reportno sensitive capability
  • memento_get_relevance_statsno sensitive capability
  • memento_get_warningsno sensitive capability
  • memento_graphno sensitive capability
  • memento_handoffno sensitive capability
  • memento_healthno sensitive capability
  • memento_install_git_hooksno sensitive capability
  • memento_kgno sensitive capability
  • memento_kg_healthno sensitive capability
  • memento_list_active_coercion_presetsno sensitive capability
  • memento_list_active_coercion_rulesno sensitive capability
  • memento_list_goalsno sensitive capability
  • memento_list_sessionsno sensitive capability
  • memento_memory_statsno sensitive capability
  • memento_migrate_workspace_memoriesno sensitive capability
  • memento_notificationsno sensitive capability
  • memento_pmg_add_entityno sensitive capability
  • memento_pmg_add_relationno sensitive capability
  • memento_pmg_entity_contextno sensitive capability
  • memento_pmg_summaryno sensitive capability
  • memento_pmg_what_might_breakno sensitive capability
  • memento_projectno sensitive capability
  • memento_project_state_summaryno sensitive capability
  • memento_record_memory_hitno sensitive capability
  • memento_record_quality_evaluationno sensitive capability
  • memento_rememberno sensitive capability
  • memento_remove_active_coercion_ruleno sensitive capability
  • memento_resume_sessionno sensitive capability
  • memento_searchno sensitive capability
  • memento_search_memoryno sensitive capability
  • memento_search_vnextno sensitive capability
  • memento_sessionno sensitive capability
  • memento_session_statusno sensitive capability
  • memento_set_autonomyno sensitive capability
  • memento_set_goalsno sensitive capability
  • memento_set_project_stateno sensitive capability
  • memento_share_memory_to_workspaceno sensitive capability
  • memento_statusno sensitive capability
  • memento_synthesize_dreamsno sensitive capability
  • memento_system_healthno sensitive capability
  • memento_toggle_accessno sensitive capability
  • memento_toggle_active_coercionno sensitive capability
  • memento_toggle_consolidation_schedulerno sensitive capability
  • memento_toggle_dependency_trackerno sensitive capability
  • memento_toggle_kg_extraction_schedulerno sensitive capability
  • memento_toggle_precognitionno sensitive capability
  • memento_toggle_superpowersno sensitive capability
  • memento_warm_predictive_cacheno sensitive capability

What this scan could not see

Versions 1

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.

VersionScoreFindingsEngineScanned
v1.2.1 latest A 93/100 10 1.13.0 2026-08-25

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.

MCP Trust Score: A · 93/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/memento-mcp/badge.svg)](https://mcptrustchecker.com/registry/memento-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/memento-mcp"><img src="https://mcptrustchecker.com/registry/memento-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/memento-mcp/badge.json via https://img.shields.io/endpoint?url=…

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 memento-mcp --online --registry pypi

Use the free API → How scoring works

Other implementations of Memento 5

Independent packages implementing the same tool, scanned with the same engine. Compare all 6 side by side →

More in Developer Tools