F
Warning
28/100
2 days ago

Yggdrasil

Durable, local-first memory for AI coding agents over MCP — zero-dependency (pure Python + SQLite/FTS5), curated and semantically de-duped. Works with Claude Code, Codex and any MCP host, and you own the data as plain rows.

Warning. Serious findings were identified. Review the full report before connecting. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we 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

VonderVuflya

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
🚨
Secret credentials may flow to a network call
6 flows detected: YGG_ENGINE_TOKEN. We can’t prove the destination matches the brand the credential belongs to.
🔐
You'll be asked for 6 credentials: YGG_MCP_TOKEN, YGG_MEMORY_TOKEN, YGG_ENGINE_TOKEN, YGG_EMBED_API_KEY, OPENROUTER_API_KEY, YGG_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.
configYGG_NPM_SOURCE
configYGG_VAULT_DIR
configYGG_MCP_HTTP_PORT
configYGG_MCP_HTTP_HOST
🔐 secretYGG_MCP_TOKEN
configYGG_HOME
configYGG_MCP_INSECURE
configYGG_MEMORY_HOST
configYGG_MEMORY_PORT
🔐 secretYGG_MEMORY_TOKEN
🔐 secretYGG_ENGINE_TOKEN
configYGG_MEMORY_DB
configYGG_FUSION
configYGG_FUSION_W_LEX
configYGG_FUSION_W_VEC
configYGG_W_USAGE
configYGG_USAGE_SCALE
configYGG_W_PIN
configYGG_VECTOR_WARN_AT
configYGG_MEMORY_VERBOSE
configYGG_TOKEN_FILE
configYGG_EMBED_MODEL
configYGG_EMBED_URL
configYGG_EMBED_BACKEND
🔐 secretYGG_EMBED_API_KEYygg config set embed_api_key sk-or-... # or export
🔐 secretOPENROUTER_API_KEY
configYGG_EMBED_API_KEY_FILE
configYGG_EMBED_TTL
configYGG_EVAL_SMALL
configYGG_EVAL_REPORT
configYGG_PORT
configYGG_NONINTERACTIVE
configLINES
configYGG_LABEL
configYGG_UNIT
configYGG_TASK
configXDG_CONFIG_HOME
configYGG_SEMDEDUP_AT
🔐 secretYGG_TOKEN
configYGG_ENGINE_URL"environment": { "": "http://127.0.0.1:42069" }
configYGG_NAMESPACE
configYGG_USER_ID
configYGG_GOV_GATE_USER_ID
configYGG_GOV_GATE_NAMESPACE
configYGG_NO_TUI
configYGG_APPLY_GATE_USER_ID
configYGG_APPLY_GATE_NAMESPACE
configYGG_DISTILL_IDLE
configNO_COLOR
configYGG_SEED_LABEL
configYGG_NO_COLOR
configYGG_UPDATE_CHECK_TTL
configYGG_BG_MODEL
configYGG_BOOTSTRAP_LIMIT
configYGG_RECALL_LIMIT
configYGG_RECALL_MIN_SCORE
// quality suggestions

Shell command execution

4 child_process/subprocess calls in production code — runs shell commands (clients/npm/bin/ygg.js:27, clients/npm/bin/ygg.js:32, clients/npm/bin/ygg.js:43)

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

Secrets stay with their owner

6 secret/sensitive values flow into network calls (YGG_ENGINE_TOKEN → http://127.0.0.1:, YGG_ENGINE_TOKEN → dynamic)

Audit where credentials are sent. A NOTION_TOKEN should only reach api.notion.com — never a third-party host.

Secrets never reach shell commands

1 secret value passed to shell commands — possible command injection

Never pass secrets through shell commands. Use library APIs that accept credentials as arguments.

Secrets not written to files

1 secret value written to files

Avoid persisting secrets to disk. Keep them in memory or your secret manager.

Secrets not logged

1 secret value sent to console.log

Redact or omit secret values from log output.

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 Verified](https://m8ven.ai/badge/mcp/vondervuflya-yggdrasil-ta4fbb?variant=verified)](https://m8ven.ai/mcp/vondervuflya-yggdrasil-ta4fbb)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: e726fda1b57ad47b1b1dbe4ef1c2ecdec4f8bff2
code hash: dde8e106227dbd37fd676bec117550f24dc61221db641d10f38672b0e55b6552
verified: 8/17/2026, 7:06:00 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