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

C
Emerging
74/100
28 days ago

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

zjw49246

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
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
🔐
You'll be asked for 2 credentials: CCM_INTERNAL_SERVICE_TOKEN, OPENAI_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.
configCCM_TESTING
configCCM_TEST_PROJECT_DIR
🔐 secretCCM_INTERNAL_SERVICE_TOKEN
configCODEX_HOME
configDISPLAY
configCCM_XVFB_DISPLAY99 自动登录专用 X display;同机多套 CCM 必须不同
configCCM_LOGIN_TMPDIR~/.cache/ccm/login-tmp Chrome profile/诊断文件的磁盘目录,避免使用 RAM-backed /tmp
🔐 secretOPENAI_API_KEY=sk-...(仅 Whisper 语音和独立 Browser Review CLI 需要)
configCCM_BROWSER_URL_FILE
configUSE_PTY_MODEtrue 启用 PTY 持久会话模式(false 则用 claude -p 一次性进程)
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployDATABASE_URL
// 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

59/59 tools missing one or more hints — start_review (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); check_review (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); stop_review (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +56 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.

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

Tool test coverage

39/59 tools referenced in tests (66%)

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

Secrets not logged

4 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/zjw49246/cc-manager)](https://m8ven.ai/mcp/zjw49246/cc-manager)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 9b1c835cbf3b306bab5f2f2812033926e4dd79fb
code hash: ce6f003e784c7b6387d4b0430e2f9772d9cc2060f88307d81e058f504f878db9
verified: 8/13/2026, 7:46:03 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