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 Antigravity

PYPI · NEXUS-WINDOWS-ANTIGRAVITY

Windows computer use in the background for Antigravity: UI Automation, Win32 messages, read back.

−3 this week 75 Trust /100

Last scanned (16 hours ago)

Scores higher than 73% 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 hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 1 of 33 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-Antigravity). 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 Usability52
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1287 tokens (~257/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
  • Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
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 current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (15)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

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.

  • 4 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Nov 26 −6
    • Source repository: pass → fail ▼ security
    • Security disclosure: pass → unverified ▼ functional
  • 31 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 29 Oct 26 +16
    • Malware scan: unverified → pass ▲ security
  • 28 Oct 26 0
    • Malware scan: unverified → pass ▲ security
    • Package version: 3.4.3 → 3.6.0 functional
    • Package version: 3.4.3 → 3.5.0 functional
  • 27 Oct 26 +1
    • Package version: 3.2.8 → 3.4.3 functional
    • Package version: 3.2.8 → 3.4.2 functional
    • Package version: 3.2.8 → 3.4.1 functional
    • Package version: 3.2.8 → 3.3.1 functional
    • Package version: 3.2.8 → 3.3.0 functional
    • Package version: 3.2.8 → 3.2.10 functional
    • Package version: 3.2.8 → 3.2.9 functional
  • 26 Oct 26 0
    • Package version: 3.1.7 → 3.2.8 functional
    • Package version: 3.1.7 → 3.2.7 functional
    • Package version: 3.1.7 → 3.2.6 functional
    • Package version: 3.1.7 → 3.2.5 functional
    • Package version: 3.1.7 → 3.2.3 functional
    • Package version: 3.1.7 → 3.2.2 functional
    • Package version: 3.1.7 → 3.2.1 functional
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-antigravity@3.6.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 pironjulien/NexusWindows-Antigravity
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pironjulien/NexusWindows-Antigravity/.github/workflows/publish.yml@refs/tags/v3.6.0
Rekor log index 3544179420
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:8a5e6615819d1b3d467eedd6ab03176353927dce7afb8baa6262901451917f77

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend Known build tool hatchling.build

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

Dependencies 33 packages
Packages resolved 33
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~912 tokens

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 →

Tool Tokens
act ~365

Act in ONE batch, in the background, on a NAMED window (hwnd), without reading the code: shared token, emergency stop and the user's pause are handled here. Actions: click, double_click, right_click, type, set, clear, check, uncheck, select (option), expand, collapse, menu (path), key, scroll, drag, hover, wait (seconds, text), focus. Target: target="Exact label", "#N", box_2d or x/y; ambiguous label refused. Steps ✓ = ~ ✗, status = the worst; follow `next`. Batch stopped on ~ or ✗, nothing more sent and no replay; look before resuming after an unknown outcome. Outward actions (paying, sending, publishing, transferring, and the Enter key that would trigger them): `confirm: true` AND `accord: "<token>"` (on the step or as a parameter), returned by the first refusal that describes the exact action. Local destruction (permanent deletion, uninstalling, formatting, resetting): `confirm: true` alone. The user's explicit order = confirmation; your own initiative = ask first. Same batch without a look: refused. foreground=True: real mouse/keyboard as a fallback only. Example: {"hwnd": "Order", "steps": [{"action": "set", "target": "Name", "text": "Alice"}, {"action": "check", "target": "Accept"}, {"action": "click", "target": "Submit"}]}

NameTypeReqDescription
accord–––
foregroundboolean––
hwnd–––
repeatboolean––
stepsarrayyes–
thenstring––
time_budgetnumber––

No output schema declared.

No examples provided.

launch ~168

Open an application (name such as "notepad.exe", or path), a folder or a document, like a double-click; the opening is read back. Settings page: app="ms-settings:display" (opened behind the user's window, read back). Refused: web addresses http, https, ftp (web pages: nexus-browser). args: arguments of a .exe program (a file to open…), never for a document, a folder or an address; also accepted after the program in `app`, a path with spaces is never split. Chromium/Electron apps: files only, never a switch. Example: {"app": "notepad.exe", "args": "C:\\Dev\\notes.txt"}

NameTypeReqDescription
appstringyes–
argsstring––

No output schema declared.

No examples provided.

look ~231

GOLDEN RULE: look → act in one batch, targets by label; never resend a batch without looking. See a NAMED window (hwnd: number, title or process) WITHOUT bringing it to the front (covered ones too): one line per element "[N] role "name" = "value" states @x,y"; image (WebP ≤ 2000 px) only if the tree is too thin, or with capture_screenshot=true, annotate (numbers drawn) or zoom=box_2d (area enlarged); query filters; format="json": compact JSON (box_2d 0-1000 per element). Same screen as the last image sent: not attached again. Unlocks a batch. Example: {"hwnd": "Notepad", "query": "save"}

NameTypeReqDescription
annotateboolean––
capture_screenshot–––
formatstring––
hwnd–––
max_depthinteger––
max_elementsinteger––
output_path–––
query–––
zoom–––

No output schema declared.

No examples provided.

window ~88

Manage a NAMED window (hwnd: number, title or process). action="close": close it cleanly (UI Automation, then WM_CLOSE), the closing is read back; a "Save?" prompt, if any, is reported, never answered. Example: {"action": "close", "hwnd": 123456}

NameTypeReqDescription
actionstringyes–
hwnd–yes–

No output schema declared.

No examples provided.

windows ~60

List open windows: hwnd, title, process (the real application for UWP), position, foreground. by_app=true: grouped by application. Example: {"by_app": false}

NameTypeReqDescription
by_appboolean––
visible_onlyboolean––

No output schema declared.

No examples provided.

Install

How do I install the NexusWindows for Antigravity MCP server?

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

pypi · nexus-windows-antigravity

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

What is the NexusWindows for Antigravity MCP server?

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

Is the NexusWindows for Antigravity MCP server safe to use?

NexusWindows for Antigravity scores 75 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.

What tools does the NexusWindows for Antigravity MCP server expose?

NexusWindows for Antigravity exposes 5 tools: windows, look, act, launch, window. Their descriptions and schemas cost roughly 912 tokens of context every time the server is loaded.

Is the NexusWindows for Antigravity MCP server still maintained?

NexusWindows for Antigravity 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 Antigravity MCP server under?

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

What did VerifyMCP test on the NexusWindows for Antigravity MCP server?

VerifyMCP ran 15 checks on NexusWindows for Antigravity, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about NexusWindows for Antigravity: Security disclosure. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.