Memory Bank (JackOman69) MCP Server
mcp-memory-bank
npm
v1.0.0
Published by jackoman69 — 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.
Graph-based knowledge management system providing a memory bank for Cursor IDE.
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 − 1 = 99. 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 |
|---|---|
| −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 1
medium Dynamic module load from a non-literal (dist/memory-bank.js)MTC-SRC-005
In the server's implementation (`dist/memory-bank.js:510`): 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: ' }); graph.import(data); return graph; } catch (error) { console.er
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/memory-bank.js
Tools 12
Each tool and what it can reach — statically extracted from the published source.
create_projectno sensitive capabilityget_file_contentno sensitive capabilityinit_memory_bankno sensitive capabilitylist_project_filesno sensitive capabilitylist_projectsno sensitive capabilitymcp_memory_bank_batch_addno sensitive capabilitymcp_memory_bank_batch_deleteno sensitive capabilitymcp_memory_bank_batch_updateno sensitive capabilitymcp_memory_bank_open_nodesno sensitive capabilitymcp_memory_bank_query_graphno sensitive capability
Show 2 more tools ↓
mcp_memory_bank_search_graphno sensitive capabilityupdate_file_contentno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (12 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 99/100 | 1 | 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.
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-bank --onlineOther implementations of Memory Bank 9
Independent packages implementing the same tool, scanned with the same engine. Compare all 10 side by side →
MCP server for remote management of project memory banks
Memory Bank MCP server for AI assistants that automatically creates and updates memory banks
MCP server for managing project documentation and context across sessions
A guided Memory Bank MCP plugin for AI-assisted development with persistent project context
Memory Bank MCP Server for RooCode, runnable via npx.
MCP server for semantic code indexing with Memory Bank - AI-powered codebase understanding
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