dsh-cua - Windows Computer Use
PYPI · DSH-CUA · SCANNED SEP 29
Windows computer-use MCP server for dsh (DeepSeek Harness), client-neutral, 19 tools.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security91
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known advisory affects this package; its severity couldn't be graded. See how to fix → View diagnostics → Fail
- Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 36 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to Hutusion/dsh-cua). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability0
- Schema quality not yet verified: our sandbox could not run this package, so we have no schema to assess.Unverified
Stability & Change Management0
- Stability not yet verified: our sandbox could not run this package, so we have no schema to compare.Unverified
Tool Coverage0
- Tool coverage not yet verified: our sandbox could not run this package, so we have no tool definitions to assess.Unverified
Tool Safety0
- Tool safety not yet verified: our sandbox could not run this package, so we have no tool text to scan.Unverified
Capabilities0
- Protocol version not yet verified: our sandbox could not run this package, so we never saw its MCP handshake.Unverified
Unverified: 5 categories
Categories scored 0 because our sandbox could not run this package, so we have no schema for these checks to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until we can run it. How we score packages →
How do I install the dsh-cua - Windows Computer Use MCP server?
dsh-cua - Windows Computer Use runs locally as a PyPI package, launched with uvx dsh-cua. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · dsh-cua
claude mcp add hutusion-dsh-cua -- uvx dsh-cua
{
"mcpServers": {
"hutusion-dsh-cua": {
"command": "uvx",
"args": [
"dsh-cua"
]
}
}
} {
"servers": {
"hutusion-dsh-cua": {
"command": "uvx",
"args": [
"dsh-cua"
]
}
}
} codex mcp add hutusion-dsh-cua -- uvx dsh-cua
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"hutusion-dsh-cua": {
"type": "local",
"command": [
"uvx",
"dsh-cua"
],
"enabled": true
}
}
} openclaw mcp add hutusion-dsh-cua --command uvx --arg dsh-cua
mcp_servers:
hutusion-dsh-cua:
command: "uvx"
args: ["dsh-cua"] {
"McpServers": {
"hutusion-dsh-cua": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"dsh-cua"
]
}
}
} assistant mcp add hutusion-dsh-cua -t stdio -c uvx -a dsh-cua
{
"mcpServers": {
"hutusion-dsh-cua": {
"command": "uvx",
"args": [
"dsh-cua"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 29 Sept 26 +26
- Malware scan: unverified → pass ▲ security
- Provenance: unverified → pass ▲ security
- The attested source repository moved: Hutusion/dsh-cua security
- Package version: 0.3.4 → 0.4.0 functional
- 28 Sept 26 −42
- Tool safety: pass → unverified ▼ security
- Malware scan: pass → unverified ▼ security
- Provenance: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: Stability not yet verified: our sandbox could not run this package, so we have no schema to compare. security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- First check of Schema quality: unverified functional
- Package version: 0.3.4 → 0.4.0 functional
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 63
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 29 Sept 2026 · Analysed pypi/dsh-cua@0.4.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | Hutusion/dsh-cua |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/Hutusion/dsh-cua/.github/workflows/publish.yml@refs/tags/v0.4.0 |
| Rekor log index | 2981721156 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:fff25f10ea58bfb4172afff9498daa911a77c5d7c0adbfe462d62831219851bc |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Vulnerabilities 2 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-hwfp-hg2m-9vr2 | CVE-2021-32559 | medium | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H | yes |
| PYSEC-2021-112 | CVE-2021-32559 | none | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 36 packages
| Packages resolved | 36 |
|---|---|
| Stale | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
Tools for package channels are captured by running the package in an isolated sandbox. Our sandbox could not run this package, so no tool list has been captured. That is a gap on our side, not a finding about the package.
What is the dsh-cua - Windows Computer Use MCP server?
dsh-cua - Windows Computer Use is an MCP server listed in the public MCP registry as io.github.Hutusion/dsh-cua. Windows computer-use MCP server for dsh (DeepSeek Harness), client-neutral, 19 tools. This page covers its PyPI package (dsh-cua).
Is the dsh-cua - Windows Computer Use MCP server safe to use?
dsh-cua - Windows Computer Use scores 47 out of 100 on VerifyMCP. We recorded 2 known advisories against it as of 29 September 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
Is the dsh-cua - Windows Computer Use MCP server still maintained?
dsh-cua - Windows Computer Use is still listed as active in the MCP registry. We last reached this channel on 29 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the dsh-cua - Windows Computer Use MCP server under?
dsh-cua - Windows Computer Use declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.