windows-mcp@0.9.0
VERIFIED· not startedPublisher claims: "Lightweight MCP Server for interacting with Windows Operating System." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Not started: dependency install failed; the server itself was not observed.- Tested
- the dependency install step · every file read, file written and host contacted by what ran
- Not tested
- server startup · the tool list · tool behavior
What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
- no credential variables read in the code
- Where it talks to
- no vendor host named in the codeAlso microsoft.com — not the publisher's domain; check what for before connecting.
- What we saw when it ran
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Connect it under the guard. Not started: dependency install failed; the server itself was not observed. The code names no credential variable; the guard pins the network to what the honeypot saw and logs every call.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
What changed since 0.8.9
vet-skills diff windows-mcp 0.8.9 0.9.0In the sandbox, this version reached for nothing 0.8.9 did not. Compared from the two recorded runs, not from source.
0.8.9 was not run in the sandbox (install failed); the comparison covers what static analysis recorded only.
The guard can hold an update like this until someone approves it (runtime.on_change: hold). A change that only shows with a real credential, or on a path the run did not reach, is not in a trace and so not in this comparison.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-22 and scored it 83/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 1 s · 2 scenarios · 0 deviationsStatic findings
process = subprocess.Popen(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.result = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.return "Error: Provide either pid or name parameter for kill mode."Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.<summary>Install in Perplexity Desktop</summary> 1. Install [Perplexity Desktop](https://apps.microsoft.com/detail/xp8jnqfbqh6pvf). 2. Open Perplexity Desktop aFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.<summary>Install in Codex CLI</summary> 1. Install Codex CLI. ```shell npm install -g @openai/codex ``` 2. Open `%USERPROFILE%/.codex/config.toml`. 3. Add the `Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.install = subprocess.run(["mkcert", "-install"], capture_output=True, text=True)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.return f"Access denied to kill PID {pid}. Try running as administrator."Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.…nalytics): @mcp.tool( name="Process", description='List and kill running processes. Keywords: task manager, running tasks, kill, terminate, stop …Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.return subprocess.run(args, capture_output=True, encoding="oem", errors="replace")Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out."""Process tool — list and kill running processes."""Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.with subprocess.Popen(*popenargs, **kwargs) as process:Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.<summary>Install in Qwen Code</summary> 1. Install Qwen Code. ```shell npm install -g @qwen-code/qwen-code@latest ``` 2. Open `%USERPROFILE%/.qwen/settings.jsonFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.| `WINDOWS_MCP_DEBUG` | `false` | Set to `1`, `true`, `yes`, or `on` to enable debug mode, which sets the log level to DEBUG for verbose output. Also available as the `--debug` CLI flag. |Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.mkcert = subprocess.run(["where", "mkcert"], capture_output=True).returncode == 0Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.<summary> Install in Gemini CLI</summary> 1. Install Gemini CLI. ```shell npm install -g @google/gemini-cli ``` 2. Open `%USERPROFILE%/.gemini/settings.json`. 3Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.process = _process = subprocess.Popen(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.result = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.logger.debug('Other exception occurred, attempting to kill process...')Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
Not checked against OSV yet; the weekly check has not reached this version.