Forgetful Ai MCP Server
forgetful-ai
PyPI
v0.5.1
Published by scottrbk — 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.
MCP Server for AI Agent Memory - persistent, semantically-searchable memory for AI agents
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:
| Points | Adoption-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 13
high Shell/command execution in server code (app/services/backup_service.py)MTC-SRC-002
In the server's implementation (`app/services/backup_service.py:97`): 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: WORD} result = subprocess.run(cmd, env=env, capture_output=True, text=True) if result.returncode != 0:
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 app/services/backup_service.py
medium Tool "unlink_entity_from_memory" can modify the filesystemMTC-CAP-002
Tool "unlink_entity_from_memory" can write, overwrite or delete files (keyword "unlink" in tool name). Verify it is scoped to a safe directory.
Fix: Constrain file operations to an explicit, non-sensitive root; reject path traversal.
Location: tool unlink_entity_from_memory
medium Tool "unlink_entity_from_project" can modify the filesystemMTC-CAP-002
Tool "unlink_entity_from_project" can write, overwrite or delete files (keyword "unlink" in tool name). Verify it is scoped to a safe directory.
Fix: Constrain file operations to an explicit, non-sensitive root; reject path traversal.
Location: tool unlink_entity_from_project
medium Tool "unlink_skill_from_memory" can modify the filesystemMTC-CAP-002
Tool "unlink_skill_from_memory" can write, overwrite or delete files (keyword "unlink" in tool name). Verify it is scoped to a safe directory.
Fix: Constrain file operations to an explicit, non-sensitive root; reject path traversal.
Location: tool unlink_skill_from_memory
medium Tool "unlink_skill_from_file" can modify the filesystemMTC-CAP-002
Tool "unlink_skill_from_file" can write, overwrite or delete files (keyword "unlink" in tool name). Verify it is scoped to a safe directory.
Fix: Constrain file operations to an explicit, non-sensitive root; reject path traversal.
Location: tool unlink_skill_from_file
medium Tool "unlink_skill_from_code_artifact" can modify the filesystemMTC-CAP-002
Tool "unlink_skill_from_code_artifact" can write, overwrite or delete files (keyword "unlink" in tool name). Verify it is scoped to a safe directory.
Fix: Constrain file operations to an explicit, non-sensitive root; reject path traversal.
Location: tool unlink_skill_from_code_artifact
medium Tool "unlink_skill_from_document" can modify the filesystemMTC-CAP-002
Tool "unlink_skill_from_document" can write, overwrite or delete files (keyword "unlink" in tool name). Verify it is scoped to a safe directory.
Fix: Constrain file operations to an explicit, non-sensitive root; reject path traversal.
Location: tool unlink_skill_from_document
low Mutating tool "unlink_entity_from_memory" declares no destructiveHintMTC-CAP-005
Tool "unlink_entity_from_memory" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.
Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.
Location: tool unlink_entity_from_memory
low Mutating tool "unlink_entity_from_project" declares no destructiveHintMTC-CAP-005
Tool "unlink_entity_from_project" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.
Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.
Location: tool unlink_entity_from_project
low Mutating tool "unlink_skill_from_memory" declares no destructiveHintMTC-CAP-005
Tool "unlink_skill_from_memory" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.
Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.
Location: tool unlink_skill_from_memory
low Mutating tool "unlink_skill_from_file" declares no destructiveHintMTC-CAP-005
Tool "unlink_skill_from_file" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.
Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.
Location: tool unlink_skill_from_file
low Mutating tool "unlink_skill_from_code_artifact" declares no destructiveHintMTC-CAP-005
Tool "unlink_skill_from_code_artifact" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.
Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.
Location: tool unlink_skill_from_code_artifact
low Mutating tool "unlink_skill_from_document" declares no destructiveHintMTC-CAP-005
Tool "unlink_skill_from_document" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.
Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.
Location: tool unlink_skill_from_document
Tools 57
Each tool and what it can reach — statically extracted from the published source.
unlink_entity_from_memorywrites filesunlink_entity_from_projectwrites filesunlink_skill_from_code_artifactwrites filesunlink_skill_from_documentwrites filesunlink_skill_from_filewrites filesunlink_skill_from_memorywrites filescreate_code_artifactno sensitive capabilitycreate_documentno sensitive capabilitycreate_entityno sensitive capabilitycreate_entity_relationshipno sensitive capability
Show 47 more tools ↓
create_memoryno sensitive capabilitycreate_projectno sensitive capabilitycreate_skillno sensitive capabilitydelete_code_artifactno sensitive capabilitydelete_documentno sensitive capabilitydelete_entityno sensitive capabilitydelete_entity_relationshipno sensitive capabilitydelete_projectno sensitive capabilitydelete_skillno sensitive capabilityexport_skillno sensitive capabilityget_code_artifactno sensitive capabilityget_current_userno sensitive capabilityget_documentno sensitive capabilityget_entityno sensitive capabilityget_entity_memoriesno sensitive capabilityget_entity_relationshipsno sensitive capabilityget_memoryno sensitive capabilityget_projectno sensitive capabilityget_recent_memoriesno sensitive capabilityget_skillno sensitive capabilityhow_to_use_forgetful_toolno sensitive capabilityimport_skillno sensitive capabilitylink_entity_to_memoryno sensitive capabilitylink_entity_to_projectno sensitive capabilitylink_memoriesno sensitive capabilitylink_skill_to_code_artifactno sensitive capabilitylink_skill_to_documentno sensitive capabilitylink_skill_to_fileno sensitive capabilitylink_skill_to_memoryno sensitive capabilitylist_code_artifactsno sensitive capabilitylist_documentsno sensitive capabilitylist_entitiesno sensitive capabilitylist_projectsno sensitive capabilitylist_skillsno sensitive capabilitymark_memory_obsoleteno sensitive capabilityquery_memoryno sensitive capabilityrebuild_embeddingsno sensitive capabilitysearch_entitiesno sensitive capabilitysearch_skillsno sensitive capabilityupdate_code_artifactno sensitive capabilityupdate_documentno sensitive capabilityupdate_entityno sensitive capabilityupdate_entity_relationshipno sensitive capabilityupdate_memoryno sensitive capabilityupdate_projectno sensitive capabilityupdate_skillno sensitive capabilityupdate_user_notesno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (57 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 2
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.5.1 latest |
A 93/100 | 13 | 1.13.0 | 2026-08-25 |
v0.5.0 |
A 93/100 | 13 | 1.12.1 | 2026-07-27 |
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 forgetful-ai --online --registry pypiMore in AI, Memory & Reasoning
FDA device & vehicle recall risk for AI agents: recall history, MAUDE trend, risk score.
Open-source MCP server exposing Agent402.Tools' catalog — 500+ strong: 400+ self-hostable tools + 100 multi-tool skill packs (security-audit, trend-analysis, structured-scrape, decode-blob, forecasting-bake-off) for AI agents — browser, web search & answe
Zero-dependency MCP server that gives AI agents a self-updating project memory in AGENTS.md. Returns merge instructions instead of mutating state, so every change is a reviewable diff.
MCP Apps UI resources and server helpers for n8n
MCP server providing comprehensive access to BookStack knowledge management system
MCP server for tracking achievements with STAR methodology