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.

CloudArch

NPM · @CLOUD-ARCH/MCP-SERVER

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

0 this week 71 Trust /100

Last scanned (21 hours ago)

Scores higher than 42% of npm servers

Category Developer Tools

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 Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 31 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
  • Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 83 days ago).Pass
  • Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability68
  • AI-judged instruction clarity (good).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 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. See how to fix → Fail
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 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.

  • 19 Nov 26 +1
    • Stability: 0.97 → pass security
  • 18 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 12 Nov 26 +1
    • Stability: 0.97 → pass security
  • 10 Nov 26 +1

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

  • 9 Nov 26 −2
    • Stability: pass → 0.90 functional
  • 3 Nov 26 +1
    • Stability: 0.97 → pass security
  • 2 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 27 Oct 26 +1
    • Stability: 0.97 → pass security
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 21 Nov 2026 · Analysed npm/@cloud-arch/mcp-server@0.2.2

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 93 packages
Packages resolved 93
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~843 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
create_diagram ~484

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{}).

NameTypeReqDescription
codestringyesCloudArch 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…
descriptionstringyesNatural language description of the system architecture to visualize. Be specific about components, connections, and data flows.
isPublicboolean–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.
namestring–Name for the diagram. Auto-generated if omitted.
readmestring–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…
slugstring–URL slug for the diagram (lowercase, hyphens). Auto-generated if omitted.
tagsarray–Tags for categorization

No output schema declared.

No examples provided.

delete_diagram ~34

Delete an existing CloudArch diagram by its ID.

NameTypeReqDescription
idstringyesThe diagram ID (UUID) to delete

No output schema declared.

No examples provided.

get_script_template ~38

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_diagrams ~24

List your CloudArch diagrams

NameTypeReqDescription
limitnumber–Max results

No output schema declared.

No examples provided.

update_diagram ~263

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.

NameTypeReqDescription
codestring–Updated script code
descriptionstring–Updated description
idstring–The diagram ID (UUID) to update. Either id or slug must be provided.
isPublicboolean–Updated visibility
namestring–Updated name
readmestring–Updated Markdown README. Same authoring guide as on create_diagram: ## Overview / ## Components / ## Scenarios / ## Tradeoffs / ## References, ~150-400 words, [LABEL] prefixes, no emojis. Use :concep…
slugstring–The diagram slug to update. Either id or slug must be provided. If slug is given, the ID is resolved automatically.
tagsarray–Updated tags

No output schema declared.

No examples provided.

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.

npm · @cloud-arch/mcp-server

# add to Claude Code
claude mcp add ru-cloud-arch-cloudarch -- npx -y @cloud-arch/mcp-server
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 71 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 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.

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

What did VerifyMCP test on the CloudArch MCP server?

VerifyMCP ran 15 checks on CloudArch, 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 CloudArch: Security disclosure. 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.