# CloudArch (npm · @cloud-arch/mcp-server)

Create and update live animated architecture diagrams on CloudArch from a prompt or script.

- Trust score: 75/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-25

## Components

- npm · `@cloud-arch/mcp-server`: 75/100 (this document), [markdown](https://verifymcp.io/servers/ru-cloud-arch-cloudarch/cloud-arch-mcp-server.md), [page](https://verifymcp.io/servers/ru-cloud-arch-cloudarch/cloud-arch-mcp-server)

## Channel facts

- Registry: `npm`
- Package: `@cloud-arch/mcp-server`
- Version: `0.2.2`
- 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-25.

- **Supply Chain Security**: 98/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.
  - 31 of 96 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 19/100
  - Repository check failed: the declared repository URL returned HTTP 404.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 26 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 68/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 843 tokens (~168/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 90/100
  - Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_diagram" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

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

CloudArch runs locally as an npm package, launched with npx -y @cloud-arch/mcp-server. 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 ru-cloud-arch-cloudarch -- npx -y @cloud-arch/mcp-server
```

### Cursor

```json
{
  "mcpServers": {
    "ru-cloud-arch-cloudarch": {
      "command": "npx",
      "args": [
        "-y",
        "@cloud-arch/mcp-server"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ru-cloud-arch-cloudarch": {
      "command": "npx",
      "args": [
        "-y",
        "@cloud-arch/mcp-server"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add ru-cloud-arch-cloudarch -- npx -y @cloud-arch/mcp-server
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ru-cloud-arch-cloudarch": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@cloud-arch/mcp-server"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ru-cloud-arch-cloudarch --command npx --arg -y --arg @cloud-arch/mcp-server
```

### Hermes

```yaml
mcp_servers:
  ru-cloud-arch-cloudarch:
    command: "npx"
    args: ["-y", "@cloud-arch/mcp-server"]
```

### Netclaw

```json
{
  "McpServers": {
    "ru-cloud-arch-cloudarch": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@cloud-arch/mcp-server"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add ru-cloud-arch-cloudarch -t stdio -c npx -a -y @cloud-arch/mcp-server
```

### Other

```json
{
  "mcpServers": {
    "ru-cloud-arch-cloudarch": {
      "command": "npx",
      "args": [
        "-y",
        "@cloud-arch/mcp-server"
      ]
    }
  }
}
```

## 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-25 (score 75, +1)

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

### 2026-09-23 (score 74, +1)

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

### 2026-09-21 (score 73, +1)

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

### 2026-09-19 (score 72, +1)

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

### 2026-09-17 (score 71, +1)

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

### 2026-09-15 (score 70, +1)

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

### 2026-09-12 (score 69, +1)

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

### 2026-09-10 (score 68, +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.

## MCP tools (5)

### `create_diagram` (~484 tokens)

Create an interactive architecture diagram on CloudArch. Provide a description of the system and get back a URL to the live animated diagram. ALWAYS pass `readme` as well — a Markdown narrative with Overview / Components / Scenarios / Tradeoffs sections — so the viewer's README pane has substance. Call get_script_template for the full README authoring guide and :concept{} / :case{} inline directive syntax (standalone leaf form: ::concept{} / ::case{}).

Input parameters:

- `code` (string, required): CloudArch script code — REQUIRED. Call get_script_template first: it carries the layout rules (.newRow() every 3-4 nodes), the scenario API (.scenario/.showError/.flashError), and the architectural p…
- `description` (string, required): Natural language description of the system architecture to visualize. Be specific about components, connections, and data flows.
- `isPublic` (boolean): Whether the diagram is publicly visible. Defaults to FALSE: a diagram built from someone's codebase should not land in the public gallery unless that was asked for. Pass true deliberately.
- `name` (string): Name for the diagram. Auto-generated if omitted.
- `readme` (string): Markdown README for the diagram. Strongly recommended — without it the viewer's README pane shows an empty card and the educational value is lost. Target ~150-400 words. Recommended sections: ## Over…
- `slug` (string): URL slug for the diagram (lowercase, hyphens). Auto-generated if omitted.
- `tags` (array): Tags for categorization

### `list_diagrams` (~24 tokens)

List your CloudArch diagrams

Input parameters:

- `limit` (number): Max results

### `update_diagram` (~263 tokens)

Update an existing CloudArch diagram. You can change the code, name, description, or other fields. Provide either id (UUID) or slug to identify the diagram.

Input parameters:

- `code` (string): Updated script code
- `description` (string): Updated description
- `id` (string): The diagram ID (UUID) to update. Either id or slug must be provided.
- `isPublic` (boolean): Updated visibility
- `name` (string): Updated name
- `readme` (string): Updated Markdown README. Same authoring guide as on create_diagram: ## Overview / ## Components / ## Scenarios / ## Tradeoffs / ## References, ~150-400 words, [LABEL] prefixes, no emojis. Use :concep…
- `slug` (string): The diagram slug to update. Either id or slug must be provided. If slug is given, the ID is resolved automatically.
- `tags` (array): Updated tags

### `delete_diagram` (~34 tokens)

Delete an existing CloudArch diagram by its ID.

Input parameters:

- `id` (string, required): The diagram ID (UUID) to delete

### `get_script_template` (~38 tokens)

Get the CloudArch script generation prompt/template. Use this to understand how to write topology scripts, then call create_diagram with the generated code.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/ru-cloud-arch-cloudarch/cloud-arch-mcp-server#diagnostics

## Score history

- 2026-09-25: 75
- 2026-09-24: 74
- 2026-09-23: 74
- 2026-09-22: 73
- 2026-09-21: 73
- 2026-09-20: 72
- 2026-09-19: 72
- 2026-09-18: 71
- 2026-09-17: 71
- 2026-09-16: 70
- 2026-09-15: 70
- 2026-09-14: 69
- 2026-09-13: 69
- 2026-09-12: 69
- 2026-09-11: 68
- 2026-09-10: 68
- 2026-09-09: 67
- 2026-09-08: 67
- 2026-09-07: 66
- 2026-09-06: 66
- 2026-09-05: 62
- 2026-09-04: 62
- 2026-09-03: 62
- 2026-09-02: 62
- 2026-09-01: 62
- 2026-08-31: 62
- 2026-08-30: 62
- 2026-08-29: 47

## Common questions

### What is the CloudArch MCP server?

CloudArch is an MCP server listed in the public MCP registry as ru.cloud-arch/cloudarch. Create and update live animated architecture diagrams on CloudArch from a prompt or script. This page covers its npm package (@cloud-arch/mcp-server).

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

CloudArch scores 75 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 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.

### What tools does the CloudArch MCP server expose?

CloudArch exposes 5 tools: create_diagram, list_diagrams, update_diagram, delete_diagram, get_script_template. Their descriptions and schemas cost roughly 843 tokens of context every time the server is loaded.

### Is the CloudArch MCP server still maintained?

CloudArch is still listed as active in the MCP registry. We last reached this channel on 25 September 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 CloudArch MCP server under?

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

## Links

- npm package: https://www.npmjs.com/package/@cloud-arch/mcp-server
- Socket report: https://socket.dev/npm/package/@cloud-arch/mcp-server
- Website: https://web.cloud-arch.ru/
- Changelog RSS feed: https://verifymcp.io/servers/ru-cloud-arch-cloudarch/cloud-arch-mcp-server.xml
- Changelog JSON feed: https://verifymcp.io/servers/ru-cloud-arch-cloudarch/cloud-arch-mcp-server.json
- HTML version of this page: https://verifymcp.io/servers/ru-cloud-arch-cloudarch/cloud-arch-mcp-server