Enhanced Memory MCP Server (marc-shade/enhanced-memory-mcp) is an MCP server listed on the M8ven Trust Index. It scores 54 out of 100, grade D. It declares 279 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
D
Caution
54/100

Enhanced Memory MCP Server

A high-performance memory management system for AI agents with 200+ tools including 4-tier memory architecture, advanced RAG pipeline, and Git-like versioning.

→ marc-shade/enhanced-memory-mcp· listed on glama

Caution. Specific findings reduced this grade. They are listed on the page. 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

marc-shade

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 →

⚡ Connect GitHub for Live Monitored

Install from

Glamanot scored here

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 4 credentials: OLLAMA_API_KEY, ANTHROPIC_API_KEY, OPENAI_API_KEY, GOOGLE_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.
configAGENTIC_SYSTEM_PATH~/agentic-system Root path for agentic system
configCAPABILITY_NODE_MAP_JSON
🔐 secretOLLAMA_API_KEY
configHOSTNAME_NODE_MAP_JSON
configCLUSTER_NODE_IDS
🔐 secretANTHROPIC_API_KEYFor contextual prefix generation
🔐 secretOPENAI_API_KEYFor query expansion (optional)
configOLLAMA_HOSTlocalhost:11434 Ollama server for LLM operations
configQDRANT_HOSTlocalhost Qdrant vector database host
configQDRANT_PORT6333 Qdrant vector database port
🔐 secretGOOGLE_API_KEY
configSTORAGE_BASE
configSAFLA_REMOTE_URL
// 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

279/279 tools missing one or more hints — compute_activation_field (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_activation_state (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_routing_bias (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +276 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.

Destructive tools are labelled

1 tool perform destructive updates without destructiveHint — art_reset deletes at line 491 (state_file.unlink())

Add destructiveHint:true to any tool whose handler calls .delete(), .upsert(), .update(), unlink, rm, DELETE, DROP, REPLACE INTO, or any operation that overwrites existing data.

Tool inputs are validated

215/278 tool handlers declare input schemas (77%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tool handlers catch errors

Only 99/278 tool handlers wrap calls in try/catch (36%)

Wrap each tool handler body in try/catch and return a structured error response.

Tests exist

No test files found

Add tests that exercise each declared tool.

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 Verified](https://m8ven.ai/badge/mcp/marc-shade/enhanced-memory-mcp?variant=verified)](https://m8ven.ai/mcp/marc-shade/enhanced-memory-mcp)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 66c87bc899f85d64d88290c088df1e55ef824ba6
code hash: cde756284e10ba92f44df7b4931fa2d23fc9ab35bbaa3d04c4d610b212914b51
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