# RaroCUA (npm · @mectro/raro-cua)

Local macOS Computer Use MCP server with screenshots, AX trees, and app actions.

- Trust score: 31/100 (low)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-29

## Components

- npm · `@mectro/raro-cua`: 31/100 (this document), [markdown](https://verifymcp.io/servers/mectrojohnny-raro-cua/mectro-raro-cua.md), [page](https://verifymcp.io/servers/mectrojohnny-raro-cua/mectro-raro-cua)

## Channel facts

- Registry: `npm`
- Package: `@mectro/raro-cua`
- Version: `0.1.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-29.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 6/100
  - Repository check failed: no source repository is declared.
  - Provenance check failed: no build-provenance attestation is published.
  - Licence could not be checked: the licence is shipped as a file inside the package, not declared as a standard (SPDX) licence identifier, so we cannot tell whether it is OSI-approved.
  - Actively maintained (last published 35 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 0/100
  - Schema quality not yet verified: our sandbox could not run this package, so we have no schema to assess.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: our sandbox could not run this package, so we have no schema to compare.
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: our sandbox could not run this package, so we have no tool definitions to assess.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: our sandbox could not run this package, so we have no tool text to scan.
- **Capabilities**: 0/100
  - Protocol version not yet verified: our sandbox could not run this package, so we never saw its MCP handshake.

**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.

## Install

### How do I install the RaroCUA MCP server?

RaroCUA runs locally as an npm package, launched with npx -y @mectro/raro-cua. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add mectrojohnny-raro-cua -- npx -y @mectro/raro-cua
```

### Cursor

```json
{
  "mcpServers": {
    "mectrojohnny-raro-cua": {
      "command": "npx",
      "args": [
        "-y",
        "@mectro/raro-cua"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "mectrojohnny-raro-cua": {
      "command": "npx",
      "args": [
        "-y",
        "@mectro/raro-cua"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add mectrojohnny-raro-cua -- npx -y @mectro/raro-cua
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mectrojohnny-raro-cua": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@mectro/raro-cua"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add mectrojohnny-raro-cua --command npx --arg -y --arg @mectro/raro-cua
```

### Hermes

```yaml
mcp_servers:
  mectrojohnny-raro-cua:
    command: "npx"
    args: ["-y", "@mectro/raro-cua"]
```

### Netclaw

```json
{
  "McpServers": {
    "mectrojohnny-raro-cua": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@mectro/raro-cua"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add mectrojohnny-raro-cua -t stdio -c npx -a -y @mectro/raro-cua
```

### Other

```json
{
  "mcpServers": {
    "mectrojohnny-raro-cua": {
      "command": "npx",
      "args": [
        "-y",
        "@mectro/raro-cua"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-28 (score 31, 0)

- [functional regression] License: fail → unverified
- [functional] Licence: SEE LICENSE IN LICENSE
- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-25 (score 31, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-08-26 (score 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-08-24 (score 0)

First indexed and scored.

## MCP tools (0)

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.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/mectrojohnny-raro-cua/mectro-raro-cua#diagnostics

## Score history

- 2026-09-29: 31
- 2026-09-28: 31
- 2026-09-27: 31
- 2026-09-26: 31
- 2026-09-25: 31
- 2026-09-24: 31
- 2026-09-23: 31
- 2026-09-22: 31
- 2026-09-21: 31
- 2026-09-20: 31
- 2026-09-19: 31
- 2026-09-18: 31
- 2026-09-17: 31
- 2026-09-16: 31
- 2026-09-15: 31
- 2026-09-14: 31
- 2026-09-13: 31
- 2026-09-12: 31
- 2026-09-11: 31
- 2026-09-10: 31
- 2026-09-09: 31
- 2026-09-08: 31
- 2026-09-07: 31
- 2026-09-06: 31
- 2026-09-05: 31
- 2026-09-04: 31
- 2026-09-03: 31
- 2026-09-02: 31
- 2026-09-01: 31
- 2026-08-31: 31

## Common questions

### What is the RaroCUA MCP server?

RaroCUA is an MCP server listed in the public MCP registry as io.github.mectrojohnny/raro-cua. Local macOS Computer Use MCP server with screenshots, AX trees, and app actions. This page covers its npm package (@mectro/raro-cua).

### Is the RaroCUA MCP server safe to use?

RaroCUA scores 31 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 29 September 2026. It declares no install or post-install scripts. 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 RaroCUA MCP server still maintained?

RaroCUA 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.

## Links

- npm package: https://www.npmjs.com/package/@mectro/raro-cua
- Socket report: https://socket.dev/npm/package/@mectro/raro-cua
- Changelog RSS feed: https://verifymcp.io/servers/mectrojohnny-raro-cua/mectro-raro-cua.xml
- Changelog JSON feed: https://verifymcp.io/servers/mectrojohnny-raro-cua/mectro-raro-cua.json
- HTML version of this page: https://verifymcp.io/servers/mectrojohnny-raro-cua/mectro-raro-cua