NexusWindows for Codex
NPM · NEXUS-WINDOWS-CODEX
Windows computer use in the background for Codex: UI Automation, Win32 messages, read back.
Available components
Last scanned (10 hours ago)
Scores higher than 37% of npm servers
Category Browser Automation
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 Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pironjulien/NexusWindows-Codex). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability66
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 557 tokens (~111/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage81
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 43% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 23 Oct 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 23 Oct 2026 · Analysed npm/nexus-windows-codex@3.0.1
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 | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pironjulien/NexusWindows-Codex |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pironjulien/NexusWindows-Codex/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3420582191 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:45e151141535eff4fdd2c477ed36fd2dfb7669e14841d762776bcde57b5d69518deaa09cd6f1ba2fefd888fde7336bed5f59572b4b63fc39bb2da6ed0 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
act Act in the window ~103
Steps on the window of the last look, in the background first (Win32 messages, UI Automation, DevTools for Chromium), the real mouse/keyboard only as a fallback under the shared foreground token. One step, or up to 32 each with its own expect; stops at the first step not verified. Per step: ✓ verified, = already done, ~ unknown (never replayed: look again), ✗ failed or refused.
| Name | Type | Req | Description |
|---|---|---|---|
| steps | array | yes | – |
No output schema declared.
No examples provided.
launch Launch an app, folder or document ~122
Open an application (name, absolute path or Store app id), a folder or a document (absolute path) or a Settings page (ms-settings:...) and give the foreground back to the user. Returns the windows attributed to this launch, each with its proof: "process" (the process the shell returned) or "application" (the requested application, started after the request: another instance started at the same moment could be taken for it); other new windows come back as candidates (outcome unknown). Look at one before acting.
| Name | Type | Req | Description |
|---|---|---|---|
| app | string | yes | – |
No output schema declared.
No examples provided.
look Look at a window ~124
See a window in the background, without bringing it forward: UI Automation tree (roles, names, ids, values, states) and, with mode image or both, a native capture that works even when the window is covered. Selects that window for act; an observation serves one act and expires after 60 s.
| Name | Type | Req | Description |
|---|---|---|---|
| mode | string | – | text (UI Automation tree, default), image (native capture), both |
| window | integer|string | – | Window id from windows, or a unique part of its title or app; omitted: the window of the last look |
No output schema declared.
No examples provided.
window Manage a window ~69
close: close the window (one close message, read back; a "save?" prompt is reported, never answered).
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| window | integer|string | – | Window id from windows, or a unique part of its title or app; omitted: the window of the last look |
No output schema declared.
No examples provided.
windows List windows ~48
Application windows on the desktop (id, app, title, pid), like the taskbar. Password managers are never listed. filter: part of a title or app.
| Name | Type | Req | Description |
|---|---|---|---|
| filter | string | – | – |
No output schema declared.
No examples provided.
How do I install the NexusWindows for Codex MCP server?
NexusWindows for Codex runs locally as an npm package, launched with npx -y nexus-windows-codex. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · nexus-windows-codex
claude mcp add pironjulien-nexus-windows-codex -- npx -y nexus-windows-codex
What is the NexusWindows for Codex MCP server?
NexusWindows for Codex is an MCP server listed in the public MCP registry as io.github.pironjulien/nexus-windows-codex. Windows computer use in the background for Codex: UI Automation, Win32 messages, read back. This page covers its npm package (nexus-windows-codex).
Is the NexusWindows for Codex MCP server safe to use?
NexusWindows for Codex scores 63 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 23 October 2026. It declares no install or post-install scripts. 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.
What tools does the NexusWindows for Codex MCP server expose?
NexusWindows for Codex exposes 5 tools: windows, look, act, launch, window. Their descriptions and schemas cost roughly 466 tokens of context every time the server is loaded.
Is the NexusWindows for Codex MCP server still maintained?
NexusWindows for Codex is still listed as active in the MCP registry. We last reached this channel on 23 October 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 Codex MCP server under?
NexusWindows for Codex declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.