stackchan-mcp (migratorywhale/stackchan-mcp) is an MCP server listed on the M8ven Trust Index. It scores 71 out of 100, grade C. It declares 14 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Limited view
71/100

stackchan-mcp

Bridges MCP-compatible AI assistants with the Stack-chan robot, enabling speech, listening, vision, movement, and facial expressions through MCP tool calls.

→ migratorywhale/stackchan-mcp· listed on glama

Limited view. Automated analysis covers part of this stack. Findings reflect what we verified. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

Limited view: static analysis for C is partially covered.

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

migratorywhale

Source: Glama

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

Glamanot scored here

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
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
✅
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 4 credentials: FISH_AUDIO_KEY, STACKCHAN_MCP_AUTH_TOKEN, STACKCHAN_FRONTEND_TOKEN, STACKCHAN_VOICE_UPLOAD_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.
configSTACKCHAN_MCP_HTTP_HOST
configSTACKCHAN_MCP_HTTP_PORT
configSTACKCHAN_AUDIO_DIR
configSTACKCHAN_AUDIO_MODE
configSTACKCHAN_PCM_TRANSPORT
configSTACKCHAN_AUDIO_TRANSPORT
configSTACKCHAN_IPexport ="192.0.2.20" # your Stack-chan's IP
configSTACKCHAN_PORToverrides such as , MCP_PYTHON, STACKCHAN_PUBLIC_MCP_URL,
configMAC_IPexport ="192.0.2.10" # your host machine's IP
configAUDIO_SERVE_PORT
configTTS_ENGINE
configEDGE_TTS_BIN
🔐 secretFISH_AUDIO_KEYexport ="your_key_here" # Fish Audio API key
configFISH_AUDIO_MODEL_ZHFish Audio: set / FISH_AUDIO_MODEL_EN to your
configFISH_AUDIO_MODEL_ENFish Audio: set FISH_AUDIO_MODEL_ZH / to your
🔐 secretSTACKCHAN_MCP_AUTH_TOKENthe bearer check in front of it either way.
configSTACKCHAN_OTEL_LOG
configSTACKCHAN_SERVICE_NAME
configSTACKCHAN_VOICE_INBOX
configSTACKCHAN_VOICE_UPLOAD_HOST0.0.0.0 ./start-voice-upload.sh
configSTACKCHAN_VOICE_UPLOAD_PORT
configSTACKCHAN_VOICE_LANG
configSTACKCHAN_VOICE_UPLOAD_MAX_BYTES
configSTACKCHAN_FRONTEND_WAKE_URL"http://127.0.0.1:3200/wake" \
configSTACKCHAN_FRONTEND_SESSION_ID"<frontend-session-uuid>" \
configSTACKCHAN_FRONTEND_SESSION_TITLE"lab-room" \
🔐 secretSTACKCHAN_FRONTEND_TOKENis not already set, so you do not need to duplicate
configSTACKCHAN_FRONTEND_MODEL
configSTACKCHAN_FRONTEND_TIMEOUT
configSTACKCHAN_FRONTEND_RETRIESis useful when the target frontend session is
configSTACKCHAN_FRONTEND_RETRY_DELAY
configSTACKCHAN_FRONTEND_QUIET_MINUTES
configSTACKCHAN_FRONTEND_PROMPT_PREFIX
configSTACKCHAN_VOICE_WAKE_WORDS小塔,机器人 in the local .env, the loop is:
🔐 secretSTACKCHAN_VOICE_UPLOAD_TOKEN"<random-token>" \
configSTACKCHAN_VOICE_UPLOAD_RATE_PER_MINUTEaccepted only for backward compatibility.
configSTACKCHAN_VOICE_UPLOAD_RATE_WINDOW_SECONDS
configSTACKCHAN_FRONTEND_REGISTRY"/path/to/frontend/relay/data/web-sessions.json" \
configSTACKCHAN_FRONTEND_ENV/path/to/frontend/relay/.env when
// 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

14/14 tools missing one or more hints — stackchan_say (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); stackchan_listen (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); stackchan_move (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +11 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

Only 5/14 tool handlers declare input schemas (36%)

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

Tool handlers catch errors

12/14 tool handlers wrap calls in try/catch (86%)

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

Tests exist

No test files found

Add tests that exercise each declared tool.

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/migratorywhale/stackchan-mcp)](https://m8ven.ai/mcp/migratorywhale/stackchan-mcp)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: d0c52d49dbd1875aee94653581a0bdb4d6072a9d
code hash: 3ac6e31df179f5b4c4e765d9b036643cbc4995a045c425cebdcdbb527f2e0591
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