# io.github.NousVigil/archstone (npm · @archstone/cli)

Compile your own business capabilities from declarative YAML and serve them as MCP tools.

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

## Components

- npm · `@archstone/cli`: 50/100 (this document), [markdown](https://verifymcp.io/servers/nousvigil-archstone/archstone-cli.md), [page](https://verifymcp.io/servers/nousvigil-archstone/archstone-cli)

## Channel facts

- Registry: `npm`
- Package: `@archstone/cli`
- Version: `0.35.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.
  - 34 of 118 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to NousVigil/archstone).
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 13 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **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 io.github.NousVigil/archstone MCP server?

io.github.NousVigil/archstone runs locally as an npm package, launched with npx -y @archstone/cli serve, plus the required manifest_dir, which you supply. 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 nousvigil-archstone -- npx -y @archstone/cli serve
```

Incomplete: the registry marks manifest_dir 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": {
    "nousvigil-archstone": {
      "command": "npx",
      "args": [
        "-y",
        "@archstone/cli",
        "serve"
      ]
    }
  }
}
```

Incomplete: the registry marks manifest_dir 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": {
    "nousvigil-archstone": {
      "command": "npx",
      "args": [
        "-y",
        "@archstone/cli",
        "serve"
      ]
    }
  }
}
```

Incomplete: the registry marks manifest_dir 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 nousvigil-archstone -- npx -y @archstone/cli serve
```

Incomplete: the registry marks manifest_dir 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": {
    "nousvigil-archstone": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@archstone/cli",
        "serve"
      ],
      "enabled": true
    }
  }
}
```

Incomplete: the registry marks manifest_dir 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 nousvigil-archstone --command npx --arg -y --arg @archstone/cli --arg serve
```

Incomplete: the registry marks manifest_dir 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:
  nousvigil-archstone:
    command: "npx"
    args: ["-y", "@archstone/cli", "serve"]
```

Incomplete: the registry marks manifest_dir 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": {
    "nousvigil-archstone": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@archstone/cli",
        "serve"
      ]
    }
  }
}
```

Incomplete: the registry marks manifest_dir 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 nousvigil-archstone -t stdio -c npx -a -y @archstone/cli serve
```

Incomplete: the registry marks manifest_dir 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": {
    "nousvigil-archstone": {
      "command": "npx",
      "args": [
        "-y",
        "@archstone/cli",
        "serve"
      ]
    }
  }
}
```

Incomplete: the registry marks manifest_dir 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-10-25 (score 50, +1)

- [functional improvement] Security disclosure: unverified → pass

### 2026-10-24 (score 49, −1)

- [functional regression] Security disclosure: pass → unverified

### 2026-10-23 (score 50, +11)

- [security improvement] Known CVEs: 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.
- [functional improvement] Dependency health: unverified → 0.88
- [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-22 (score 39, −11)

- [security regression] Known CVEs: 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.
- [functional regression] Dependency health: 0.88 → unverified
- [functional] 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: 0.34.0 → 0.35.0

### 2026-10-15 (score 50, 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-12 (score 50, 0)

- [functional] Package version: 0.29.0 → 0.34.0

### 2026-10-08 (score 50)

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/nousvigil-archstone/archstone-cli#diagnostics

## Score history

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

## Common questions

### What is the io.github.NousVigil/archstone MCP server?

io.github.NousVigil/archstone is an MCP server listed in the public MCP registry as io.github.NousVigil/archstone. Compile your own business capabilities from declarative YAML and serve them as MCP tools. This page covers its npm package (@archstone/cli).

### Is the io.github.NousVigil/archstone MCP server safe to use?

io.github.NousVigil/archstone scores 50 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. 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 io.github.NousVigil/archstone MCP server still maintained?

io.github.NousVigil/archstone 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 io.github.NousVigil/archstone MCP server under?

io.github.NousVigil/archstone 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 io.github.NousVigil/archstone MCP server?

VerifyMCP ran 9 checks on io.github.NousVigil/archstone, covering Malware scan, Known CVEs, Install scripts, Dependency health and 5 more. 5 items could not be completed, a gap on our side rather than a finding about io.github.NousVigil/archstone: Schema quality, Stability, Tool coverage, Tool safety and 1 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/@archstone/cli
- Socket report: https://socket.dev/npm/package/@archstone/cli
- Repository: https://github.com/NousVigil/archstone
- Website: https://archstone.dev/
- Changelog RSS feed: https://verifymcp.io/servers/nousvigil-archstone/archstone-cli.xml
- Changelog JSON feed: https://verifymcp.io/servers/nousvigil-archstone/archstone-cli/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/nousvigil-archstone/archstone-cli.json
- HTML version of this page: https://verifymcp.io/servers/nousvigil-archstone/archstone-cli