Back to MCP Trust Indexm8ven
C
Emerging
74/100
4 days ago

qwen-coder-epic

My custom version of qwen coder

→ FiredMosquito831/qwen-coder-epic· listed on github_code

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

FiredMosquito831

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
🚨
Secret credentials may flow to a network call
9 flows detected: GITHUB_TOKEN. We can’t prove the destination matches the brand the credential belongs to.
🔐
You'll be asked for 1 credential: GITHUB_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.
configCLAUDE_CONFIG_DIR
configCODEX_HOME
configGEMINI_CONFIG_DIR
configOPENCODE_CONFIG
configOPENCODE_CONFIG_DIR
configTERM
configXDG_CONFIG_HOME
configSEARXNG_URL
configSEARXNG_AUTO_START
configQWEN_HOME
configCOMSPEC
configSHELL
configPYTHONPATH
configREPOSITORY_URL
configRESOURCE_NAME
configDESCRIPTION
configAWESOME_CC_PAT_PUBLIC_REPO
🔐 secretGITHUB_TOKEN
configGITHUB_OUTPUT
configISSUE_TITLE
configISSUE_BODY
// 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

44/44 tools missing one or more hints — log_event (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); query_events (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); rotate_logs (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +41 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.

Tool test coverage

33/44 tools referenced in tests (75%)

Write tests that reference each tool by name so every tool has at least one test.

Shell command execution

4 child_process/subprocess calls in production code — runs shell commands (KERNELS/get-shit-done-main/get-shit-done-main/hooks/gsd-check-update.js:25, KERNELS/superpowers-main/superpowers-main/skills/writing-skills/render-graphs.js:25, KERNELS/superpowers-main/superpowers-main/skills/writing-skills/render-graphs.js:72)

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

Secrets not logged

20 secret values 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 Score](https://m8ven.ai/badge/mcp/firedmosquito831-qwen-coder-epic-1s0xv6)](https://m8ven.ai/mcp/firedmosquito831-qwen-coder-epic-1s0xv6)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: ed359664fa99de92f9400414a2cbcf7ce628f9fa
code hash: 40c110fb1a87fba16fb6aaa414ec6ebb285a8bbc537505a5d333d425eabae0c6
verified: 8/19/2026, 4:05:45 AM
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