Ai Memory (npm) MCP Server
ai-memory-mcp
npm
v1.0.0
Published by an unidentified publisher — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.
Model Context Protocol (MCP) server that gives AI assistants a persistent, file-based long-term memory with 17 tools: full CRUD, search (fuzzy/tag/date filters), context-aware capture (capture_context/suggest_memory), maintenance (stats/auto_index/check_d
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 − 8 = 92. 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 |
| −2 | publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read |
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 1
high Shell/command execution in server code (index.mjs)MTC-SRC-002
In the server's implementation (`index.mjs:16`): 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: eSync, execSync } from "child_process"; import { dirname, extname, join, relative, resolve, sep } from "path"; // =====
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 index.mjs
Tools 17
Each tool and what it can reach — statically extracted from the published source.
auto_indexno sensitive capabilitycapture_contextno sensitive capabilitycheck_duplicatesno sensitive capabilitycheck_orphansno sensitive capabilitydelete_memoryno sensitive capabilityfind_relatedno sensitive capabilitygit_diffno sensitive capabilitygit_initno sensitive capabilitygit_logno sensitive capabilitylist_memoryno sensitive capability
Show 7 more tools ↓
move_memoryno sensitive capabilityread_memoryno sensitive capabilitysearch_memoryno sensitive capabilitystatsno sensitive capabilitysuggest_memoryno sensitive capabilityupdate_memoryno sensitive capabilitywrite_memoryno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (17 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 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.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v1.0.0 latest |
A 92/100 | 1 | 1.13.0 | 2026-09-07 |
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 ai-memory-mcp --onlineOther implementations of Ai Memory 3
Independent packages implementing the same tool, scanned with the same engine. Compare all 4 side by side →
Python SDK for the ai-memory HTTP API (persistent memory for AI agents).
A production-ready Model Context Protocol (MCP) server for semantic memory management
MCP server component for Schift AI Memory.
More 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