F
Warning
0/100
11 days ago

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

lyeeen

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
🚨
Hardcoded credentials detected
21 live-looking API keys in source: 4 GitHub PAT (classic), 7 OpenAI API key, 5 Slack token
🚨
Known vulnerabilities in dependencies: 1 critical, 2 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
🔐
You'll be asked for 6 credentials: CHUTES_CLIENT_SECRET, GEMINI_API_KEY, GOOGLE_API_KEY, OLLAMA_API_KEY, OPENCLAW_GATEWAY_PASSWORD, OPENCLAW_GATEWAY_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies1 critical2 high7 low

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

criticaltar@7.5.16GHSA-23hp-3jrh-7fpw

node-tar: Decompression/parse DoS via unlimited input

hightar@7.5.16GHSA-8x88-c5mf-7j5w

node-tar: Negative tar entry size causes infinite loop in archive replace

highundici@8.5.0GHSA-4cwx-7wf7-3272

undici vulnerable to cross-user information disclosure and parse-time crash via degenerate private cache directives

lowtar@7.5.16GHSA-gvwx-54wh-qm9j

node-tar: Uncaught Exception DoS via NUL byte in PAX path/linkpath records

lowtar@7.5.16GHSA-r292-9mhp-454m

node-tar: Uncontrolled recursion in mapHas/filesFilter allows uncatchable stack-overflow DoS via crafted long-path tar with member selection

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.
configCHUTES_CLIENT_ID
🔐 secretCHUTES_CLIENT_SECRET
configCHUTES_OAUTH_REDIRECT_URI
configCHUTES_OAUTH_SCOPES
🔐 secretGEMINI_API_KEY
🔐 secretGOOGLE_API_KEY
🔐 secretOLLAMA_API_KEY
configOPENCLAW_CLI
🔐 secretOPENCLAW_GATEWAY_PASSWORD
configOPENCLAW_GATEWAY_STARTUP_TRACE
🔐 secretOPENCLAW_GATEWAY_TOKEN
configOPENCLAW_SKIP_CANVAS_HOST
configSLACK_BOT_USER_ID
configSLACK_FORWARDER_URL
configTHREAD_OWNERSHIP_CHANNELS
configVITEST
// quality suggestions

Dependencies

85 dependencies, 1 flagged: playwright-core

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

5/5 tools missing one or more hints — codex_endpoint_probe (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); codex_sessions_list (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); codex_session_read (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +2 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 inputs are validated

4/5 tool handlers declare input schemas (80%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tool handlers catch errors

3/5 tool handlers wrap calls in try/catch (60%)

Wrap each tool handler body in try/catch and return a structured error response.

No hardcoded API keys

21 live-looking API keys in source: 4 GitHub PAT (classic), 7 OpenAI API key, 5 Slack token

Move secrets to environment variables (process.env.X) or your secret manager.

Tool test coverage

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

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

Shell command execution

19 child_process calls — runs shell commands

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

No arbitrary install scripts

Has postinstall/preinstall script — runs arbitrary code on npm install

Remove postinstall/preinstall hooks unless they’re essential.

Production dependencies are patched

1 critical, 2 high severity in production deps — tar@7.5.16 (critical), tar@7.5.16 (high)

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

Dependency freshness

4/54 production deps abandoned (no release in 2+ years): proper-lockfile@2022-06-24 (4.1y), json5@2023-03-04 (3.4y), web-push@2024-01-16 (2.6y)

Domain consistency

npm scope @openclaw doesn't match GitHub owner lyeeen

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 10 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/lyeeen-my-openclaw-1tv44k?variant=verified)](https://m8ven.ai/mcp/lyeeen-my-openclaw-1tv44k)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: e7db35f1e4d8a170bbb6834f95bd06cf14801b15
code hash: 24f279444e3df0cfbf279a5a49b2c8c427a473efa194101c9f2d929bc7505412
verified: 8/8/2026, 8:12:39 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