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.

io.github.gaopengbin/cesium-mcp-dev

NPM · CESIUM-MCP-DEV

CesiumJS API docs, code generation and development tools for IDE AI assistants.

Available components

0 this week 78 Trust /100

Last scanned (3 hours ago)

Scores higher than 58% 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
  • 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
  • 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
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 15 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 274 tokens (~91/item across 3 items; 3 tools + 0 resources), lean.Pass
  • 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 Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 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
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.

  • 5 Nov 26 0
    • Stability: 0.97 → pass security
  • 4 Nov 26 +1

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

  • 3 Nov 26 −1
    • Stability: pass → 0.93 functional
  • 28 Oct 26 0
    • Stability: 0.97 → pass security
  • 27 Oct 26 0
    • Stability: pass → 0.97 functional
  • 24 Oct 26 −5
    • CVE-2023-54404 affects this package: high ▼ security
    • Known CVEs: pass → fail ▼ security
  • 21 Oct 26 0
    • Stability: 0.97 → pass security
  • 20 Oct 26 0
    • Stability: pass → 0.97 functional
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 5 Nov 2026 · Analysed npm/cesium-mcp-dev@1.139.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 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 3 exposed · ~274 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
cesium_api_lookup ~80

查询 Cesium API 文档。输入类名或关键词,返回对应的 API 描述、构造参数、常用方法和示例代码。

NameTypeReqDescription
categorystring–查询类别
querystringyesCesium 类名或关键词,如 "Viewer"、"Entity"、"Color"、"flyTo"

No output schema declared.

No examples provided.

cesium_code_gen ~83

根据自然语言描述生成 Cesium 代码片段。支持常见场景:视图控制、图层加载、Entity 创建、样式设置等。

NameTypeReqDescription
descriptionstringyes用自然语言描述需要实现的功能,如 "创建一个红色的点标记在天安门"
languagestring–代码语言

No output schema declared.

No examples provided.

cesium_entity_builder ~111

交互式构建 Cesium Entity 配置。选择 Entity 类型(point/billboard/label/polyline/polygon/model),返回完整的 Entity JSON 配置和创建代码。

NameTypeReqDescription
colorstring–颜色(CSS 格式)
namestring–Entity 名称
positionobject–位置(经纬度)
sizenumber–尺寸(像素或米)
typestringyesEntity 图形类型

No output schema declared.

No examples provided.

Install

How do I install the io.github.gaopengbin/cesium-mcp-dev server?

io.github.gaopengbin/cesium-mcp-dev runs locally as an npm package, launched with npx -y cesium-mcp-dev. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · cesium-mcp-dev

# add to Claude Code
claude mcp add gaopengbin-cesium-mcp-dev -- npx -y cesium-mcp-dev
Common questions

What is the io.github.gaopengbin/cesium-mcp-dev server?

io.github.gaopengbin/cesium-mcp-dev is listed in the public MCP registry as io.github.gaopengbin/cesium-mcp-dev. CesiumJS API docs, code generation and development tools for IDE AI assistants. This page covers its npm package (cesium-mcp-dev).

Is the io.github.gaopengbin/cesium-mcp-dev server safe to use?

io.github.gaopengbin/cesium-mcp-dev scores 78 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 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 io.github.gaopengbin/cesium-mcp-dev server expose?

io.github.gaopengbin/cesium-mcp-dev exposes 3 tools: cesium_api_lookup, cesium_code_gen, cesium_entity_builder. Their descriptions and schemas cost roughly 274 tokens of context every time the server is loaded.

Is the io.github.gaopengbin/cesium-mcp-dev server still maintained?

io.github.gaopengbin/cesium-mcp-dev 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.gaopengbin/cesium-mcp-dev server under?

io.github.gaopengbin/cesium-mcp-dev declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.