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.sceneview/mcp

NPM · SCENEVIEW-MCP · SCANNED SEP 21

3D & AR SDK for Android, iOS, Web — API docs, samples, validation, and code generation.

Available components

0 this week 86 Trust /100
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 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
  • 31 of 95 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 39 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability87
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1935 tokens (~129/item across 15 items; 13 tools + 2 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 Management93
  • Stability observed for 28 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 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 14 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
Install

How do I install the io.github.sceneview/mcp server?

io.github.sceneview/mcp runs locally as an npm package, launched with npx -y sceneview-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 · sceneview-mcp

# add to Claude Code
claude mcp add sceneview-mcp-2 -- npx -y sceneview-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "sceneview-mcp-2": {
      "command": "npx",
      "args": [
        "-y",
        "sceneview-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "sceneview-mcp-2": {
      "command": "npx",
      "args": [
        "-y",
        "sceneview-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add sceneview-mcp-2 -- npx -y sceneview-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "sceneview-mcp-2": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "sceneview-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add sceneview-mcp-2 --command npx --arg -y --arg sceneview-mcp
# ~/.hermes/config.yaml
mcp_servers:
  sceneview-mcp-2:
    command: "npx"
    args: ["-y", "sceneview-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "sceneview-mcp-2": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "sceneview-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add sceneview-mcp-2 -t stdio -c npx -a -y sceneview-mcp
// mcp.json
{
  "mcpServers": {
    "sceneview-mcp-2": {
      "command": "npx",
      "args": [
        "-y",
        "sceneview-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.

  • 21 Sept 26 +1

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

  • 20 Sept 26 +1
    • Security disclosure: unverified → pass functional
  • 19 Sept 26 0
    • Security disclosure: pass → unverified functional
  • 17 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 16 Sept 26 +1
    • Stability: 0.97 → pass security
  • 14 Sept 26 +1

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

  • 12 Sept 26 +1

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

  • 10 Sept 26 −3
    • Stability: pass → 0.80 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 21 Sept 2026 · Analysed npm/sceneview-mcp@3.4.7

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 95 packages
Packages resolved 95
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 13 exposed · ~1,832 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
get_ar_setup ~68

Returns detailed AR setup instructions — AndroidManifest permissions and features, Gradle dependencies, ARCore session configuration options (depth, light estimation, instant placement, plane detection, image tracking, cloud anchors), and a complete working AR starter template. More detailed than `get_setup` for AR-specific configuration.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_best_practices ~81

Returns SceneView performance and architecture best practices — memory management, model optimization, threading rules, Compose integration patterns, and common anti-patterns. Use this when the user asks about performance, optimization, best practices, or architecture.

NameTypeReqDescription
categorystringCategory to filter by. "all" returns everything. Defaults to "all" if omitted.

No output schema declared.

No examples provided.

get_ios_setup ~110

Returns the complete iOS setup guide for SceneViewSwift — SPM dependency, Package.swift example, minimum platform versions, Info.plist entries for AR (camera permission), and basic SwiftUI integration code. Use this when a user wants to set up SceneView for iOS, macOS, or visionOS.

NameTypeReqDescription
typestringyes"3d" for 3D-only scenes. "ar" for augmented reality (requires iOS, not macOS/visionOS via this path).

No output schema declared.

No examples provided.

get_migration_guide ~54

Returns the full SceneView 2.x → 3.0 migration guide. Use this when a user reports code that worked in 2.x but breaks in 3.0, or when helping someone upgrade.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_node_reference ~125

Returns the full API reference for a specific SceneView node type or composable — parameters, types, and a usage example — parsed directly from the official llms.txt. Use this when you need the exact signature or options for a node (e.g. ModelNode, LightNode, ARScene). If the requested type is not found, the response lists all available types.

NameTypeReqDescription
nodeTypestringyesThe node type or composable name to look up, e.g. "ModelNode", "LightNode", "ARScene", "AnchorNode". Case-insensitive.

No output schema declared.

No examples provided.

get_platform_roadmap ~58

Returns the SceneView multi-platform roadmap — current Android support status, planned iOS/KMP/web targets, and timeline. Use this when the user asks about cross-platform support, iOS, Kotlin Multiplatform, or future plans.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_sample ~673

Returns a complete, compilable Kotlin sample for a given SceneView scenario. Use this to get a working starting point before customising. Call `list_samples` first if you are unsure which scenario fits.

NameTypeReqDescription
scenariostringyesThe scenario to fetch: - "model-viewer": Full-screen 3D scene with a GLB model, HDR environment, orbit camera, and animation controls - "ar-model-viewer": AR scene with plane detection. Tap a surface…

No output schema declared.

No examples provided.

get_setup ~56

Returns the Gradle dependency and AndroidManifest snippet required to use SceneView in an Android project.

NameTypeReqDescription
typestringyes"3d" for 3D-only scenes. "ar" for augmented reality (includes 3D).

No output schema declared.

No examples provided.

get_troubleshooting ~65

Returns the SceneView troubleshooting guide — common crashes (SIGABRT, model not showing), build failures, AR issues (drift, overexposure, image detection), and performance problems. Use this when a user reports something not working, a crash, or unexpected behavior.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_web_setup ~74

Returns the complete Web setup guide for SceneView Web — npm install, Kotlin/JS Gradle config, HTML canvas setup, and basic Filament.js integration code. SceneView Web uses the same Filament rendering engine as Android, compiled to WebAssembly. Use this when a user wants to set up SceneView for browsers.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_samples ~98

Lists all available SceneView code samples with their IDs, descriptions, and tags. Use this to find the right sample before calling `get_sample`, or to show the user what SceneView can do.

NameTypeReqDescription
tagstringOptional tag to filter by (e.g. "ar", "3d", "ios", "swift", "anchor", "geometry", "animation", "video", "lighting"). Omit to list all samples.

No output schema declared.

No examples provided.

render_3d_preview ~249

Generates an interactive 3D preview link. Accepts a model URL, a SceneView code snippet, or both. Returns a URL to sceneview.github.io/preview that renders the model in the browser with orbit controls, AR support, and sharing. For model URLs: embeds a model-viewer link directly. For code snippets: shows the 3D preview with the code in a companion panel. Use this when you want to show a 3D model to the user — paste the link in your response and they can click to see it live.

NameTypeReqDescription
arbooleanEnable AR mode on supported devices (default: true).
autoRotatebooleanAuto-rotate the model (default: true).
codeSnippetstringSceneView code snippet (Kotlin or Swift) to display alongside the 3D preview in a companion panel. Useful when showing generated code together with a live preview.
modelUrlstringPublic URL to a .glb or .gltf model file. Must be HTTPS and CORS-enabled. If omitted, a default model is used.
titlestringCustom title shown above the preview.

No output schema declared.

No examples provided.

validate_code ~121

Checks a Kotlin or Swift SceneView snippet for common mistakes. For Kotlin: threading violations, wrong destroy order, missing null-checks, LightNode trailing-lambda bug, deprecated 2.x APIs. For Swift: missing @MainActor, async/await patterns, missing imports, RealityKit mistakes. Language is auto-detected. Always call this before presenting generated SceneView code to the user.

NameTypeReqDescription
codestringyesThe Kotlin or Swift source code to validate (composable function, SwiftUI view, class, or file). Language is auto-detected.

No output schema declared.

No examples provided.

Common questions

What is the io.github.sceneview/mcp server?

io.github.sceneview/mcp is listed in the public MCP registry as io.github.sceneview/mcp. 3D & AR SDK for Android, iOS, Web, API docs, samples, validation, and code generation. This page covers its npm package (sceneview-mcp).

Is the io.github.sceneview/mcp server safe to use?

io.github.sceneview/mcp scores 86 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 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 io.github.sceneview/mcp server expose?

io.github.sceneview/mcp exposes 13 tools: get_sample, list_samples, get_setup, validate_code, get_migration_guide, and 8 more. Their descriptions and schemas cost roughly 1,832 tokens of context every time the server is loaded.

Is the io.github.sceneview/mcp server still maintained?

io.github.sceneview/mcp is still listed as active in the MCP registry. We last reached this channel on 21 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 io.github.sceneview/mcp server under?

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