Oswright MCP Server

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.

Trust grade
A
92/100
Last scanned get badge →
Trust
A · 92/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.
A Why this grade threat 100 − adoption risk = 92/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 − 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:

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

Findings 3

high Shell/command execution in server code (oswright/clipboard.py)MTC-SRC-002

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

high Shell/command execution in server code (oswright/mcp_server.py)MTC-SRC-002

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

high Shell/command execution in server code (oswright/window.py)MTC-SRC-002

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

Tools 32

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

  • click_textno sensitive capability
  • click_ui_elementno sensitive capability
  • close_windowno sensitive capability
  • double_click_textno sensitive capability
  • fill_fieldno sensitive capability
  • fill_formno sensitive capability
  • fill_ui_elementno sensitive capability
  • find_image_on_screenno sensitive capability
  • find_text_on_screenno sensitive capability
  • focus_windowno sensitive capability
Show 22 more tools ↓
  • get_active_windowno sensitive capability
  • get_clipboardno sensitive capability
  • get_mouse_positionno sensitive capability
  • get_ocr_infono sensitive capability
  • get_screen_infono sensitive capability
  • get_ui_treeno sensitive capability
  • hover_textno sensitive capability
  • launch_appno sensitive capability
  • list_windowsno sensitive capability
  • minimize_windowno sensitive capability
  • mouse_clickno sensitive capability
  • mouse_double_clickno sensitive capability
  • mouse_dragno sensitive capability
  • mouse_moveno sensitive capability
  • mouse_scrollno sensitive capability
  • press_keyno sensitive capability
  • read_screen_textno sensitive capability
  • right_click_textno sensitive capability
  • screenshotno sensitive capability
  • screenshot_windowno sensitive capability
  • set_clipboardno sensitive capability
  • type_textno 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.3.1 latest A 92/100 3 1.9.0 2026-07-23

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: A · 92/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/oswright/badge.svg)](https://mcptrustchecker.com/registry/oswright)
HTML
<a href="https://mcptrustchecker.com/registry/oswright"><img src="https://mcptrustchecker.com/registry/oswright/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/oswright/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 oswright --online --registry pypi

Use the free API → How scoring works

More in Developer Tools