CloudArch Codeflow
NPM · @CLOUD-ARCH/MCP-CODEFLOW · SCANNED SEP 20
Turn a TypeScript codebase into a live animated call-flow diagram on CloudArch.
Available components
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 32 of 106 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 21 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability74
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 524 tokens (~262/item across 2 items; 2 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 Management73
- Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 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
How do I install the CloudArch Codeflow MCP server?
CloudArch Codeflow runs locally as an npm package, launched with npx -y @cloud-arch/mcp-codeflow. 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-codeflow
claude mcp add ru-cloud-arch-cloudarch-codeflow -- npx -y @cloud-arch/mcp-codeflow
{
"mcpServers": {
"ru-cloud-arch-cloudarch-codeflow": {
"command": "npx",
"args": [
"-y",
"@cloud-arch/mcp-codeflow"
]
}
}
} {
"servers": {
"ru-cloud-arch-cloudarch-codeflow": {
"command": "npx",
"args": [
"-y",
"@cloud-arch/mcp-codeflow"
]
}
}
} codex mcp add ru-cloud-arch-cloudarch-codeflow -- npx -y @cloud-arch/mcp-codeflow
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ru-cloud-arch-cloudarch-codeflow": {
"type": "local",
"command": [
"npx",
"-y",
"@cloud-arch/mcp-codeflow"
],
"enabled": true
}
}
} openclaw mcp add ru-cloud-arch-cloudarch-codeflow --command npx --arg -y --arg @cloud-arch/mcp-codeflow
mcp_servers:
ru-cloud-arch-cloudarch-codeflow:
command: "npx"
args: ["-y", "@cloud-arch/mcp-codeflow"] {
"McpServers": {
"ru-cloud-arch-cloudarch-codeflow": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@cloud-arch/mcp-codeflow"
]
}
}
} assistant mcp add ru-cloud-arch-cloudarch-codeflow -t stdio -c npx -a -y @cloud-arch/mcp-codeflow
{
"mcpServers": {
"ru-cloud-arch-cloudarch-codeflow": {
"command": "npx",
"args": [
"-y",
"@cloud-arch/mcp-codeflow"
]
}
}
} 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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +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.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Sept 26 +3
- Stability: unverified → 0.27 ▲ functional
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 20 Sept 2026 · Analysed npm/@cloud-arch/mcp-codeflow@0.1.1
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 →
Dependencies 106 packages
| Packages resolved | 106 |
|---|---|
| Stale | 32 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
analyze_codeflow ~348
Analyse a TypeScript project and visualise the call flow from a given entry method/function as an animated CloudArch diagram. Walks the AST, builds a unified call graph (class methods AND module-level functions), reachability-traces from the entry, lays it out by architectural layer (controllers/services/repos/infra) detected from file paths, and publishes it. Detects Promise.all (rendered as parallel block) and try/catch (catch path rendered as showError). Returns the diagram URL. Out of scope for now: if/else branching, super/inheritance, decorator-based DI, non-TS languages.
| Name | Type | Req | Description |
|---|---|---|---|
| additionalEntries | array | – | Extra entries (same syntax as `entry`) rendered as additional scenarios on the same diagram. Use this when you want to compare or co-visualise several flows that share infrastructure. |
| entry | string | yes | Entry point. Accepts: 'ClassName.methodName' (single class method), 'ClassName.*' (all public methods of class as scenarios), 'moduleName:funcName' (single function), 'moduleName:*' (all functions of… |
| isPublic | boolean | – | Whether the diagram is publicly visible. Defaults to false (your own code is usually private). |
| name | string | – | Name for the published diagram. Auto-generated from entry if omitted. |
| projectPath | string | yes | Absolute path to a directory containing tsconfig.json (the root of the TS project to analyse). |
| slug | string | – | URL slug for the diagram. Auto-generated if omitted. |
No output schema declared.
No examples provided.
list_entry_candidates ~176
Suggest analyse-able entry points for a TypeScript project. Scans all classes and module-level functions, ranks them by 'how likely is this a flow start' — controllers/routes score highest, repos/infra lowest, action-style names (create*/update*/process*/handle*/...) get a bump, and entries with a richer reachable subgraph beat leaves. Use this BEFORE `analyze_codeflow` when you don't know the project's structure — pick a candidate from the result and pass its `entry` field to the analyser. Returns a ranked list with file paths and reasons.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max candidates to return (default 20). Lower for a quick overview, higher to see everything. |
| projectPath | string | yes | Absolute path to a directory containing tsconfig.json (the root of the TS project to inspect). |
No output schema declared.
No examples provided.
What is the CloudArch Codeflow MCP server?
CloudArch Codeflow is an MCP server listed in the public MCP registry as ru.cloud-arch/cloudarch-codeflow. Turn a TypeScript codebase into a live animated call-flow diagram on CloudArch. This page covers its npm package (@cloud-arch/mcp-codeflow).
Is the CloudArch Codeflow MCP server safe to use?
CloudArch Codeflow scores 75 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 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 Codeflow MCP server expose?
CloudArch Codeflow exposes 2 tools: analyze_codeflow, list_entry_candidates. Their descriptions and schemas cost roughly 524 tokens of context every time the server is loaded.
Is the CloudArch Codeflow MCP server still maintained?
CloudArch Codeflow is still listed as active in the MCP registry. We last reached this channel on 20 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 Codeflow MCP server under?
CloudArch Codeflow declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.