wezterm-agent-mcp
npm
v0.1.9
Published by multiagentcognition — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.
Wezterm MCP Server — programmable terminal control plane for multi-agent AI workflows
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 10.6 = 89. What the published surface and source actually contain:
| Points | What was found | Category |
|---|---|---|
| −9.5 | Untrusted input concatenated into a command sink ×2 MTC-SRC-009 | injection |
| −1.2 | Package runs install-time scripts MTC-SUP-010 | supply-chain |
2. Client adoption risk — 89 − 7 = 82. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −6 | capability blast radius (high) — client exposure if the model is manipulated |
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Tool "wez_spawn" appears to run shell commands or evaluate code (keyword "spawn" in tool name). Arbitrary execution driven by model input is one of the most dangerous MCP capabilities; combined with any untrusted input it becomes RCE.
Fix: Sandbox execution, allowlist commands/arguments, and never pass model output to a shell unescaped.
Location: tool wez_spawn
In the server's implementation (`build/init.js:1`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: { execSync } from 'node:child_process'; import { existsSync, mkdirSync, readFileSync, writeFileSync } from 'node:fs'; im
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server build/init.js
In the server's implementation (`build/platform.js:8`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: ecFileSync } from 'node:child_process'; import { existsSync } from 'node:fs'; import { homedir } from 'node:os'; import
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server build/platform.js
In the server's implementation (`build/wez-mcp.js:8`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: nodeSpawn } from 'node:child_process'; import { existsSync, mkdirSync, readFileSync, readdirSync, renameSync, statSync,
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server build/wez-mcp.js
In the server's implementation (`build/init.js:50`): A shell/process command assembled from concatenated or interpolated values is command injection when any part is attacker-influenced — the OWASP canonical RCE flow. Verify what reaches the interpolated value. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: sswd return execSync(`eval echo ~${sudoUser}`, { encoding: 'utf8', timeout: 3000 }).trim(); }
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server build/init.js
In the server's implementation (`build/platform.js:39`): A shell/process command assembled from concatenated or interpolated values is command injection when any part is attacker-influenced — the OWASP canonical RCE flow. Verify what reaches the interpolated value. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: const out = execSync(`pgrep -x ${name}`, { encoding: 'utf8', timeout: 3000 }); return out.trim()
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server build/platform.js
Tool "wez_spawn" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.
Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.
Location: tool wez_spawn
"wezterm-agent-mcp" executes postinstall script(s) at install time. An install hook runs at install time; most are routine build/setup, but review what it does before trusting it.
Evidence: node build/postinstall.js
Fix: Review the scripts; install with --ignore-scripts where possible and vet what they do.
Location: package wezterm-agent-mcp
Each tool and what it can reach — statically extracted from the published source.
wez_spawnruns code / shellwez_clean_socketsno sensitive capabilitywez_focus_directionno sensitive capabilitywez_focus_paneno sensitive capabilitywez_focus_tabno sensitive capabilitywez_fullscreenno sensitive capabilitywez_get_textno sensitive capabilitywez_kill_allno sensitive capabilitywez_kill_guino sensitive capabilitywez_kill_muxno sensitive capabilitywez_kill_paneno sensitive capabilitywez_kill_tabno sensitive capabilitywez_launch_agentsno sensitive capabilitywez_launch_gridno sensitive capabilitywez_launch_mixedno sensitive capabilitywez_listno sensitive capabilitywez_move_to_tabno sensitive capabilitywez_read_allno sensitive capabilitywez_read_all_deepno sensitive capabilitywez_read_tabno sensitive capabilitywez_reconcileno sensitive capabilitywez_rename_workspaceno sensitive capabilitywez_resize_paneno sensitive capabilitywez_restart_paneno sensitive capabilitywez_screenshotno sensitive capabilitywez_screenshot_all_tabsno sensitive capabilitywez_send_keyno sensitive capabilitywez_send_key_allno sensitive capabilitywez_send_textno sensitive capabilitywez_send_text_allno sensitive capabilitywez_send_text_submitno sensitive capabilitywez_send_text_submit_allno sensitive capabilitywez_send_text_submit_someno sensitive capabilitywez_session_recoverno sensitive capabilitywez_session_saveno sensitive capabilitywez_set_tab_titleno sensitive capabilitywez_set_window_titleno sensitive capabilitywez_splitno sensitive capabilitywez_startno sensitive capabilitywez_statusno sensitive capabilitywez_zoom_paneno sensitive capabilityScan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.1.9 latest |
B 82/100 | 8 | 1.13.0 | 2026-09-07 |
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan wezterm-agent-mcp --online
Hotel booking MCP server — 300K+ properties, real confirmation numbers, loyalty programs. Builders monetize every booking via Stripe Connect. The first MCP server that completes real hotel reservations inside AI conversations.
Manage AdGuard Home through AI assistants
Read-only Azure DevOps for MCP clients using only your existing browser session — no PAT, no Azure CLI. Browse work items, pull requests, comments, attachments and Artifacts feeds across every project, repo and feed you can access.
MCP server for Adobe Experience Manager Assets integration development
Servidor MCP para el tiempo oficial de España (API pública OpenData de AEMET). Predicción, observación y avisos como herramientas MCP tipadas.
A standalone MCP stdio bridge for Affinity by Canva's local MCP SSE server.