Wezterm Agent MCP Server

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

Trust grade
B
82/100
Last scanned get badge →
Trust
B · 82/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
B Why this grade threat 89 − adoption risk = 82/100

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:

PointsWhat was foundCategory
−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:

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

Findings 8

high Tool "wez_spawn" exposes command/code executionMTC-CAP-001

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

high Shell/command execution in server code (build/init.js)MTC-SRC-002

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

high Shell/command execution in server code (build/platform.js)MTC-SRC-002

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

high Shell/command execution in server code (build/wez-mcp.js)MTC-SRC-002

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

medium Untrusted input concatenated into a command sink (build/init.js)MTC-SRC-009

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

medium Untrusted input concatenated into a command sink (build/platform.js)MTC-SRC-009

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

low Mutating tool "wez_spawn" declares no destructiveHintMTC-CAP-005

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

low Package runs install-time scripts (postinstall)MTC-SUP-010

"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

Tools 41

Each tool and what it can reach — statically extracted from the published source.

  • wez_spawnruns code / shell
  • wez_clean_socketsno sensitive capability
  • wez_focus_directionno sensitive capability
  • wez_focus_paneno sensitive capability
  • wez_focus_tabno sensitive capability
  • wez_fullscreenno sensitive capability
  • wez_get_textno sensitive capability
  • wez_kill_allno sensitive capability
  • wez_kill_guino sensitive capability
  • wez_kill_muxno sensitive capability
Show 31 more tools ↓
  • wez_kill_paneno sensitive capability
  • wez_kill_tabno sensitive capability
  • wez_launch_agentsno sensitive capability
  • wez_launch_gridno sensitive capability
  • wez_launch_mixedno sensitive capability
  • wez_listno sensitive capability
  • wez_move_to_tabno sensitive capability
  • wez_read_allno sensitive capability
  • wez_read_all_deepno sensitive capability
  • wez_read_tabno sensitive capability
  • wez_reconcileno sensitive capability
  • wez_rename_workspaceno sensitive capability
  • wez_resize_paneno sensitive capability
  • wez_restart_paneno sensitive capability
  • wez_screenshotno sensitive capability
  • wez_screenshot_all_tabsno sensitive capability
  • wez_send_keyno sensitive capability
  • wez_send_key_allno sensitive capability
  • wez_send_textno sensitive capability
  • wez_send_text_allno sensitive capability
  • wez_send_text_submitno sensitive capability
  • wez_send_text_submit_allno sensitive capability
  • wez_send_text_submit_someno sensitive capability
  • wez_session_recoverno sensitive capability
  • wez_session_saveno sensitive capability
  • wez_set_tab_titleno sensitive capability
  • wez_set_window_titleno sensitive capability
  • wez_splitno sensitive capability
  • wez_startno sensitive capability
  • wez_statusno sensitive capability
  • wez_zoom_paneno sensitive capability

What this scan could not see

Versions 1

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

VersionScoreFindingsEngineScanned
v0.1.9 latest B 82/100 8 1.13.0 2026-09-07

Embed this score

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.

MCP Trust Score: B · 82/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/wezterm-agent-mcp/badge.svg)](https://mcptrustchecker.com/registry/wezterm-agent-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/wezterm-agent-mcp"><img src="https://mcptrustchecker.com/registry/wezterm-agent-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/wezterm-agent-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

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

Use the free API → How scoring works

More in Developer Tools