# ai.aquex/stage1 (npm · @aquex/stage1)

Stage1 Inspector — local website capture, evidence views and design comparison

- Trust score: 34/100 (low)
- Change this week: +6
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `@aquex/stage1`: 34/100 (this document), [markdown](https://verifymcp.io/servers/ai-aquex-stage1/aquex-stage1.md), [page](https://verifymcp.io/servers/ai-aquex-stage1/aquex-stage1)

## Channel facts

- Registry: `npm`
- Package: `@aquex/stage1`
- Version: `0.7.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-11-05.

- **Supply Chain Security**: 99/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.
  - 63 of 264 dependencies flagged as unhealthy (1 deprecated).
- **Provenance & Transparency**: 19/100
  - Repository check failed: no source repository is declared.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 2 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 ai.aquex/stage1 MCP server?

ai.aquex/stage1 runs locally as an npm package, launched with npx -y @aquex/stage1 stage1-mcp, plus the required --out, which you supply. The registry lists runner options for this package that are not in this command (they are not ones we reproduce, or they name another package). Check the registry entry before relying on it. 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 ai-aquex-stage1 -- npx -y @aquex/stage1 stage1-mcp
```

The registry lists runner options for this package that are not in this command (they are not ones we reproduce, or they name another package). Check the registry entry before relying on it. Incomplete: the registry marks --out as required and gives no value we can show, so it is not in this command. Add it before you run it.

### Cursor

```json
{
  "mcpServers": {
    "ai-aquex-stage1": {
      "command": "npx",
      "args": [
        "-y",
        "@aquex/stage1",
        "stage1-mcp"
      ]
    }
  }
}
```

The registry lists runner options for this package that are not in this command (they are not ones we reproduce, or they name another package). Check the registry entry before relying on it. Incomplete: the registry marks --out as required and gives no value we can show, so it is not in this command. Add it before you run it.

### VS Code

```json
{
  "servers": {
    "ai-aquex-stage1": {
      "command": "npx",
      "args": [
        "-y",
        "@aquex/stage1",
        "stage1-mcp"
      ]
    }
  }
}
```

The registry lists runner options for this package that are not in this command (they are not ones we reproduce, or they name another package). Check the registry entry before relying on it. Incomplete: the registry marks --out as required and gives no value we can show, so it is not in this command. Add it before you run it.

### Codex

```bash
codex mcp add ai-aquex-stage1 -- npx -y @aquex/stage1 stage1-mcp
```

The registry lists runner options for this package that are not in this command (they are not ones we reproduce, or they name another package). Check the registry entry before relying on it. Incomplete: the registry marks --out as required and gives no value we can show, so it is not in this command. Add it before you run it.

### opencode

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

The registry lists runner options for this package that are not in this command (they are not ones we reproduce, or they name another package). Check the registry entry before relying on it. Incomplete: the registry marks --out as required and gives no value we can show, so it is not in this command. Add it before you run it.

### OpenClaw

```bash
openclaw mcp add ai-aquex-stage1 --command npx --arg -y --arg @aquex/stage1 --arg stage1-mcp
```

The registry lists runner options for this package that are not in this command (they are not ones we reproduce, or they name another package). Check the registry entry before relying on it. Incomplete: the registry marks --out as required and gives no value we can show, so it is not in this command. Add it before you run it.

### Hermes

```yaml
mcp_servers:
  ai-aquex-stage1:
    command: "npx"
    args: ["-y", "@aquex/stage1", "stage1-mcp"]
```

The registry lists runner options for this package that are not in this command (they are not ones we reproduce, or they name another package). Check the registry entry before relying on it. Incomplete: the registry marks --out as required and gives no value we can show, so it is not in this command. Add it before you run it.

### Netclaw

```json
{
  "McpServers": {
    "ai-aquex-stage1": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@aquex/stage1",
        "stage1-mcp"
      ]
    }
  }
}
```

The registry lists runner options for this package that are not in this command (they are not ones we reproduce, or they name another package). Check the registry entry before relying on it. Incomplete: the registry marks --out as required and gives no value we can show, so it is not in this command. Add it before you run it.

### Vellum

```bash
assistant mcp add ai-aquex-stage1 -t stdio -c npx -a -y @aquex/stage1 stage1-mcp
```

The registry lists runner options for this package that are not in this command (they are not ones we reproduce, or they name another package). Check the registry entry before relying on it. Incomplete: the registry marks --out as required and gives no value we can show, so it is not in this command. Add it before you run it.

### Other

```json
{
  "mcpServers": {
    "ai-aquex-stage1": {
      "command": "npx",
      "args": [
        "-y",
        "@aquex/stage1",
        "stage1-mcp"
      ]
    }
  }
}
```

The registry lists runner options for this package that are not in this command (they are not ones we reproduce, or they name another package). Check the registry entry before relying on it. Incomplete: the registry marks --out as required and gives no value we can show, so it is not in this command. Add it before you run it.

## 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-11-02 (score 34, +6)

- [security improvement] CVE-2023-54404 no longer affects this package
- [security improvement] CVE-2026-111767 no longer affects this package
- [security improvement] CVE-2026-111768 no longer affects this package
- [security improvement] CVE-2026-111771 no longer affects this package
- [security improvement] CVE-2026-111769 no longer affects this package
- [security improvement] Known CVEs: fail → pass
- [functional] Package version: 0.6.0 → 0.7.0

### 2026-10-24 (score 28, 0)

- [security regression] CVE-2023-54404 affects this package: high

### 2026-10-21 (score 28, −6)

- [security regression] CVE-2026-111771 affects this package: high
- [security regression] CVE-2026-111768 affects this package: high
- [security regression] CVE-2026-111769 affects this package: high
- [security regression] CVE-2026-111767 affects this package: high
- [security regression] Known CVEs: pass → fail

### 2026-10-14 (score 34, 0)

- [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.
- [functional] 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.

### 2026-10-09 (score 34)

First indexed and scored.

## MCP tools (0)

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/ai-aquex-stage1/aquex-stage1#diagnostics

## Score history

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

## Common questions

### What is the ai.aquex/stage1 MCP server?

ai.aquex/stage1 is an MCP server listed in the public MCP registry as ai.aquex/stage1. Stage1 Inspector, local website capture, evidence views and design comparison. This page covers its npm package (@aquex/stage1).

### Is the ai.aquex/stage1 MCP server safe to use?

ai.aquex/stage1 scores 34 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 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 ai.aquex/stage1 MCP server still maintained?

ai.aquex/stage1 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 ai.aquex/stage1 MCP server under?

ai.aquex/stage1 declares the Apache-2.0 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 ai.aquex/stage1 MCP server?

VerifyMCP ran 8 checks on ai.aquex/stage1, covering Malware scan, Known CVEs, Install scripts, Dependency health and 4 more. 6 items could not be completed, a gap on our side rather than a finding about ai.aquex/stage1: Security disclosure, Schema quality, Stability, Tool coverage and 2 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/@aquex/stage1
- Socket report: https://socket.dev/npm/package/@aquex/stage1
- Website: https://aquex.ai/products/stage1
- Changelog RSS feed: https://verifymcp.io/servers/ai-aquex-stage1/aquex-stage1.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-aquex-stage1/aquex-stage1/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/ai-aquex-stage1/aquex-stage1.json
- HTML version of this page: https://verifymcp.io/servers/ai-aquex-stage1/aquex-stage1