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

Back to MCP Trust IndexM8ven
C
Emerging
74/100
7 days ago

xc-body

→ SiyiLi/xc-body· listed on github_code

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

SiyiLi

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 →

⚡ Connect GitHub for Live Monitored

Install from

GitHub

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

// 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 11 credentials: STACKCHAN_TOKEN, BEARER_TOKEN, VISION_TOKEN, STACKCHAN_AUDIO_HOOK_TOKEN, XC_BODY_PENDING_HTTP_TOKEN, STACKCHAN_PCM_TOKEN, GITHUB_TOKEN, OSS_ACCESS_KEY_SECRET, VERSIONS_TOKEN, OPENAI_API_KEY, STACKCHAN_IRODORI_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.
🔐 secretSTACKCHAN_TOKEN
🔐 secretBEARER_TOKEN
configWS_PORT
configCAPTURE_PORT
configDYLD_LIBRARY_PATH
configMCP_HTTP_ALLOWED_HOSTS
configVISION_HOST
configVISION_URL
🔐 secretVISION_TOKEN
configSTACKCHAN_AUDIO_HOOK_URL
🔐 secretSTACKCHAN_AUDIO_HOOK_TOKEN
configHOST
configMCP_HTTP_HOST
configMCP_HTTP_PORT
🔐 secretXC_BODY_PENDING_HTTP_TOKEN
🔐 secretSTACKCHAN_PCM_TOKEN
configXDG_CONFIG_HOME
configSTACKCHAN_OWNER_ID
🔐 secretGITHUB_TOKEN
configOSS_ACCESS_KEY_ID
🔐 secretOSS_ACCESS_KEY_SECRET
configOSS_ENDPOINT
configOSS_BUCKET_NAME
configVERSIONS_SERVER_URL
🔐 secretVERSIONS_TOKEN
configOSS_BUCKET_URL
configSTACKCHAN_FASTER_WHISPER_MODEL
configSTACKCHAN_FASTER_WHISPER_DEVICE
configSTACKCHAN_FASTER_WHISPER_COMPUTE_TYPE
configSTACKCHAN_OPENAI_WHISPER_MODEL
🔐 secretOPENAI_API_KEY
configSTACKCHAN_EDGE_TTS_DEFAULT_VOICE
configSTACKCHAN_IRODORI_SPEAKER
configSTACKCHAN_IRODORI_STEPS
configSTACKCHAN_IRODORI_URL
🔐 secretSTACKCHAN_IRODORI_KEY
configSTACKCHAN_VOICEVOX_URL
configSTACKCHAN_VOICEVOX_DEFAULT_SPEAKER
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
// 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

57/57 tools missing one or more hints — get_status (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_device_info (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); upgrade_firmware (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +54 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 9/57 tools referenced in tests (16%)

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

Domain consistency

npm scope @xc-body doesn't match GitHub owner siyili

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 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/siyili/xc-body)](https://m8ven.ai/mcp/siyili/xc-body)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: ad9c1226a6fceba79db01f113597f8b3229d61b9
code hash: f9d95cd273cbf6b8360bfa6f4ad074c2d9d691c69e75101b7870c38a8f0b0c67
verified: 9/3/2026, 6:30:18 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