Ombre-Brain (P0luz/Ombre-Brain) is an MCP server listed on the M8ven Trust Index. It scores 98 out of 100, grade A. It declares 16 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
A
Trusted
98/100
8 days ago

Ombre-Brain

→ P0luz/Ombre-Brain· listed on github_code

Trusted. Deep verification, no outstanding findings, and an established reputation. 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

P0luz

Source: github_code

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

GitHub

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 10 credentials: OMBRE_GITHUB_TOKEN, OMBRE_EMBED_API_KEY, OMBRE_API_KEY, OMBRE_COMPRESS_API_KEY, PASSWORD, OMBRE_DASHBOARD_PASSWORD, OMBRE_SETUP_TOKEN, OMBRE_MCP_TOKEN, OMBRE_HOOK_TOKEN, GEMINI_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.
configOMBRE_PORT裸机（纯 Python）：直接监听 ，默认 18001。这个「默认端口」只对裸机有意义。
configOMBRE_BIND_HOST默认 /mcp 强制 OAuth 2.1，Operit 这类客户端不走该流程，会在 401 处卡成「半连接」（正是黄灯）。OB 与 Operit 在同一手机时，同时设 =127.0.0.1 和 OMBRE_MCP_REQUIRE_AUTH=false 后重启；需要让局域网其他设备连接时，保持鉴权并使用“静态 Token”模式。
configOMBRE_HOOK_URL
configOMBRE_HOOK_SKIP
🔐 secretOMBRE_GITHUB_TOKEN
configOMBRE_BUCKETS_DIR每人各设一个，必须互不相同
configOMBRE_EMBED_FORMAT
🔐 secretOMBRE_EMBED_API_KEYecho "=your-embed-key" >> .env
configOMBRE_OLLAMA_URL
configOMBRE_CONFIG_PATH
configRENDER
configOMBRE_VAULT_DIR每人各设一个，必须互不相同
🔐 secretOMBRE_API_KEY永久兼容旧名： → OMBRE_COMPRESS_API_KEY，OMBRE_BASE_URL → OMBRE_COMPRESS_BASE_URL，PASSWORD → OMBRE_DASHBOARD_PASSWORD，OMBRE_BUCKETS_DIR → OMBRE_VAULT_DIR。
configOMBRE_BASE_URL永久兼容旧名：OMBRE_API_KEY → OMBRE_COMPRESS_API_KEY， → OMBRE_COMPRESS_BASE_URL，PASSWORD → OMBRE_DASHBOARD_PASSWORD，OMBRE_BUCKETS_DIR → OMBRE_VAULT_DIR。
🔐 secretOMBRE_COMPRESS_API_KEYecho "=your-key-here" > .env
configOMBRE_COMPRESS_BASE_URL2. 可选 （例如 https://generativelanguage.googleapis.com/v1beta/openai/）和 OMBRE_EMBED_API_KEY
🔐 secretPASSWORD永久兼容旧名：OMBRE_API_KEY → OMBRE_COMPRESS_API_KEY，OMBRE_BASE_URL → OMBRE_COMPRESS_BASE_URL， → OMBRE_DASHBOARD_PASSWORD，OMBRE_BUCKETS_DIR → OMBRE_VAULT_DIR。
🔐 secretOMBRE_DASHBOARD_PASSWORD永久兼容旧名：OMBRE_API_KEY → OMBRE_COMPRESS_API_KEY，OMBRE_BASE_URL → OMBRE_COMPRESS_BASE_URL，PASSWORD → ，OMBRE_BUCKETS_DIR → OMBRE_VAULT_DIR。
configOMBRE_MCP_REQUIRE_AUTH默认 /mcp 强制 OAuth 2.1，Operit 这类客户端不走该流程，会在 401 处卡成「半连接」（正是黄灯）。OB 与 Operit 在同一手机时，同时设 OMBRE_BIND_HOST=127.0.0.1 和 =false 后重启；需要让局域网其他设备连接时，保持鉴权并使用“静态 Token”模式。
configOMBRE_MCP_AUTH_MODE
configOMBRE_MEDIA_DIR
configOMBRE_MEDIA_MAX_BYTES
configXXX
configOMBRE_LOG_DIR
configOMBRE_LOG_FILE
configAI_NAME旧版历史 Letter 默认继续公开且不可补锁。Dashboard 可按单封信执行一次“转换为新版 Letter”：正文与原始元数据不变，只从现有 补写实际关系名，并把锁控制权固定交给 AI；转换后由 AI 通过 letter_lock_update 管理锁，human 不获得锁权限。该转换不批量执行，也不根据旧 author 推断身份。
configOMBRE_OWNER_NAME每人设自己的
configOMBRE_OWNER_COUNT所有人设成相同的值（= 人数）
configOMBRE_HOST_VAULT_DIRecho "=D:/Ombre-Brain/buckets-data" >> .env
configOMBRE_DASHBOARD_SESSION_DAYS
🔐 secretOMBRE_SETUP_TOKEN
🔐 secretOMBRE_MCP_TOKEN
configOMBRE_TRANSPORT默认是 stdio——stdio 根本不开 HTTP 服务，本地桥自然连不上。config.yaml 里写 transport: streamable-http，或设环境变量 =streamable-http，然后重启。
configOMBRE_HOOK_ALLOW_PUBLIC
🔐 secretOMBRE_HOOK_TOKEN
configOMBRE_ALLOW_CUSTOM_UPDATE_REPO
configOMBRE_UPDATE_ALLOW_PIP
configOMBRE_IMAGE_ROOT
configOMBRE_CONTAINER_NAME
🔐 secretGEMINI_API_KEY
configOMBRE_ALLOW_UNTRUSTED_MIRROR
// 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

18/18 tools missing one or more hints — breath (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); breath_search (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); breath_advanced (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +15 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.

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 2 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/p0luz/ombre-brain)](https://m8ven.ai/mcp/p0luz/ombre-brain)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 46b2339a73ee3f78d764c4066cd6d0071e609d6c
code hash: fc9ae7dab96c9df820f732996bcb459d587833ec3b4331dd78152a1c2c85172c
verified: 9/2/2026, 5:46:41 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