wmux (openwong2kim/wmux) is an MCP server listed on the M8ven Trust Index. It scores 76 out of 100, grade B. It declares 6 tools. No publisher has claimed this listing.

B
Caution
76/100
2 months ago

wmux

Run Claude Code, Codex & Gemini in parallel on Windows & macOS — git worktree fan-out with atomic hunk adoption, approval gates, reboot-surviving sessions

Caution. Specific findings reduced this grade. They are listed on the page. 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

openwong2kim

Source: github_topic · also listed on Glama, 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
⚠️
Tool descriptions don’t match what handlers do
1 tool describes read intent but its handler mutates — company_a2a_ack (line 148: execFileSync(ps, [)
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: APPLE_APP_SPECIFIC_PASSWORD, WMUX_AUTH_TOKEN, WMUX_MINISERVER_TOKEN, WMUX_WSID_PROBE_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies1 medium4 low

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

mediumvite@5.4.21GHSA-4w7w-66w2-5vf9

Vite Vulnerable to Path Traversal in Optimized Deps `.map` Handling

lowelectron@41.0.3GHSA-8x5q-pvf5-64mp

Electron: Use-after-free in offscreen shared texture release() callback

lowelectron@41.0.3GHSA-f37v-82c4-4x64

Electron: Crash in clipboard.readImage() on malformed clipboard image data

lowelectron@41.0.3GHSA-f3pv-wv63-48x8

Electron: Named window.open targets not scoped to the opener's browsing context

lowpostcss@8.5.8GHSA-qx2v-qp2m-jg93

PostCSS has XSS via Unescaped </style> in its CSS Stringify Output

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.
🔐 secretAPPLE_APP_SPECIFIC_PASSWORD
configAPPLE_ID
configAPPLE_TEAM_ID
configCDPRandomized port — no fixed debug port
configCDP_URL
configCYCLES
configComSpec
configPath
configProgramFiles
configSHELL
configSystemRoot
configTAG
configWMUX_APP_ROOT
🔐 secretWMUX_AUTH_TOKEN
configWMUX_BRIDGE_DEBUG
configWMUX_DATA_SUFFIX
configWMUX_IDLE_GRACE_MS
configWMUX_IDLE_SHUTDOWN_MS
configWMUX_MINISERVER_OWNERS
configWMUX_MINISERVER_PIPE
configWMUX_MINISERVER_RESOLVE_ONCE
🔐 secretWMUX_MINISERVER_TOKEN
configWMUX_MINISERVER_WORKSPACES
configWMUX_SOCKET_PATH
configWMUX_SURFACE_ID
configWMUX_WATCHDOG_TICK_MS
configWMUX_WORKSPACE_ID
configWMUX_WSID_PROBE_DOUBLE
configWMUX_WSID_PROBE_PIPE
🔐 secretWMUX_WSID_PROBE_TOKEN
configWS_NAME
configXDG_CONFIG_HOME
// 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

6/6 tools missing one or more hints — company_a2a_whoami (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); company_a2a_send (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); company_a2a_broadcast (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +3 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.

Descriptions match behaviour

1 tool describes read intent but its handler mutates — company_a2a_ack (line 148: execFileSync(ps, [)

Rename the tool, rewrite the description, or move the side-effect into a separate clearly-named tool.

Tool inputs are validated

4/6 tool handlers declare input schemas (67%)

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

Tool test coverage

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

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

Shell command execution

14 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.

Domain consistency

npm scope @wmux-examples doesn't match GitHub owner openwong2kim

Use the same org name across GitHub, npm, and your homepage so users can verify the publisher.

Tool description accuracy

company_a2a_ack: description implies read-only but handler writes/deletes/executes

Update tool descriptions to accurately reflect all capabilities — especially write, delete, or execute operations.

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 9 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/openwong2kim/wmux?variant=verified)](https://m8ven.ai/mcp/openwong2kim/wmux)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 27a79a3c89b004e6aba9ff1d21fdfabc921ef033
code hash: c9967b231e80b3b739a39e4ce1b77c6a5e0985a31782a8851fb8e88c2c4e1df4
verified: 6/14/2026, 11:01:00 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