Memory (exaudeus) MCP Server
@exaudeus/memory-mcp
npm
v1.9.9
Source verified
Published by etiennebbeaulac — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.
Codebase memory MCP server - persistent, evolving knowledge for AI coding 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 − 6 = 94. 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 |
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 3
high Shell/command execution in server code (dist/config.js)MTC-SRC-002
In the server's implementation (`dist/config.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: { execFileSync } from 'child_process'; import path from 'path'; import os from 'os'; import { DEFAULT_STORAGE_BUDGET_BY
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/config.js
high Shell/command execution in server code (dist/git-service.js)MTC-SRC-002
In the server's implementation (`dist/git-service.js:3`): 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: port { execFile } from 'child_process'; import { promisify } from 'util'; const execFileAsync = promisify(execFile); con
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/git-service.js
high Shell/command execution in server code (dist/store.js)MTC-SRC-002
In the server's implementation (`dist/store.js:7`): 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: port { execFile } from 'child_process'; import { promisify } from 'util'; import { DEFAULT_CONFIDENCE, realClock, parseT
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/store.js
Tools 12
Each tool and what it can reach — statically extracted from the published source.
Available memory lobesno sensitive capabilitybriefno sensitive capabilityconventionno sensitive capabilityconventionsno sensitive capabilityfixno sensitive capabilitygotchano sensitive capabilitygotchasno sensitive capabilitylearnno sensitive capabilitymemory_bootstrapno sensitive capabilitymemory-mcpno sensitive capability
Show 2 more tools ↓
preferno sensitive capabilityrecallno 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.9.9 latest |
A 94/100 | 3 | 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 @exaudeus/memory-mcp --onlineOther implementations of Memory 38
Independent packages implementing the same tool, scanned with the same engine. Compare all 39 side by side →
The official knowledge-graph memory server: persistent entities, relations and observations.
The agentage Memory MCP server: exposes your local vaults as the frozen 6 memory__* tools over stdio. The open, cross-vendor counterpart to @modelcontextprotocol/server-memory.
Semantic memory and knowledge management for Claude Code.
MCP server for enabling memory for Claude through a knowledge graph
MCP server for enabling memory for Claude through a knowledge graph
MCP server for enabling memory for Claude through a knowledge graph
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