JinNing6/CyberHuaTuo-Plugin (JinNing6/CyberHuaTuo-Plugin) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 64 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Emerging
74/100
10 days ago

JinNing6/CyberHuaTuo-Plugin

A medical MCP server for agents that diagnoses tracebacks, provides exact fixes, and converts verified solutions into reusable prescriptions, plus a guard for destructive shell commands.

→ JinNing6/CyberHuaTuo-Plugin· listed on glama

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

JinNing6

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 →

⚡ Connect GitHub for Live Monitored

Install from

Glamanot scored here

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
3 flows detected: GITHUB_TOKEN. We can’t prove the destination matches the brand the credential belongs to.
🔐
You'll be asked for 12 credentials: GITHUB_TOKEN, CONTEXT7_API_KEY, OPENAI_API_KEY, ANTHROPIC_API_KEY, DEEPSEEK_API_KEY, KIMI_API_KEY, DOUBAO_API_KEY, MINIMAX_API_KEY, GROQ_API_KEY, GEMINI_API_KEY, COHERE_API_KEY, GH_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.
configGITHUB_USERNAME
configCYBERHUATUO_EVIDENCE_LEDGER
configCYBERHUATUO_ACTIVATION_LEDGER
configCYBERHUATUO_WORKSPACE_ROOT
🔐 secretGITHUB_TOKEN🌐 上传药方到 GitHub (需 GITHUB_TOKEN)
configCHROMA_DB_PATH
configDIAGNOSIS_MODEL
configEMBEDDING_MODEL
configOLLAMA_BASE_URL
configHOST
configCONTEXT7_ENABLED
🔐 secretCONTEXT7_API_KEY
configCONTEXT7_BASE_URL
configMINE_DEFAULT_LIMIT
configMINE_MIN_REACTIONS
configMINE_MIN_COMMENTS
configGITHUB_SYNC_ENABLED
configGITHUB_SYNC_OWNER
configGITHUB_SYNC_REPO
configGITHUB_SYNC_BRANCH
configEPHEMERAL_SEARCH_ENABLED
configCASE_SYNC_ENABLED
configCASE_SYNC_INTERVAL_MINUTES
configNOURISHING_ENABLED
configEPIDEMIC_ENABLED
🔐 secretOPENAI_API_KEY
🔐 secretANTHROPIC_API_KEY
🔐 secretDEEPSEEK_API_KEY
🔐 secretKIMI_API_KEY
🔐 secretDOUBAO_API_KEY
🔐 secretMINIMAX_API_KEY
🔐 secretGROQ_API_KEY
🔐 secretGEMINI_API_KEY
🔐 secretCOHERE_API_KEY
configBOT_MIN_SCORE
configBOT_MAX_RESULTS
configGITHUB_REPOSITORY
configCOMSPEC
configSHELL
configCYBERHUATUO_MARKETPLACE_SUBMISSION_LEDGER
configCYBERHUATUO_TRACTION_SNAPSHOT_LEDGER
🔐 secretGH_TOKEN
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
// 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

64/64 tools missing one or more hints — verified_cure (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); cure_feedback (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); diagnose (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +61 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/jinning6/cyberhuatuo-plugin)](https://m8ven.ai/mcp/jinning6/cyberhuatuo-plugin)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 8b1806cbf36a30cb6558580240204c7f39b23de4
code hash: 8037dcf28f8e003e6ca7f64ea8f4fdd71f5f4c25c6d8a4e85999587fe1b22cea
verified: 9/3/2026, 11:02:04 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