metamind-vault-rag (Nikitzu/metamind-vault-rag) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 3 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Emerging
74/100
11 days ago

metamind-vault-rag

MCP server for hybrid retrieval over markdown vaults, combining sqlite-vec embeddings and FTS5 keywords with reciprocal rank fusion, plus optional cross-encoder reranking.

→ Nikitzu/metamind-vault-rag· listed on glama

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

Nikitzu

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 1 credential: VAULT_RECALL_REQUIRE_TOKEN
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.
configVAULT_HTTP_PORTPort for the loopback search API
configVAULT_RECALL_TOKEN_PATH
🔐 secretVAULT_RECALL_REQUIRE_TOKEN
configVAULT_CONFIDENCE_LOW_PCT
configVAULT_CONFIDENCE_HIGH_PCT
configVAULT_CONFIDENCE
configVAULT_COLLECTIONCollection name, which scopes the index files
configVAULT_PATHDirectory to index
configVAULT_MAX_CHUNK_CHARS
configVAULT_CHUNK_TARGET_CHARS
configVAULT_CHUNK_OVERLAP_CHARS
configVAULT_EMBED_CONTEXT
configVAULT_STALE_VAULT_DAYS
configVAULT_STATE_DIRWhere indexes, caches and logs are written. Defaults to ~/.vault-rag
configVAULT_RECALL_LOG_PATH
configVAULT_RERANKER_MODEL
configVAULT_RERANKER_ONNX_FILE
configVAULT_RERANK_OVERFETCH
configVAULT_RERANK_MAX_LEN
configVAULT_RERANK_MIN_CANDIDATES
configVAULT_RERANK_ALPHA
configVAULT_RERANK_THREADS
configVAULT_RRF_KEYWORD_WEIGHT
configVAULT_RRF_SEMANTIC_WEIGHT
configVAULT_RRF_KEYWORD_WEIGHT_EXACT
configVAULT_RRF_ADAPTIVE
configVAULT_TEMPORAL_OVERFETCH
configVAULT_MAX_CHUNKS_PER_FILE
configVAULT_CHUNK_IDENTITY
configVAULT_RRF_OVERFETCH
configVAULT_SQLITE_BUSY_TIMEOUT_S
configVAULT_NO_FTS_BACKFILL
configVAULT_BACKEND
configVAULT_EMBED_MODEL
configVAULT_EMBED_DIM
configFASTEMBED_CACHE_PATH
// 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

3/3 tools missing one or more hints — search_vault (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); related_notes (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); expand_search (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.

Tool test coverage

1/3 tools referenced in tests (33%)

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/nikitzu/metamind-vault-rag)](https://m8ven.ai/mcp/nikitzu/metamind-vault-rag)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 85f9aadf1b8b82931f205242b4e5da67c514b002
code hash: a1eb4b79dbe3ad14bb6ebcef8a452affa01f589408b3af257e96c48962de0ca4
verified: 9/1/2026, 5:50:38 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