gbrain-cn (weiping/gbrain-cn) is an MCP server listed on the M8ven Trust Index. It scores 56 out of 100, grade D. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
D
Caution
56/100

gbrain-cn

GBrain fork with Chinese language support (Zhipu AI embedding, CJK search)

→ weiping/gbrain-cn· listed on github_code

Caution. Specific findings reduced this grade. They are listed on the page. 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

weiping

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

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
⚠️
Known vulnerabilities in dependencies: 3 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
✅
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: GBRAIN_REMOTE_CLIENT_SECRET
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies3 high1 low

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

highjs-yaml@3.14.2GHSA-2883-xcg3-v3hh

js-yaml: maxTotalMergeKeys does not limit CPU use for empty merge sources

highjs-yaml@3.14.2GHSA-52cp-r559-cp3m

js-yaml: YAML merge-key chains can force quadratic CPU consumption

highjs-yaml@3.14.2GHSA-5p4m-2wfm-xmqj

JS-YAML: Quadratic CPU consumption in !!omap resolution (3.x and 4.x) — CVE-2026-59870 fix not backported

lowjs-yaml@3.14.2GHSA-h67p-54hq-rp68

JS-YAML: Quadratic-complexity DoS in merge key handling via repeated aliases

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// 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.
configGBRAIN_AUTOPILOT_MAX_RECONNECT_FAILS
configGBRAIN_BIN_OVERRIDE
configGBRAIN_DOCTOR_FM_TIMEOUT_MS
configGBRAIN_EMBEDDING_DIMENSIONS
configGBRAIN_EMBEDDING_IMAGE_OCR
configGBRAIN_EMBEDDING_IMAGE_OCR_MODEL
configGBRAIN_EMBEDDING_MODEL
configGBRAIN_EMBEDDING_MULTIMODAL
configGBRAIN_HOME
configGBRAIN_HTTP_CORS_ORIGIN
configGBRAIN_MCP_FORCE_SURFACE
configGBRAIN_NO_BRAINSTORM_PREVIEW
configGBRAIN_NO_RETRY_CONNECT
🔐 secretGBRAIN_REMOTE_CLIENT_SECRET
configGBRAIN_SERVE_DEGRADED
configGBRAIN_SKIP_STARTUP_HOOKS
configGBRAIN_SOURCE
configGBRAIN_STDIN_TIMEOUT_MS
configLLAMA_SERVER_BASE_URL
configOPENCLAW_HOME
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployDATABASE_URL
// quality suggestions

Shell command execution

19 calls in production code run through a shell (src/cli.ts:2531, evals/functional-area-resolver/harness-runner.ts:227, src/commands/autopilot.ts:226)

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

No arbitrary install scripts

Has postinstall/preinstall script — runs arbitrary code on npm install

Remove postinstall/preinstall hooks unless they’re essential.

Production dependencies are patched

0 critical, 3 high severity in production deps — js-yaml@3.14.2 (high), js-yaml@3.14.2 (high)

Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.

Dependency freshness

1/29 production deps stale: exifr@2022-05-01 (4.4y)

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 Verified](https://m8ven.ai/badge/mcp/weiping/gbrain-cn?variant=verified)](https://m8ven.ai/mcp/weiping/gbrain-cn)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 0a1a1fb47925c86e66dbaa70f81186e0fd3d7430
code hash: 422e4b9ec5fbe20ebd9e4ec977128f8585b6992ca6d476be85a2c61e74e0dfbc
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