computer-mcp
PyPI
v0.0.7
Published by commandagi — 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.
Cross-platform MCP server for computer automation and control
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 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 7 = 93. 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 "spawn_terminal" appears to run shell commands or evaluate code (keyword "spawn" in tool name, parameter "command"). 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 spawn_terminal
In the server's implementation (`computer_mcp/actions/accessibility_tree.py:94`): 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: ' result = subprocess.run( ["osascript", "-e", script], capture_output=Tr
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 computer_mcp/actions/accessibility_tree.py
In the server's implementation (`computer_mcp/actions/focused_app.py:51`): 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: ''' result = subprocess.run( ["osascript", "-e", script], capture_output=True,
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 computer_mcp/actions/focused_app.py
In the server's implementation (`computer_mcp/actions/keyboard.py:246`): 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: result = subprocess.run( ["osascript", "-e", script], capture_output=Tr
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 computer_mcp/actions/keyboard.py
In the server's implementation (`computer_mcp/actions/window.py:827`): 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: result_osascript = subprocess.run( ["osascript", "-e", script], capture_output=Tr
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 computer_mcp/actions/window.py
In the server's implementation (`computer_mcp/core/utils.py:227`): 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: ' result = subprocess.run( ["osascript", "-e", script], capture_output=Tr
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 computer_mcp/core/utils.py
In the server's implementation (`computer_mcp/handlers/accessibility_tree.py:86`): 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: ' result = subprocess.run( ["osascript", "-e", script], capture_output=Tr
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 computer_mcp/handlers/accessibility_tree.py
In the server's implementation (`computer_mcp/handlers/focused_app.py:43`): 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: ''' result = subprocess.run( ["osascript", "-e", script], capture_output=True,
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 computer_mcp/handlers/focused_app.py
In the server's implementation (`computer_mcp/handlers/window.py:1188`): 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: result_osascript = subprocess.run( ["osascript", "-e", script], capture_output=True
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 computer_mcp/handlers/window.py
Tool "spawn_terminal" takes a command-shaped parameter "command" with no enum/pattern constraint. Free-form, model- or attacker-controlled arguments reaching a shell is the command-injection precondition.
Fix: Constrain the parameter (enum/pattern), or build the command from a fixed template with escaped args.
Location: tool spawn_terminal · inputSchema.properties.command
Tool "spawn_terminal" takes a command-shaped parameter "shell" with no enum/pattern constraint. Free-form, model- or attacker-controlled arguments reaching a shell is the command-injection precondition.
Fix: Constrain the parameter (enum/pattern), or build the command from a fixed template with escaped args.
Location: tool spawn_terminal · inputSchema.properties.shell
Tool "spawn_terminal" 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 spawn_terminal
Each tool and what it can reach — statically extracted from the published source.
spawn_terminalruns code / shellbutton_downno sensitive capabilitybutton_upno sensitive capabilityclickno sensitive capabilityclose_terminalno sensitive capabilityclose_windowno sensitive capabilitydouble_clickno sensitive capabilitydragno sensitive capabilityget_window_infono sensitive capabilitykey_downno sensitive capabilitykey_pressno sensitive capabilitykey_upno sensitive capabilitylist_terminalsno sensitive capabilitylist_virtual_desktopsno sensitive capabilitylist_windowsno sensitive capabilitymaximize_windowno sensitive capabilityminimize_windowno sensitive capabilitymouse_moveno sensitive capabilitymove_windowno sensitive capabilitymove_window_to_virtual_desktopno sensitive capabilityread_terminal_outputno sensitive capabilityresize_windowno sensitive capabilityrestore_windowno sensitive capabilityscreenshotno sensitive capabilityscreenshot_windowno sensitive capabilitysend_terminal_keyno sensitive capabilitysend_terminal_textno sensitive capabilityset_configno sensitive capabilityset_window_topmostno sensitive capabilitysnap_window_bottomno sensitive capabilitysnap_window_leftno sensitive capabilitysnap_window_rightno sensitive capabilitysnap_window_topno sensitive capabilityswitch_to_windowno sensitive capabilityswitch_virtual_desktopno sensitive capabilitytriple_clickno sensitive capabilitytypeno 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.0.7 latest |
A 93/100 | 12 | 1.13.0 | 2026-08-25 |
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 computer-mcp --online --registry pypi
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.