Clade (shenxingy/Clade) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 9 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Emerging
74/100

Clade

Turn Claude Code and Codex from chat assistants into autonomous coding systems

→ shenxingy/Clade· listed on github_repo_search

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

⚡ 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

shenxingy

Source: github_repo_search

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
🚨
Secret credentials may flow to a network call
2 flows detected: MINIMAX_CODING_API_KEY, GITHUB_TOKEN. We can’t prove the destination matches the brand the credential belongs to.
🔐
You'll be asked for 7 credentials: MINIMAX_CODING_API_KEY, GOOGLE_AI_API_KEY, CLADE_API_KEY, CLADE_USAGE_HUB_TOKEN, GITHUB_TOKEN, MOZ_API_KEY, BING_WEBMASTER_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.
configCHROME
configPUP
configCLADE_RUNTIMEaccepts claude (the backwards-compatible default), codex, or
configORCHESTRATOR_PROJECT_DIR
configCORS_ORIGINS
🔐 secretMINIMAX_CODING_API_KEY
configMINIMAX_GROUP_ID
configCLADE_MCP_COMPACT
🔐 secretGOOGLE_AI_API_KEY
configCLADE_AGENT_RUNTIME
configCLADE_SURFACE
configCLADE_TASK_SOURCE
configCLADE_TRUSTED_CHECKOUT
configGITHUB_EVENT_NAME
configCLADE_CCUSAGE_CMD
configCLADE_MACHINE_ID
configCLAUDE_CONFIG_DIR
🔐 secretCLADE_API_KEY
configXDG_CACHE_HOME
configCLAUDE_SLT_ASCII
configCOLORTERM
configTERM_PROGRAM
configTERM
configCLADE_GIT_IDENTITY_FILE
configRED_PHASE_REPO
configRED_PHASE_PYTHON
configRED_PHASE_SUBDIR
configCLADE_USAGE_HUB_URL
🔐 secretCLADE_USAGE_HUB_TOKEN
configCLADE_USAGE_INTERVAL
configCLADE_PROVIDER_SMOKE_BASE_URL
🔐 secretGITHUB_TOKEN
configADS_IMAGE_PROVIDER
🔐 secretMOZ_API_KEY
🔐 secretBING_WEBMASTER_API_KEY
// 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

9/9 tools missing one or more hints — clade_list_skills (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); dynamic_tool_212 (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); clade_list_skills (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +6 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

6/9 tools referenced in tests (67%)

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

Secrets not logged

1 secret value sent to logger.info

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