Back to MCP Trust Indexm8ven
C
Limited view
74/100
8 days ago

memtrust

MCP server exposing a "run" tool that benchmarks agent-memory backends and returns a reproducible JSON report.

→ RudrenduPaul/memtrust· listed on glama

Limited view. Automated analysis covers part of this stack. Findings reflect what we verified. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

Limited view: static analysis for Python is partially covered.

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

RudrenduPaul

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

Glama

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 8 credentials: MEM0_SELFHOSTED_API_KEY, OPENAI_API_KEY, AWS_SECRET_ACCESS_KEY, GOOGLE_API_KEY, MEM0_DIRECT_ELASTICSEARCH_API_KEY, GRAPHITI_NEO4J_PASSWORD, GRAPHITI_GEMINI_API_KEY, MEMTRUST_JUDGE_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.
🔐 secretMEM0_SELFHOSTED_API_KEY
configMEM0_DIRECT_VECTOR_STORE_PROVIDER$ export =qdrant
configMEM0_DIRECT_VECTOR_STORE_URL$ export =http://localhost:6333
configMEM0_DIRECT_EMBEDDING_DIMS
🔐 secretOPENAI_API_KEYwith nothing but set fails every single LLM-based extraction call, out of the
configAWS_ACCESS_KEY_ID
🔐 secretAWS_SECRET_ACCESS_KEY
configAWS_REGION
🔐 secretGOOGLE_API_KEY
🔐 secretMEM0_DIRECT_ELASTICSEARCH_API_KEY
configOPENVIKING_BASE_URL
configGRAPHITI_FALKORDB_URL
configGRAPHITI_NEO4J_USER
🔐 secretGRAPHITI_NEO4J_PASSWORD
configGRAPHITI_EMBEDDER_PROVIDER
🔐 secretGRAPHITI_GEMINI_API_KEY
🔐 secretMEMTRUST_JUDGE_API_KEYexport =... # needed for LongMemEval/LoCoMo grading; contradiction-detection doesn't need it
configMEMTRUST_JUDGE_MODEL
configMEMTRUST_JUDGE_BASE_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

1/1 tools missing one or more hints — run (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint). 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.

Shell command execution

7 child_process/subprocess calls in production code — runs shell commands (npm/memtrust-cli/bin/memtrust.js:50, src/memtrust/cli.py:128, src/memtrust/adapters/openviking_adapter.py:33)

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

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/rudrendupaul-memtrust-114j86)](https://m8ven.ai/mcp/rudrendupaul-memtrust-114j86)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 6946de0c75587ed8bb15f0cfa02860693485cffa
code hash: b4d4388b83dd26a20e3e0fe209fcf9e60db692721334266677d0e6c5bc4b45c8
verified: 8/11/2026, 7:41:58 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