agentic-memory-stack-for-claude-code (dmmdea/agentic-memory-stack-for-claude-code) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 29 tools. No publisher has claimed this listing.

C
Emerging
74/100

agentic-memory-stack-for-claude-code

Persistent, multi-tier, measurably-faithful memory backend for Claude Code on Windows + WSL2 (mem0 + Qdrant + EmbeddingGemma + Codex). Self-contained, operator-agnostic installer skill.

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

dmmdea

Source: github_repo_search

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

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// 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 3 credentials: MEM0_KEY, JOBS_IDEMPOTENCY_KEY, MEM0_API_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.
configMEM0_DEFAULT_USER_ID
configMEM0_STACK_VERSION
configMEM0_MAX_MEMORY_CHARS
configMEM0_ZFS_DATASET
configMEM0_SEARCH_OVERFETCH_BUFFER
configMEM0_OPERATIONAL_HALF_LIFE_DAYS
configMEM0_WEIBULL_KAPPA
configMEM0_DURABLE_FRESHNESS_HALF_LIFE_DAYS
configMEM0_LOG_FULL_QUERY
configMEM0_LOG_HASH_FILTERS
configMEM0_URL
configMEM0_RELEVANCE_FLOOR_OPERATIONAL
configMEM0_BRAND_COHERENCE_THRESHOLD
configMEM0_API_KEY_FILE
configXDG_RUNTIME_DIR
configCREDENTIALS_DIRECTORY
configMEM0_CODEX_SHIM_URL
configMEM0_CODEX_TRANSPORT
configMEM0_HOST_KIND
🔐 secretMEM0_KEY
configFASTEMBED_CACHE_PATH
configQDRANT_URL
configMEM0_COLLECTION
configMEM0_HISTORY_DB
configMEM0_BACKUP_DIR
configMEM0_AMS01_REPORT
configMEM0_AMS01_RECEIPTS
configMEM0_AMS01_TMP_COLLECTION
configCODEX_HOME
configMEM0_EVAL_ROOT
configMEM0_BM25_REPORT
configMEM0_BM25_RECEIPTS
configMEM0_QDRANT_COLLECTION
🔐 secretJOBS_IDEMPOTENCY_KEY
configMEM0_EPISODES_COLLECTION
configMEM0_EPISODIC_DB
configMEM0_EMBED_URL
configMEM0_EMBED_MODEL
configMEM0_CP437_REPORT
configMEM0_CP437_RECEIPTS
configMEM0_PROMOTION_GATE_MODE
🔐 secretMEM0_API_KEY
configMEM0_QDRANT_URL
configMEM0_SIDECAR_DIR
configMEM0_WSL_DISTRO
configMEM0_WSL_USER
configMEM0_SHARED_DRIVE_DIR
configMEM0_FOREIGN_HOSTS
configMEM0_LOCAL_HOST
configMEM0_SHARED_DRIVE_LETTERS
configMEM0_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

29/29 tools missing one or more hints — memory_add (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); memory_search (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); memory_recall (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +26 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

12/29 tools referenced in tests (41%)

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

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 3 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/dmmdea/agentic-memory-stack-for-claude-code)](https://m8ven.ai/mcp/dmmdea/agentic-memory-stack-for-claude-code)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 8d8b5944d599b830ccdf4164c71f56a8fe8b8807
code hash: 06eb37158a93ba1ef42b647f2a10e183e5ac8dc31e6501ef248a5bab99417330
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