oswright
PyPI
v0.3.1
Published by an unidentified publisher — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.
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 − 8 = 92. 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 |
| −2 | publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read |
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.
In the server's implementation (`oswright/clipboard.py:48`): 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: try: return subprocess.check_output(["pbpaste"], text=True, timeout=5) except subprocess.SubprocessE
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 oswright/clipboard.py
In the server's implementation (`oswright/mcp_server.py:1089`): 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: e command split subprocess.Popen(command.split(), shell=False) else: subprocess.Popen(shlex.split(co
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 oswright/mcp_server.py
In the server's implementation (`oswright/window.py:209`): 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: output = subprocess.check_output( ["wmctrl", "-l", "-G"], text=True, timeout=5
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 oswright/window.py
Each tool and what it can reach — statically extracted from the published source.
click_textno sensitive capabilityclick_ui_elementno sensitive capabilityclose_windowno sensitive capabilitydouble_click_textno sensitive capabilityfill_fieldno sensitive capabilityfill_formno sensitive capabilityfill_ui_elementno sensitive capabilityfind_image_on_screenno sensitive capabilityfind_text_on_screenno sensitive capabilityfocus_windowno sensitive capabilityget_active_windowno sensitive capabilityget_clipboardno sensitive capabilityget_mouse_positionno sensitive capabilityget_ocr_infono sensitive capabilityget_screen_infono sensitive capabilityget_ui_treeno sensitive capabilityhover_textno sensitive capabilitylaunch_appno sensitive capabilitylist_windowsno sensitive capabilityminimize_windowno sensitive capabilitymouse_clickno sensitive capabilitymouse_double_clickno sensitive capabilitymouse_dragno sensitive capabilitymouse_moveno sensitive capabilitymouse_scrollno sensitive capabilitypress_keyno sensitive capabilityread_screen_textno sensitive capabilityright_click_textno sensitive capabilityscreenshotno sensitive capabilityscreenshot_windowno sensitive capabilityset_clipboardno sensitive capabilitytype_textno 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.3.1 latest |
A 92/100 | 3 | 1.9.0 | 2026-07-23 |
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 oswright --online --registry pypi
Security scan results for the 1stay MCP server.
Security scan results for the Adguard Home MCP server.
Security scan results for the Ado Browser MCP server.
Security scan results for the Adobe Experience Dev MCP server.
Security scan results for the Aemet MCP server.
Security scan results for the Affinity Mcp Bridge MCP server.