xiaozhi-usb-active-wake-workbuddy (Yirxat233/xiaozhi-usb-active-wake-workbuddy) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 11 tools. No publisher has claimed this listing.

C
Emerging
74/100
2 days ago

xiaozhi-usb-active-wake-workbuddy

USB-initiated official Xiaozhi cloud conversations for ESP32-S3, with WorkBuddy integration.

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

Yirxat233

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 →

Install from

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
1 flow detected: VERSIONS_TOKEN. We can’t prove the destination matches the brand the credential belongs to.
🔐
You'll be asked for 3 credentials: GITHUB_TOKEN, OSS_ACCESS_KEY_SECRET, VERSIONS_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.
configBRIDGE_HOST
configBRIDGE_PORT
configCODEBUDDY_CLI_SCRIPT
configFFMPEG_PATH
configMCP_ENDPOINT
configMOCK_STEP_DELAY_MS
configWORKBUDDY_CONFIG_DIR
configWORKBUDDY_CWD
configWORKBUDDY_DESKTOP_TIMEOUT_MS
configWORKBUDDY_MAX_TURNS
configWORKBUDDY_PERMISSION_MODE
configWORKBUDDY_PROJECT_ROOTSBridge 扫描 的一级目录,并合并 WORKBUDDY_SESSION_ROOT 中 JSONL 记录引用的工作区。
configWORKBUDDY_SESSION_ROOTBridge 扫描 WORKBUDDY_PROJECT_ROOTS 的一级目录,并合并 中 JSONL 记录引用的工作区。
configWORKBUDDY_STATE_FILE当前活动项目和每个项目的最后 Session 串行写入 ,并保留 .bak;重启时主文件损坏会自动回退到备份。
configWORKBUDDY_TOOLS
configWORKBUDDY_TRANSPORT
configXIAOZHI_MCP_ENDPOINT
configXIAOZHI_MCP_RECONNECT_INITIAL_MS
configXIAOZHI_MCP_RECONNECT_MAX_MS
configXIAOZHI_PYTHON
configXIAOZHI_PYTHON_PACKAGES
configXIAOZHI_USB_PORT
🔐 secretGITHUB_TOKEN
configOSS_ACCESS_KEY_ID
🔐 secretOSS_ACCESS_KEY_SECRET
configOSS_ENDPOINT
configOSS_BUCKET_NAME
configVERSIONS_SERVER_URL
🔐 secretVERSIONS_TOKEN
configOSS_BUCKET_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

11/11 tools missing one or more hints — xiaozhi_speak (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); workbuddy_list_projects (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); workbuddy_create_project (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +8 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

4/11 tools referenced in tests (36%)

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

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 3 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/yirxat233/xiaozhi-usb-active-wake-workbuddy)](https://m8ven.ai/mcp/yirxat233/xiaozhi-usb-active-wake-workbuddy)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: b10b145b8e512af6e710d2edaf5220b9223aeaea
code hash: b03a5691db1f1658e13de6917150bc8ce0585ea2f24314bc2a0522b5ae9ab17b
verified: 9/10/2026, 9:06:14 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