C
Limited view
74/100
12 days ago

YourMemory

Agentic AI memory with Ebbinghaus forgetting curve decay. +16pp better recall than Mem0 on LoCoMo.

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

sachitrafa

Source: github_topic · also listed on 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 5 credentials: SUPERMEMORY_API_KEY, ZEP_API_KEY, MEM0_API_KEY, NEO4J_PASSWORD, ANTHROPIC_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.
configYOURMEMORY_RATE_LIMIT
configYOURMEMORY_RATE_WINDOW
configYOURMEMORY_RATE_LIMIT_LOOPBACK
configYOURMEMORY_OLLAMA_URL
configYOURMEMORY_OLLAMA_MODEL
configYOURMEMORY_USER
configYOURMEMORY_EXTRACT_BACKEND
configYOURMEMORY_OLLAMA_KEEPALIVE
configYOURMEMORY_COMPACTION
configYOURMEMORY_HOST
configYOURMEMORY_DASHBOARD_PORT
configYOURMEMORY_TELEMETRY
configYOURMEMORY_REPLACE_NATIVE_MEMORY
configYOURMEMORY_PATH
configYOURMEMORY_SESSION_TTL
configYOURMEMORY_URL
configYOURMEMORY_BUFFER
configYOURMEMORY_TOPK
configYOURMEMORY_MODEL
configYM_BASE_URL
🔐 secretSUPERMEMORY_API_KEY
🔐 secretZEP_API_KEY
🔐 secretMEM0_API_KEY
configYOURMEMORY_DB
configGRAPH_BACKEND
configNEO4J_URI
configNEO4J_USER
🔐 secretNEO4J_PASSWORD
configYOURMEMORY_SESSION_CONTEXT_N
configYOURMEMORY_AUDIT
configYOURMEMORY_AUDIT_RETENTION_DAYS
configYOURMEMORY_AUTH
configYOURMEMORY_COMPACT_MIN
configYOURMEMORY_COMPACT_SIM
configYOURMEMORY_COMPACT_MAX
configYOURMEMORY_EMBED_BACKEND
configYOURMEMORY_EMBED_MODEL
🔐 secretANTHROPIC_API_KEY
configYOURMEMORY_EXTRACT_MODEL
configYOURMEMORY_RELEVANCE_JUDGE
configYOURMEMORY_JUDGE_MODEL
configYOURMEMORY_JUDGE_TIMEOUT
configYOURMEMORY_RECALL_COOLDOWN
configYOURMEMORY_SESSION_IDLE
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployDATABASE_URL
deployPORT
// 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

6/6 tools missing one or more hints — call_tool (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); recall_memory (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); memory_search (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +3 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.

Tests exist

No test files found

Add tests that exercise each declared tool.

No eval / new Function

4 eval() or new Function() calls — dynamic code execution

Replace eval / Function with explicit parsing or safer alternatives.

Shell command execution

8 child_process calls — runs shell commands

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 5 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/sachitrafa-yourmemory-1wptpb)](https://m8ven.ai/mcp/sachitrafa-yourmemory-1wptpb)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 0bda3e0331e67b357832735f6beec3d3f7fb022e
code hash: 64867c46ae5296c96c692110a89b5b67fc9b90b07ecb5781f14983b3cbf3a0ca
verified: 8/7/2026, 2:24:25 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