CityEngine Cloud
OCI · GHCR.IO/CGAJS/CITYENGINE-MCP
Text-to-3D city buildings: natural language to CGA rules to rendered glTF models.
Available components
Last scanned (13 hours ago)
Scores higher than 35% of OCI servers
Category Design and Media
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 Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency32
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 7 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability62
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 961 tokens (~160/item across 6 items; 6 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 Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (17% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Checks we ran (12)
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (4)
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.
- Malware scan in Supply Chain Security (scores 0 for this)No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
- Known CVEs in Supply Chain Security (scores 0 for this)Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
- Install scripts in Supply Chain Security (scores 0 for this)Install-script risk not yet assessed.
- Dependency health in Supply Chain Security (scores 0 for this)Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
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 →
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.
- 21 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Nov 26 33
First indexed and scored.
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 oci/ghcr.io/cgajs/cityengine-mcp@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
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 →
generate_cga ~181
自然语言一句话 → NL2CGA → CGA 规则源码(不渲染,同步返回)。 两种模式二选一: 1. text:自然语言描述,如「三层小楼,坡屋顶,底层商铺」。 2. base_cga + instruction:在既有 CGA 上按指令修改(如「把立面材质改成红砖」)。 LLM 兜底模式最长约 90s,属正常现象。 Returns: cga_source(可喂给 parse_cga / generate_model 的 cga_edit 回传)、 engine_path(self/kimi_fallback/hybrid)、warnings、usage。
| Name | Type | Req | Description |
|---|---|---|---|
| base_cga | – | – | – |
| instruction | – | – | – |
| text | – | – | – |
No output schema declared.
No examples provided.
generate_model ~207
自然语言一句话 → 直接生成三维模型(NL2CGA + 引擎解析一键串联)。 两种模式二选一: 1. text:自然语言描述,如「生成一栋 12 层现代玻璃幕墙办公楼」。 2. base_cga + instruction:回传既有 CGA + 修改指令,二次生成再出模型。 Args:(其余参数同 parse_cga) Returns: cga_source(供后续 cga_edit 回传)、模型统计、glb 本地路径、 签名下载地址、sha256、usage、warnings。
| Name | Type | Req | Description |
|---|---|---|---|
| attributes | – | – | – |
| base_cga | – | – | – |
| download_glb | boolean | – | – |
| initial_shape | – | – | – |
| instruction | – | – | – |
| output_dir | – | – | – |
| seed | – | – | – |
| text | – | – | – |
| timeout_s | number | – | – |
No output schema declared.
No examples provided.
get_demo ~114
查看某个官网 demo 案例的详情:属性面板定义、材质数、节点数、引擎耗时。 注意:demo 的 CGA 源码属付费内容(官网商城),本工具返回公开快照信息 (属性 schema / 规模 / 引擎指标),适合做参数设计参考。 Args: demo_id: list_demos 返回的 id,如 building-glass-20260928。
| Name | Type | Req | Description |
|---|---|---|---|
| demo_id | string | yes | – |
No output schema declared.
No examples provided.
get_quota ~32
查询当前 API key 的套餐、额度用量(generate/NL2CGA)与限流参数。
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_demos ~54
列出 CityEngine 官网首页的 demo 案例(id、名称、引擎、来源日期、属性个数)。 返回条目可传给 get_demo 查看属性面板细节。
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
parse_cga ~310
用 CityEngine 引擎解析 CGA 规则源码,生成三维模型(glTF/glb)。 Args: cga_source: CGA 规则源码全文(手写或 generate_cga 的产物)。 attributes: CGA attr 覆盖,如 {"height": 30};键必须在规则的 attr 声明内。 initial_shape: 初始地块多边形 {"type":"Polygon","pts":[[x,z],...]},米制; 缺省用 30m x 20m 调试地块。 seed: 随机种子,固定后可复现结果。 download_glb: 是否把 glb 下载到本地(默认 True)。 output_dir: glb 落盘目录(默认环境变量 CITYENGINE_OUTPUT_DIR 或当前目录下 cityengine_mcp_output/)。 timeout_s: 轮询 job 的最长秒数(上限 300)。 Returns: job_id、模型统计(nodes/vertices/triangles/textures_embedded)、glb 本地路径、 签名下载地址(24h 有效)、sha256、计费用量、告警列表。
| Name | Type | Req | Description |
|---|---|---|---|
| attributes | – | – | – |
| cga_source | string | yes | – |
| download_glb | boolean | – | – |
| initial_shape | – | – | – |
| output_dir | – | – | – |
| seed | – | – | – |
| timeout_s | number | – | – |
No output schema declared.
No examples provided.
How do I install the CityEngine Cloud MCP server?
CityEngine Cloud runs locally as a container image, launched with docker run --rm -i -e CITYENGINE_API_KEY -e CITYENGINE_GATEWAY_BASE ghcr.io/cgajs/cityengine-mcp:0.1.0. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/cgajs/cityengine-mcp
claude mcp add cgajs-cityengine-mcp -- docker run --rm -i -e CITYENGINE_API_KEY -e CITYENGINE_GATEWAY_BASE ghcr.io/cgajs/cityengine-mcp:0.1.0
This image reads CITYENGINE_API_KEY and CITYENGINE_GATEWAY_BASE. Set them in your client's env block for this server; docker run -e passes each one through to the container.
What is the CityEngine Cloud MCP server?
CityEngine Cloud is an MCP server listed in the public MCP registry as io.github.cgajs/cityengine-mcp. Text-to-3D city buildings: natural language to CGA rules to rendered glTF models. This page covers its container image (ghcr.io/cgajs/cityengine-mcp).
Is the CityEngine Cloud MCP server safe to use?
CityEngine Cloud scores 37 out of 100 on VerifyMCP. 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 CityEngine Cloud MCP server expose?
CityEngine Cloud exposes 6 tools: parse_cga, generate_cga, generate_model, list_demos, get_demo, get_quota. Their descriptions and schemas cost roughly 898 tokens of context every time the server is loaded.
Is the CityEngine Cloud MCP server still maintained?
CityEngine Cloud 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 did VerifyMCP test on the CityEngine Cloud MCP server?
VerifyMCP ran 12 checks on CityEngine Cloud, covering Source repository, Provenance, License, Maintenance and 8 more. 4 items could not be completed, a gap on our side rather than a finding about CityEngine Cloud: Malware scan, Known CVEs, Install scripts and Dependency health. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a container image, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.