Memento Vault (sandsower/memento-vault) is an MCP server listed on the M8ven Trust Index. It scores 71 out of 100, grade C. It declares 20 tools. No publisher has claimed this listing.

C
Limited view
71/100
19 days ago

Memento Vault

Provides persistent knowledge capture and retrieval for coding agents. Enables searching the vault, storing notes, capturing sessions, and reading notes via MCP tools.

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

sandsower

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: MEMENTO_API_KEY, VOYAGE_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.
configMEMENTO_PI_PROCESSOR
configMEMENTO_PI_PROCESS_QUEUE_MODEL
configXDG_CONFIG_HOME
configMEMENTO_HOST
configMEMENTO_PORT
configXDG_DATA_HOME
configPI_CODING_AGENT_SESSION_DIR
configMEMENTO_PI_TRANSCRIPT_ROOTS
configMEMENTO_TRANSPORT
🔐 secretMEMENTO_API_KEY
configLONGMEMEVAL_BACKEND
configMEMENTO_VAULT_PATH
configMEMENTO_SEARCH_BACKEND
configMEMENTO_EVAL_FORCE_LLM_BACKEND
configMEMENTO_EVAL_NOW
configMEMENTO_REGEN_GOLDEN
configMEMENTO_EVAL_VECTOR_ADVISORY
configMEMENTO_MODEL_CACHE_DIR
configXDG_RUNTIME_DIR
configMEMENTO_SWEEPER_ORPHAN_GRACE_SECONDS
configMEMENTO_AGENT
configXDG_CACHE_HOME
🔐 secretVOYAGE_API_KEY
🔐 secretOPENAI_API_KEY
🔐 secretGOOGLE_API_KEY
configMEMENTO_VAULT_URL
configCODEX_HOME
configMEMENTO_PI_STATE_HOME
configXDG_STATE_HOME
configINDEX_PATH
configMEMENTO_DEBUG
configMEMENTO_OPENCODE_SESSION_ID
// 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

20/20 tools missing one or more hints — memento_search (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); memento_related (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); memento_query (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +17 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 inputs are validated

18/20 tool handlers declare input schemas (90%)

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

Tool handlers catch errors

Only 9/20 tool handlers wrap calls in try/catch (45%)

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.

Shell command execution

4 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 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/sandsower-memento-vault-bzwqzk)](https://m8ven.ai/mcp/sandsower-memento-vault-bzwqzk)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 72fcf58c799b8c4d9f722013bd0c067038131dfc
code hash: 3145430f191255acb7e83cbd3ea761a918e255d6339d2cdb57a6410011b09e55
verified: 8/6/2026, 3:23:39 PM
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