Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

NexusWindows for Claude

PYPI · NEXUS-WINDOWS-CLAUDE

Windows computer use in the background: UI Automation and Win32 messages, every action read back.

Available components

pypi · nexus-windows-claude 44
−6 this week 44 Trust /100

Last scanned (10 hours ago)

Scores higher than 43% of PyPI servers

Category Browser Automation

Trust breakdown (7 categories)

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 Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs uv_build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 2 of 42 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency71
  • Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
  • Cryptographically verified build provenance (signed, bound to pironjulien/NexusWindows-Claude). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 7 days ago).Pass
  • Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
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 →

Changelog

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.

  • 1 Nov 26 −6
    • Source repository: pass → fail ▼ security
    • Security disclosure: pass → unverified ▼ functional
  • 28 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
    • Package version: 3.7.1 → 3.7.4 functional
    • Package version: 3.7.1 → 3.7.3 functional
    • Package version: 3.7.1 → 3.7.2 functional
  • 27 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
    • Package version: 3.3.1 → 3.7.1 functional
    • Package version: 3.3.1 → 3.7.0 functional
    • Package version: 3.3.1 → 3.5.0 functional
    • Package version: 3.3.1 → 3.3.2 functional
  • 26 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
    • Stability: Stability not yet verified: our sandbox could not run this package, so we have no schema to compare. security
    • Tool safety: Tool safety not yet verified: our sandbox could not run this package, so we have no tool text to scan. security
    • Schema quality: Schema quality not yet verified: our sandbox could not run this package, so we have no schema to assess. functional
    • Capabilities: Protocol version not yet verified: our sandbox could not run this package, so we never saw its MCP handshake. functional
    • Tool coverage: Tool coverage not yet verified: our sandbox could not run this package, so we have no tool definitions to assess. functional
    • Package version: 3.2.2 → 3.3.1 functional
    • Package version: 3.2.2 → 3.3.0 functional
  • 25 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
    • Tool safety: Tool safety not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. 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
    • Capabilities: Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet. functional
    • Tool coverage: Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. functional
    • Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
    • Package version: 3.1.4 → 3.2.2 functional
    • Package version: 3.1.4 → 3.2.1 functional
    • Package version: 3.1.4 → 3.1.5 functional
  • 24 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
    • Package version: 3.0.1 → 3.1.4 functional
    • Package version: 3.0.1 → 3.1.3 functional
    • Package version: 3.0.1 → 3.1.1 functional
    • Package version: 3.0.1 → 3.1.0 functional
    • Package version: 3.0.1 → 3.0.2 functional
  • 23 Oct 26 35

    First indexed and scored.

Diagnostics

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 5 Nov 2026 · Analysed pypi/nexus-windows-claude@3.7.4

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 pironjulien/NexusWindows-Claude
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pironjulien/NexusWindows-Claude/.github/workflows/publish.yml@refs/tags/v3.7.4
Rekor log index 3542939402
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:866b82d1b17e79f883ee4492e27b3a559ffd32bf43c895acbcb7497d7374f681

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted uv_build

Background: Why install scripts are a supply-chain risk →

Dependencies 42 packages
Packages resolved 42
No linked repository 2
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools

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.

Install

How do I install the NexusWindows for Claude MCP server?

NexusWindows for Claude runs locally as a PyPI package, launched with uvx nexus-windows-claude. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · nexus-windows-claude

# add to Claude Code
claude mcp add pironjulien-nexus-windows-claude -- uvx nexus-windows-claude
Common questions

What is the NexusWindows for Claude MCP server?

NexusWindows for Claude is an MCP server listed in the public MCP registry as io.github.pironjulien/nexus-windows-claude. Windows computer use in the background: UI Automation and Win32 messages, every action read back. This page covers its PyPI package (nexus-windows-claude).

Is the NexusWindows for Claude MCP server safe to use?

NexusWindows for Claude scores 44 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 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 NexusWindows for Claude MCP server still maintained?

NexusWindows for Claude is still listed as active in the MCP registry. We last reached this channel on 5 November 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 NexusWindows for Claude MCP server under?

NexusWindows for Claude declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.