vibe3d
NPM · @VIBEBYTE/VIBE3D-MCP
Edit and render 3D scenes over MCP: rooms, nodes, materials, cameras, and snapshots.
Available components
Last scanned (7 hours ago)
Scores higher than 81% of npm 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 Security100
- 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
- 0 of 1 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to vibebytes/vibe3d). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 1 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability70
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 3675 tokens (~216/item across 17 items; 17 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 Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 96% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 17 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 18 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
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.
- 4 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 3 Nov 26 0
- Malware scan: unverified → pass ▲ security
- Package version: 0.2.13 → 0.2.14 functional
- 2 Nov 26 −14
- Malware scan: pass → unverified ▼ security
- Known CVEs: pass → unverified ▼ security
- Dependency health: 1.00 → unverified ▼ functional
- Package version: 0.2.10 → 0.2.13 functional
- Package version: 0.2.10 → 0.2.12 functional
- 30 Oct 26 +2
- Security disclosure: unverified → pass ▲ functional
- 29 Oct 26 +27
- Stability: 0.00 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Known CVEs: unverified → pass ▲ security
- Source repository: fail → pass ▲ security
- Provenance: fail → pass ▲ security
- The attested source repository moved: vibebytes/vibe3d security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- Dependency health: unverified → 1.00 ▲ functional
- Package version: 0.2.8 → 0.2.10 functional
- Package version: 0.2.8 → 0.2.9 functional
- 28 Oct 26 53
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 5 Nov 2026 · Analysed npm/@vibebyte/vibe3d-mcp@0.2.14
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | vibebytes/vibe3d |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/vibebytes/vibe3d/.github/workflows/publish-release.yml@refs/tags/v0.2.14 |
| Rekor log index | 3674708164 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:016675f87a683a0db0c1013ddcf598d0476bd7d02bcc3345a4e04df42d57e2dc2be79311e3021aaebc2d40d62e7ebff4876c0ce6737098d13a2a0f7c4 |
Background: How many MCP packages publish verified provenance →
Dependencies 1 package
| Packages resolved | 1 |
|---|---|
| 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 →
vibe3d_animation ~197
[animation] 程序化动画：定义轨道 / 播放 / 停止 / 清除 / 批量摆姿势 / 人形步态｜op: define play stop clear pose gait｜必填见 params 描述，字段见 vibe3d_help {tool, op}
| Name | Type | Req | Description |
|---|---|---|---|
| op | string | yes | animation 下的 op；每个 op 的参数字段用 vibe3d_help {tool, op} 查 |
| params | object | – | op 与必填字段：define{node_id,clip} play{node_id} stop{node_id} clear{node_id} pose{targets} gait{node_id,style}。参数可平铺在顶层（顶层优先），省略 params 时取其顶层字段 |
| room_id | string | – | 省略用默认房间；多房间/多聊天并行必传 |
No output schema declared.
No examples provided.
vibe3d_apply_ops ~468
[apply_ops] 原子批量 op（仅用于跨节点依赖；日常请用专用工具）｜嵌套载荷包在同名字段 {op:"node.create",node:{…}} / {op:"env.set",env:{…}}，不能平铺到 op 顶层（会校验失败）；ops 传数组不是 JSON 字符串。逐条操作请用专用工具
| Name | Type | Req | Description |
|---|---|---|---|
| ops | array | yes | 按顺序原子执行；每个元素是 {op:"名字", ...字段}。复合载荷要包在同名字段里，不能平铺在 op 顶层：node.create 传 {op,node:{…}}、env.set 传 {op,env:{…}}、stage.set 传 {op,stage:{…}}、camera.set 传 {op,camera:{…}}、fx.create 传 {op,fx:{…}}。op 与顶层字段：nod… |
| room_id | string | – | 省略则用会话默认房间；多房间或多聊天并行时必须显式传 |
No output schema declared.
No examples provided.
vibe3d_asset ~167
[asset] 资产：解析 glTF / 上传贴图模型 / 列表 / 删除｜op: [read] inspect list；[write] put delete｜必填见 params 描述，字段见 vibe3d_help {tool, op}
| Name | Type | Req | Description |
|---|---|---|---|
| op | string | yes | asset 下的 op；每个 op 的参数字段用 vibe3d_help {tool, op} 查 |
| params | object | – | op 与必填字段：inspect{src} put{src} list delete{sha}。参数可平铺在顶层（顶层优先），省略 params 时取其顶层字段 |
| room_id | string | – | 省略用默认房间；多房间/多聊天并行必传 |
No output schema declared.
No examples provided.
vibe3d_camera ~204
[camera] 机位：设置 / 保存命名机位 / 删除 / 像素投影与反投影｜op: [read] project unproject；[write] set save delete｜必填见 params 描述，字段见 vibe3d_help {tool, op}｜set 平铺 p/target/fov，勿包成 camera:{…}；save 用命名机位
| Name | Type | Req | Description |
|---|---|---|---|
| op | string | yes | camera 下的 op；每个 op 的参数字段用 vibe3d_help {tool, op} 查 |
| params | object | – | op 与必填字段：set save{name} delete{name} project{points} unproject{points}。参数可平铺在顶层（顶层优先），省略 params 时取其顶层字段 |
| room_id | string | – | 省略用默认房间；多房间/多聊天并行必传 |
No output schema declared.
No examples provided.
vibe3d_export_glb ~112
[export_glb] 导出 GLB（任务制，用 vibe3d_job 查进度）｜拿到 jobId 后轮询 vibe3d_job.get 到 state=done（失败看 error）
| Name | Type | Req | Description |
|---|---|---|---|
| include | array | – | 额外带上相机 / 灯光；默认不带 |
| node_ids | array | – | 只导出这些节点（含子树）；省略则导出整场景 |
| room_id | string | – | – |
No output schema declared.
No examples provided.
vibe3d_fx ~164
[fx] 特效：粒子或光柱，建 / 删｜op: create delete｜必填见 params 描述，字段见 vibe3d_help {tool, op}｜id 由服务端生成，不要复用已有 id
| Name | Type | Req | Description |
|---|---|---|---|
| op | string | yes | fx 下的 op；每个 op 的参数字段用 vibe3d_help {tool, op} 查 |
| params | object | – | op 与必填字段：create{type} delete{fx_id}。参数可平铺在顶层（顶层优先），省略 params 时取其顶层字段 |
| room_id | string | – | 省略用默认房间；多房间/多聊天并行必传 |
No output schema declared.
No examples provided.
vibe3d_help ~92
查参数契约：给 tool(+op) 返回该 op 的参数字段/必填/枚举/错误码与示例；不给 tool 则列出全部工具与 op
| Name | Type | Req | Description |
|---|---|---|---|
| op | string | – | 该工具下的 op；省略则返回该工具全部 op |
| tool | string | – | 工具名；省略则列出全部工具与 op |
No output schema declared.
No examples provided.
vibe3d_job ~159
[job] 导出任务：查询 / 列表 / 取消｜op: [read] get list；[write] cancel｜必填见 params 描述，字段见 vibe3d_help {tool, op}
| Name | Type | Req | Description |
|---|---|---|---|
| op | string | yes | job 下的 op；每个 op 的参数字段用 vibe3d_help {tool, op} 查 |
| params | object | – | op 与必填字段：get{job_id} list cancel{job_id}。参数可平铺在顶层（顶层优先），省略 params 时取其顶层字段 |
| room_id | string | – | 省略用默认房间；多房间/多聊天并行必传 |
No output schema declared.
No examples provided.
vibe3d_material ~242
[material] 材质：按预设建 / 局部改 / 贴图与 UV / 批量指派｜op: create patch map assign｜必填见 params 描述，字段见 vibe3d_help {tool, op}｜create 收 {preset}，id 由服务端生成；preset 任意描述词都收（如 matte-white 会归一到 concrete + 浅色），原名回读在 preset/presetNote；patch 用 baseColor（也接受 color 别名）/metalness/roughness/emissive/opacity
| Name | Type | Req | Description |
|---|---|---|---|
| op | string | yes | material 下的 op；每个 op 的参数字段用 vibe3d_help {tool, op} 查 |
| params | object | – | op 与必填字段：create patch{material_id,patch} map{material_id} assign{material_id}。参数可平铺在顶层（顶层优先），省略 params 时取其顶层字段 |
| room_id | string | – | 省略用默认房间；多房间/多聊天并行必传 |
No output schema declared.
No examples provided.
vibe3d_mesh ~239
[mesh] 网格构造：布尔 / 管体 / 背板 / 车削 / 有机体 / 倒角 / 树 / 人体 / 贴花｜op: boolean tube backdrop lathe organic bevel tree mannequin decal｜必填见 params 描述，字段见 vibe3d_help {tool, op}｜decal 用真字形/图片；color 用 [r,g,b,a] 或 '#RRGGBB'
| Name | Type | Req | Description |
|---|---|---|---|
| op | string | yes | mesh 下的 op；每个 op 的参数字段用 vibe3d_help {tool, op} 查 |
| params | object | – | op 与必填字段：boolean{target,tool} tube{points,radius} backdrop lathe{profile} organic{radius,seed} bevel{size,radius} tree{height,spread,levels,seed} mannequin decal。参数可平铺在顶层（顶层优先），省略 params 时取其顶层字段 |
| room_id | string | – | 省略用默认房间；多房间/多聊天并行必传 |
No output schema declared.
No examples provided.
vibe3d_node ~292
[node] 节点：建 / 改 / 删 / 克隆 / 读 / 换父 / 批量变换 / 阵列 / 吸附 / 编组 / 合并烘焙 / 按画面框拟合 / 导入模型｜op: [read] get；[write] create update delete clone reparent transform array attach group merge fit_screen import｜必填见 params 描述，字段见 vibe3d_help {tool, op}｜create 平铺传 kind+shape+size，material 可省略（自动建）
| Name | Type | Req | Description |
|---|---|---|---|
| op | string | yes | node 下的 op；每个 op 的参数字段用 vibe3d_help {tool, op} 查 |
| params | object | – | op 与必填字段：create{kind} update{node_id,patch} delete{node_id} clone{node_id} get{node_id} reparent{node_id,parent} transform array{node_id,count} attach{node_id,target_id,face} group{ids,name} merge{no… |
| room_id | string | – | 省略用默认房间；多房间/多聊天并行必传 |
No output schema declared.
No examples provided.
vibe3d_open_editor ~109
[open_editor] 打开房间编辑器（默认弹窗）｜返回 url 与 hint；open:false 只回链接
| Name | Type | Req | Description |
|---|---|---|---|
| focus | – | – | 打开后选中并聚焦到该节点 |
| open | boolean | – | true（默认）直接弹窗；false 只返回 url 不弹 |
| reuse | boolean | – | 复用已开的同房间编辑页；false 强制新开一个 |
| room_id | string | – | – |
No output schema declared.
No examples provided.
vibe3d_render ~209
[render] 渲染：快照 / 多视角 / 单资产特写 / 像素取色 / ID 通道 / 序列帧｜op: snapshot views node pick assert id_pass sequence video｜必填见 params 描述，字段见 vibe3d_help {tool, op}｜snapshot / views 前先 vibe3d_status 探能力
| Name | Type | Req | Description |
|---|---|---|---|
| op | string | yes | render 下的 op；每个 op 的参数字段用 vibe3d_help {tool, op} 查 |
| params | object | – | op 与必填字段：snapshot views node{node_id} pick assert{anchors} id_pass sequence{from,to,fps} video{from,to,fps}。参数可平铺在顶层（顶层优先），省略 params 时取其顶层字段 |
| room_id | string | – | 省略用默认房间；多房间/多聊天并行必传 |
No output schema declared.
No examples provided.
vibe3d_room ~169
[room] 房间：建 / 列 / 切绑定 / 看摘要 / 关 / 时间线｜op: [read] list use get timeline；[write] create close｜必填见 params 描述，字段见 vibe3d_help {tool, op}
| Name | Type | Req | Description |
|---|---|---|---|
| op | string | yes | room 下的 op；每个 op 的参数字段用 vibe3d_help {tool, op} 查 |
| params | object | – | op 与必填字段：create list use{room_id} get close timeline。参数可平铺在顶层（顶层优先），省略 params 时取其顶层字段 |
| room_id | string | – | 省略用默认房间；多房间/多聊天并行必传 |
No output schema declared.
No examples provided.
vibe3d_scene ~234
[scene] 场景：取整份 / 摘要 / 查询节点 / 统计 / 拾取 / 体检 / 撤销重做 / 差分 / 导入导出 / 检查点 / 当前选中｜op: [read] get summary query stats pick validate diff export checkpoints selection；[write] undo redo import checkpoint restore｜必填见 params 描述，字段见 vibe3d_help {tool, op}｜import 是整场景替换，仅用于初始化或回滚
| Name | Type | Req | Description |
|---|---|---|---|
| op | string | yes | scene 下的 op；每个 op 的参数字段用 vibe3d_help {tool, op} 查 |
| params | object | – | op 与必填字段：get summary query stats pick validate undo redo diff export import{doc} checkpoint checkpoints restore{checkpoint_id} selection。参数可平铺在顶层（顶层优先），省略 params 时取其顶层字段 |
| room_id | string | – | 省略用默认房间；多房间/多聊天并行必传 |
No output schema declared.
No examples provided.
vibe3d_stage ~213
[stage] 舞台与环境：预设/曝光/后处理/三渲二；雾、背景、环境光、HDRI｜op: set env｜必填见 params 描述，字段见 vibe3d_help {tool, op}｜set/env 的字段平铺在顶层（勿包成 stage:{…}）：env 传 background/ambient/fog，颜色 [r,g,b,a]，fog 是对象 {near,far}、关雾传 false
| Name | Type | Req | Description |
|---|---|---|---|
| op | string | yes | stage 下的 op；每个 op 的参数字段用 vibe3d_help {tool, op} 查 |
| params | object | – | op 与必填字段：set{stage} env。参数可平铺在顶层（顶层优先），省略 params 时取其顶层字段 |
| room_id | string | – | 省略用默认房间；多房间/多聊天并行必传 |
No output schema declared.
No examples provided.
vibe3d_status ~60
[status] 能力探测：渲染器是否就绪、能否出 ID 通道、快照上限与载荷上限｜含 id-pass 支持；渲染或导入前先查一次
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the vibe3d MCP server?
vibe3d runs locally as an npm package, launched with npx -y @vibebyte/vibe3d-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @vibebyte/vibe3d-mcp
claude mcp add vibebytes-vibe3d -- npx -y @vibebyte/vibe3d-mcp
What is the vibe3d MCP server?
vibe3d is an MCP server listed in the public MCP registry as io.github.vibebytes/vibe3d. Edit and render 3D scenes over MCP: rooms, nodes, materials, cameras, and snapshots. This page covers its npm package (@vibebyte/vibe3d-mcp).
Is the vibe3d MCP server safe to use?
vibe3d scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 vibe3d MCP server expose?
vibe3d exposes 17 tools: vibe3d_help, vibe3d_status, vibe3d_room, vibe3d_scene, vibe3d_node, and 12 more. Their descriptions and schemas cost roughly 3,330 tokens of context every time the server is loaded.
Is the vibe3d MCP server still maintained?
vibe3d 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 vibe3d MCP server under?
vibe3d declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.