openclaw-skills (zhaog100/openclaw-skills) is an MCP server listed on the M8ven Trust Index. It scores 41 out of 100, grade D. It declares 8 tools. No publisher has claimed this listing.

D
Warning
41/100
8 days ago

openclaw-skills

OpenClaw skills collection by miliger

Warning. Serious findings were identified. Review the full report before connecting. 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

zhaog100

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

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
🚨
Secret credentials may flow to a network call
15 flows detected: GITHUB_TOKEN, OPENCLAW_GATEWAY_TOKEN, AI_API_KEY. We can’t prove the destination matches the brand the credential belongs to.
🚨
Reads files from sensitive locations
Touches: ~/.openclaw/secrets/github-bounty-hunter.env, ~/.openclaw/workspace/skills/github-bounty-hunter/.env
🔐
You'll be asked for 14 credentials: OPENROUTER_API_KEY, JWT_TOKEN, BASIC_PASSWORD, AF_JWT_SECRET, GITHUB_TOKEN, OPENCLAW_GATEWAY_TOKEN, AI_API_KEY, SENSEVOICE_API_KEY, OPENAI_API_KEY, ALPHA_VANTAGE_API_KEY, FRED_API_KEY, TWELVE_DATA_API_KEY, TEST_PASSWORD, DB_PASSWORD
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.
🔐 secretOPENROUTER_API_KEY
configBASE_URL
configAUTH_TYPE
🔐 secretJWT_TOKEN
configBASIC_USERNAME
🔐 secretBASIC_PASSWORD
configTIMEOUT_SECONDS
configRETRY_COUNT
🔐 secretAF_JWT_SECRET
configAF_DB_URL
configAF_DEBUG
configAF_WECOM_WEBHOOK
configAF_DINGTALK_WEBHOOK
configAF_FEISHU_WEBHOOK
🔐 secretGITHUB_TOKEN
configPAYMENT_ADDRESS
configGITHUB_USERNAME
configAI_CODE_GEN
configOPENCLAW_GATEWAY_URL
🔐 secretOPENCLAW_GATEWAY_TOKEN
configAI_MODEL
configAI_API_URL
🔐 secretAI_API_KEY
configSUPPORTED_TOKENS
configSUPPORTED_CHAINS
configSUPPORTED_FIAT_METHODS
configSUPPORTED_CURRENCIES
configSUPPORTED_PLATFORMS
configRTC_MIN_AMOUNT
configRTC_NETWORK
configUSDT_WALLET_TRC20
configUSDT_WALLET_ERC20
configETH_WALLET
configBTC_WALLET
configSOL_WALLET
configRTC_WALLET
configPAYPAL_EMAIL
configICE_CONFIG_PATH
configOPENCLAW_WORKSPACE
configSENSEVOICE_API_URL
🔐 secretSENSEVOICE_API_KEY
🔐 secretOPENAI_API_KEY
configHEADLESS
🔐 secretALPHA_VANTAGE_API_KEY
🔐 secretFRED_API_KEY
🔐 secretTWELVE_DATA_API_KEY
configOLLAMA_HOST
🔐 secretTEST_PASSWORD
🔐 secretDB_PASSWORD
// 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

8/8 tools missing one or more hints — check_context (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); switch_session (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); set_threshold (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +5 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

Only 0/8 tools referenced in tests (0%)

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

No access to sensitive paths

Reads sensitive paths: ~/.openclaw/secrets/github-bounty-hunter.env, ~/.openclaw/workspace/skills/github-bounty-hunter/.env

Remove reads of sensitive system paths. If you genuinely need them, document why in the README.

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 Verified](https://m8ven.ai/badge/mcp/zhaog100/openclaw-skills?variant=verified)](https://m8ven.ai/mcp/zhaog100/openclaw-skills)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: cb3100b5da870ce504d882fcb36eee14aac046ac
code hash: c0405ab2f45079e8a136bf2bcfaac2942187657b18e38b17d4830e9b4e852d3a
verified: 9/2/2026, 6:52:04 PM
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