Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

three.ws Scenes

NPM · @THREE-WS/SCENE-MCP · SCANNED AUG 3

Compose a placed 3D diorama from one sentence, export a forged world, browse saved scenes.

Available components

+23 this week 67 Trust /100
Trust breakdown (6 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 →

Supply Chain Security87
  • No malware found by supply-chain analysis.Pass
  • Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability69
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 855 tokens (~171/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 Management23
  • Stability observed for 7 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
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · @three-ws/scene-mcp

# add to Claude Code
claude mcp add nirholas-scene-mcp -- npx -y @three-ws/scene-mcp
# add to Codex CLI
codex mcp add nirholas-scene-mcp -- npx -y @three-ws/scene-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "nirholas-scene-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@three-ws/scene-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add nirholas-scene-mcp --command npx --arg -y --arg @three-ws/scene-mcp
# ~/.hermes/config.yaml
mcp_servers:
  nirholas-scene-mcp:
    command: "npx"
    args: ["-y", "@three-ws/scene-mcp"]
// mcp.json
{
  "mcpServers": {
    "nirholas-scene-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@three-ws/scene-mcp"
      ]
    }
  }
}
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.

  • 2 Aug 26 +48
    • Provenance: unverified → fail security
    • Install scripts: unverified → pass security
    • Known CVEs: unverified → partial security
    • Malware scan: unverified → pass security
    • Tool coverage: 100 → unverified functional
    • Schema quality: unverified → excellent functional
    • License: unverified → pass functional
    • Stability: unverified → 0.20 functional
    • Maintenance: unverified → pass functional
    • MCP protocol: unverified → pass functional
    • Dependency health: unverified → partial functional
    • First check of Schema quality: unverified functional
    • Licence: Apache-2.0 functional
  • 31 Jul 26 −7
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 −18
    • Malware scan: pass → unverified security
  • 27 Jul 26 44

    First indexed and scored.

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 3 Aug 2026 · Analysed npm/@three-ws/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Dependencies 95 packages

95 packages in the resolved dependency tree · 95 deprecated · 29 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 5 exposed · ~645 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.

Tool Tokens
build_world ~166

One sentence → a fully forged, exported 3D world, entirely server-side: composes the scene plan, forges every object on the free text→3D lane, and merges the result into one GLB with named, selectable nodes plus ground and lighting. Returns the populated diorama, the merged GLB URL, and a ready-to-open Scene Studio link. This is the whole progressive /diorama browser flow collapsed into one call — it can take a couple of minutes for a full object set. Partial forges are not failures: whatever forged is exported, and `skipped` names anything that did not.

NameTypeReqDescription
promptstringyesOne short sentence describing the world to build, e.g. "a neon alley with a food cart and two streetlights".

No output schema declared.

No examples provided.

compose_scene ~143

Compose a tiny 3D diorama from one short sentence. Returns a PLAN: an evocative title, a mood (dawn/day/dusk/night), ground + island type, a color palette, and 2–8 placed objects — each with a single-object forge prompt, position, scale and rotation. No meshes are generated yet and nothing is saved; feed the plan to the three.ws diorama page (or /api/forge per object) to build the world. Read-mostly but runs live LLM inference.

NameTypeReqDescription
promptstringyesOne short sentence describing the world to build, e.g. "a lonely lighthouse on a stormy cliff".

No output schema declared.

No examples provided.

export_scene ~164

Merge an already-forged diorama (objects with real glbUrl values, e.g. from your own forging after compose_scene, or fetched via get_scene) into ONE glTF 2.0 binary: every object becomes a named, selectable node, plus a real ground disc and mood-tuned lighting. Returns the merged GLB URL and a ready-to-open three.ws Scene Studio link. Objects that never forged are skipped and reported, not treated as a failure — a partial world still exports. Requires the target deployment to have object storage configured (three.ws does).

NameTypeReqDescription
dioramaobjectyesThe diorama object to export — same shape returned by compose_scene/get_scene, with each object you want included carrying status:"ready" and a real glbUrl.

No output schema declared.

No examples provided.

get_scene ~74

Fetch one saved diorama (a fully-forged 3D world) by its id, including its title, mood, palette, ground, and the placed objects with their GLB URLs. Returns the orbitable viewer URL. Read-only.

NameTypeReqDescription
idstringyesThe diorama id returned when the world was saved.

No output schema declared.

No examples provided.

list_scenes ~98

Browse the public diorama gallery — the most recent saved worlds, or the featured set. Returns a list of cards (id, title, mood, thumbnail/preview, view count) plus each world's viewer URL. Read-only.

NameTypeReqDescription
limitintegerHow many to return (1–50, default 24).
liststringWhich gallery to read: newest saved worlds ("recent") or the curated set ("featured").

No output schema declared.

No examples provided.