qwen-code-docs (QwenLM/qwen-code-docs) is an MCP server listed on the M8ven Trust Index. M8ven has not graded it yet. No publisher has claimed this listing.

Not scored

qwen-code-docs

A documentation translation tool specifically designed for Qwen Code

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

QwenLM

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 →

Install from

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
🚨
Secret credentials may flow to a network call
1 flow detected: OPENAI_API_KEY. We can’t prove the destination matches the brand the credential belongs to.
🚨
Known vulnerabilities in dependencies: 2 critical, 8 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
🔐
You'll be asked for 1 credential: OPENAI_API_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies2 critical8 high6 medium10 low

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

criticalnext@14.2.35GHSA-2xp9-vwfh-vxw4

Next.js: Unauthenticated Remote Code Execution in Image Optimization API when AVIF files are used

criticalnext@14.2.35GHSA-p293-qw3h-jr36

Next.js: Unauthenticated Remote Code Execution on windows-hosted servers

highnext@14.2.35GHSA-36qx-fr4f-26g5

Next.js has a Middleware / Proxy bypass in Pages Router applications using i18n

highnext@14.2.35GHSA-89xv-2m56-2m9x

Next.js: Server-Side Request Forgery in Server Actions on custom servers

highnext@14.2.35GHSA-8h8q-6873-q5fj

Next.js Vulnerable to Denial of Service with Server Components

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.
configGITHUB_STEP_SUMMARY
🔐 secretOPENAI_API_KEY
configOPENAI_BASE_URL
configQWEN_API_MAX_RETRIES
configQWEN_CHUNK_CHARS
configQWEN_FILE_CONCURRENCY
configQWEN_MODEL
configQWEN_TRANSLATION_CONCURRENCY
// quality suggestions

Tools detected

No tools extracted — insufficient content to verify at Tier 2

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

Shell command execution

12 calls in production code run through a shell (orchestrator/orchestrator.mjs:157, orchestrator/orchestrator.mjs:232, orchestrator/orchestrator.mjs:1344)

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

Secrets stay with their owner

1 secret sent to a request target we could not resolve (OPENAI_API_KEY → dynamic) — often a configured endpoint, not necessarily third-party

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

Secrets not logged

3 secret values sent to log

Redact or omit secret values from log output.

Production dependencies are patched

2 critical, 8 high severity in production deps — next@14.2.35 (critical), next@14.2.35 (critical)

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

Dependency freshness

1/17 production deps stale: server-only@2022-09-03 (4y)

Domain consistency

npm scope @qwen-code doesn't match GitHub owner qwenlm

Use the same org name across GitHub, npm, and your homepage so users can verify the publisher.

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/qwenlm/qwen-code-docs)](https://m8ven.ai/mcp/qwenlm/qwen-code-docs)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 4f3b56693fd3ab35843975b14ce2f0d55d1e403d
code hash: cc8af69e9ff64b134e2225090e02ef799c7f20594d72958d5d7da3508dafe938
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