C
Emerging
74/100
5 days ago

remem-mcp

Local memory MCP server that survives context compaction, learns from errors, injects fixes before the next attempt, and syncs to your git repo so your whole team shares it.

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

tinhien11

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

Install from

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 4 credentials: OPENAI_API_KEY, REMEM_GLOBAL_SESSION_KEY, REMEM_LLM_API_KEY, REMEM_SESSION_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configDEVIN_TRANSCRIPTS_DIR
🔐 secretOPENAI_API_KEY
configREMEM_AUDIT_LOG_PATH
configREMEM_CORE_ONLYCore-only mode (disable advanced tools) _(unset, set to 1)_
configREMEM_DB_PATHDB path ~/.local/share/remem-mcp/memory.db
configREMEM_ESCALATION_THRESHOLD
configREMEM_FIX_STALENESS_DAYS
configREMEM_GLOBAL_ERRORSCross-project errors _(unset, set to 1)_
🔐 secretREMEM_GLOBAL_SESSION_KEYCross-project memory _(unset)_
configREMEM_GOAL_ID
configREMEM_HOOK_LOG_PATH
🔐 secretREMEM_LLM_API_KEYLLM API key (pipeline) _(unset)_
configREMEM_LLM_BASE_URL
configREMEM_LLM_MODEL
configREMEM_QUIETSuppress hook feedback _(unset, set to 1)_
configREMEM_RETRO_DAYSRetro window (days) 7
🔐 secretREMEM_SESSION_KEY
configREMEM_VIEWER_PORT
configXDG_CONFIG_HOME
configXDG_DATA_HOME
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

28/28 tools missing one or more hints — recall (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); capture (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); search (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +25 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool test coverage

19/28 tools referenced in tests (68%)

Write tests that reference each tool by name so every tool has at least one test.

Shell command execution

19 child_process/subprocess calls in production code — runs shell commands (src/doctor.ts:70, src/hook-handlers.ts:599, src/hook-handlers.ts:2418)

Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.

Secrets not logged

1 secret value sent to console.log

Redact or omit secret values from log output.

No arbitrary install scripts

Has postinstall/preinstall script — runs arbitrary code on npm install

Remove postinstall/preinstall hooks unless they’re essential.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 6 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/tinhien11-remem-mcp-jhgwg0)](https://m8ven.ai/mcp/tinhien11-remem-mcp-jhgwg0)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 6cccd9ea82491c3bab73ea0328e8a4c3f68f7238
code hash: c8104b15c01b4028830f9061182e95619d10a0c5e857e03520dbd45e353ffb3b
verified: 8/15/2026, 9:41:33 AM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client