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.

Stori3D

NPM · STORI3D-MCP

See and edit the building project open in Stori3D: walls, rooms, openings, finishes, skies.

Available components

+3 this week 70 Trust /100

Last scanned (12 hours ago)

Scores higher than 39% of npm servers

Category Design and Media

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
  • 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency6
  • Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Licence could not be checked: the licence is shipped as a file inside the package, not declared as a standard (SPDX) licence identifier, so we cannot tell whether it is OSI-approved.Unverified
  • Actively maintained (last published 19 days ago).Pass
  • Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability75
  • 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 10254 tokens (~131/item across 78 items; 77 tools + 1 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 Management73
  • Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage77
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 32% 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
  • All 6 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 79 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
What we tested

Checks we ran (14)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • Maintenance
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (2)

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.

  • License in Provenance & TransparencyLicence could not be checked: the licence is shipped as a file inside the package, not declared as a standard (SPDX) licence identifier, so we cannot tell whether it is OSI-approved.
  • Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.

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 →

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.

  • 3 Nov 26 +1

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

  • 1 Nov 26 +1

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

  • 30 Oct 26 +1

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

  • 28 Oct 26 +1

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

  • 26 Oct 26 +1

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

  • 24 Oct 26 +1

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

  • 22 Oct 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.

  • 19 Oct 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.

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/stori3d-mcp@0.9.0

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 93 packages
Packages resolved 93
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 77 exposed · ~10,099 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
remove_elements ~56

Delete elements by id (a wall takes its doors and windows with it). Deleting a level, or more than 10 elements, asks the user in Stori3D first — tell them why.

NameTypeReqDescription
idsarrayyes–

No output schema declared.

No examples provided.

remove_property ~27

Remove a property definition (values already on elements are kept).

NameTypeReqDescription
namestringyes–

No output schema declared.

No examples provided.

remove_sheet ~37

Delete a sheet and the drawings placed on it (the model and the notes on drawings stay). Undoable.

NameTypeReqDescription
sheetstringyes–

No output schema declared.

No examples provided.

render_image ~171

A path-traced (photo-real) image: glass, lamps and the sky's light, saved on the user's computer. Takes from under a minute to many minutes: samples 64 is a quick draft, 256 good (default), 1024 best; bigger images take longer. Set the sky (set_sky) and sun (set_sun) and the camera (a saved view) first. The user sees Stori3D busy meanwhile. Returns where it was saved.

NameTypeReqDescription
formatstring––
heightinteger–Pixels, default 1080
pathstring––
samplesinteger––
viewstring–current (default), overview, or a saved view
widthinteger–Pixels, default 1920

No output schema declared.

No examples provided.

reply_comment ~78

Answer a comment thread on the review link (its id or number from list_comments), as the signed-in user: the client sees it on the link. The user sees your answer and allows it first. resolve: true also marks it resolved.

NameTypeReqDescription
resolveboolean––
textstringyes–
threadstringyes–

No output schema declared.

No examples provided.

resolve_comment ~44

Mark a comment thread on the review link resolved (or open again with resolved: false). Clients see it.

NameTypeReqDescription
resolvedboolean––
threadstringyes–

No output schema declared.

No examples provided.

save_view ~42

Save the user's current camera as a named view (for presenting, image exports and share links). Set it up first with set_camera.

NameTypeReqDescription
namestringyes–

No output schema declared.

No examples provided.

select ~47

Select elements in Stori3D so the user sees them highlighted and their properties (e.g. the doors that fail a check). Empty ids clears the selection.

NameTypeReqDescription
idsarrayyes–

No output schema declared.

No examples provided.

set_active_level ~55

Make a level the active one (the one being edited and drawn in plan; others show ghosted or hidden). New elements go on the active level unless you name one.

NameTypeReqDescription
levelstringyesLevel id or name

No output schema declared.

No examples provided.

set_camera ~81

Move the user's view: preset "overview", "top" (plan view of the active level) or "element" (frame one element), or an eye position and target (plan mm plus height in mm above ground).

NameTypeReqDescription
elementstring––
positionobject––
presetstring––
targetobject––

No output schema declared.

No examples provided.

set_project_details ~63

The details shown with shared tours: architect, client, location, description (plain text). Levels and floor area are added automatically.

NameTypeReqDescription
architectstring––
clientstring––
descriptionstring––
locationstring––

No output schema declared.

No examples provided.

set_properties ~62

Set custom property values on an element (null clears one). Values are checked against the project's definitions (types, choices). Setting data on an untagged room tags it and returns its new id.

NameTypeReqDescription
idstringyes–
valuesobjectyes–

No output schema declared.

No examples provided.

set_section ~77

Cut the model to see inside: "plan" (horizontal, height mm above the active floor), "x" (vertical at plan x = offset mm), "y" (vertical at plan y = offset mm), or "off".

NameTypeReqDescription
heightnumber––
modestringyes–
offsetnumber––

No output schema declared.

No examples provided.

set_site ~146

Put the project on the map: an address (looked up; the first match is used, and the matches are returned) or latitude/longitude, and north: degrees true north is turned clockwise from the plan's north (up). The map, terrain and neighbouring buildings load around it, and set_sun can then light it. Changes the project's saved site (not an undo step).

NameTypeReqDescription
addressstring–Street address or place, e.g. "322 King William St, Adelaide"
latnumber––
lonnumber––
northnumber–Degrees clockwise from plan north (default: unchanged, 0 for a new site)

No output schema declared.

No examples provided.

set_sky ~180

The project's sky (list_skies): an HDRI environment that lights the model with realistic reflections and ambient light and can show behind it. id "none" goes back to the default lighting. rotation (degrees) turns it, e.g. to put the sunset behind the building; intensity is the lighting strength (1 = as photographed, 0–5); background false lights the model without showing the sky; blur (0–1) softens the background. Settings you leave out keep their current values. Saved with the project; one undo step. Works alongside set_sun (direct sunlight and shadows).

NameTypeReqDescription
backgroundboolean––
blurnumber––
idstring–Sky id, or "none"; omit to adjust the current sky
intensitynumber––
rotationnumber––

No output schema declared.

No examples provided.

set_sun ~106

Sun and shadows for the site (needs a site location: set_site): it changes the project's saved sun (not an undo step). Date YYYY-MM-DD and time in hours local to the site (e.g. 9.5 = 09:30). Returns the sun's azimuth (degrees clockwise from north) and altitude. Use with capture_view for shadow studies.

NameTypeReqDescription
datestring––
enabledboolean––
timenumber––

No output schema declared.

No examples provided.

set_title_block ~117

The title block every sheet shares: project, practice, projectNumber, drawnBy, layout (corner, strip down the right side, or band along the bottom) and fields, the practice's own boxes (label and value, e.g. Checked, Client ref). The client and site come from set_project_details.

NameTypeReqDescription
drawnBystring––
fieldsarray––
layoutstring––
practicestring––
projectstring––
projectNumberstring––

No output schema declared.

No examples provided.

share_link ~101

Publish the project as a link anyone can open in a browser (no account): view-only, or a review link with comments: true, where clients pin comments on the model (list_comments reads them). The user is asked first; the project must be in the cloud (signed in), and review links need a plan with them. The link updates on every cloud save. Returns the link.

NameTypeReqDescription
commentsboolean–Let visitors pin comments (default false)

No output schema declared.

No examples provided.

share_tour ~157

Publish a tour as a player-only link (play/pause/speed, optional walking, project details; nothing else) and return it. With `story: true` it is shared as a scroll story instead: a page that opens on the floor plan and, as the visitor scrolls, raises the walls, comes down to where the tour starts and walks it, each room turning from a drawing to its materials as the camera goes in. A tour can have both links. The user is asked to allow it first, and the project must be signed in to the cloud. The link updates on every cloud save. Set the project details with set_project_details first.

NameTypeReqDescription
storyboolean––
tourstringyes–

No output schema declared.

No examples provided.

solid_operation ~143

Boolean on closed objects, by id (elements or other objects): union (merge), subtract (the first minus the others, which are removed), trim (the same, the others kept) or intersect (only the overlap). The first id is kept and becomes a plain mesh (it loses parametric data, so walls, slabs, roofs, stairs and columns can only cut, not be cut). A door or window used to cut cuts its rough opening and stays, e.g. to open an imported wall. Objects that aren't closed solids are refused. Returns the result's id.

NameTypeReqDescription
idsarrayyesThe first is kept
operationstringyes–

No output schema declared.

No examples provided.

split_wall ~94

Split a wall in two, offset mm from its start (along its centre line): the wall keeps the first part and its id, a new wall (returned) takes the rest with the doors and windows in it. Not through a door or window, nor within 50 mm of an end. Curved walls split into two arcs of the same circle.

NameTypeReqDescription
offsetnumberyes–
wallstringyes–

No output schema declared.

No examples provided.

status ~20

Whether Stori3D is connected, and to which project.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

stop_sharing ~64

Take a link down, so it stops working: the project's link (default), or a tour's link or scroll story (tour, story). The user is asked first. Comments already made are kept.

NameTypeReqDescription
storyboolean––
tourstring––

No output schema declared.

No examples provided.

undo ~34

Undo your own last change (only if the latest step in Stori3D's history is an AI change — never the user's).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

update_element ~447

Change an element. Lengths in mm, angles in degrees. By kind: level {name, elevation, height}; wall {length (along its centre line), height, thickness, type (a wall type name or null), bulge (curves it: mm its middle bows out, + to the left going start to end, 0 straight, at most half its straight length), start, end (moves its ends; walls joined there follow)}; slab {thickness}; roof {roofType flat|shed|gable|hip, pitch, overhang, thickness}; stair {width, going, maxRiser, rise, shape straight|L|U, turn left|right, winders (true: an L or U turns on tapered treads instead of a landing), position, rotation}; door/window {width, height, open 0–1, hand left|right, offset (slides it along its wall: mm from the wall's start to its centre)}, window also {sill}; model {position, rotation} (moves an imported model or group); furniture {position, rotation, width, depth, height, lamp {on, lumens, kelvin}}; column {shape rect|round, width, depth, height, position, rotation}; beam {start, end, width, depth, top}; ramp {start, end, width, rise, thickness, transition, headroom}; lift {position, rotation, width, depth, wall, height, doorWidth, doorHeight}; parking {start, end, count, accessible, bayWidth, bayLength, angle, startNumber} (moving start/end refits the count unless count is given); grid {origin, rotation, xSpacings, ySpacings, numbers, letters, extension}; room {name}. wall also {attachTop: true} to extend it up to the roof over it. Any: {name}. Fields a kind doesn't have are an error. A size outside the element's limits fails with the allowed range unless clamp is true.

NameTypeReqDescription
changesobjectyes–
clampboolean––
idstringyes–

No output schema declared.

No examples provided.

update_sheet ~123

Change a sheet: name, number, paper, orientation, status; revise with a note to issue the next revision (P1 → P2, A → B) dated today; removeDrawing (a drawing's id) takes a drawing off it.

NameTypeReqDescription
namestring––
numberstring––
orientationstring––
paperstring––
removeDrawingstring––
revisestring–What changed, for the revision table
sheetstringyes–
statusstring––

No output schema declared.

No examples provided.

update_tour ~100

Change a tour (id or name): name, loop, fov, walk (null: no walking), path (replaces all points; same format as create_tour) or stops.

NameTypeReqDescription
fovnumber––
loopboolean––
namestring––
patharray––
stopsarray––
tourstringyesTour id or name
walk–––

No output schema declared.

No examples provided.

Install

How do I install the Stori3D MCP server?

Stori3D runs locally as an npm package, launched with npx -y stori3d-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 · stori3d-mcp

# add to Claude Code
claude mcp add richy7734-stori3d-mcp -- npx -y stori3d-mcp
Common questions

What is the Stori3D MCP server?

Stori3D is an MCP server listed in the public MCP registry as io.github.richy7734/stori3d-mcp. See and edit the building project open in Stori3D: walls, rooms, openings, finishes, skies. This page covers its npm package (stori3d-mcp).

Is the Stori3D MCP server safe to use?

Stori3D scores 70 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. 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 Stori3D MCP server expose?

Stori3D exposes 77 tools: connect, status, project_summary, list_elements, get_element, and 72 more. Their descriptions and schemas cost roughly 10,099 tokens of context every time the server is loaded.

Is the Stori3D MCP server still maintained?

Stori3D 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 did VerifyMCP test on the Stori3D MCP server?

VerifyMCP ran 14 checks on Stori3D, covering Malware scan, Known CVEs, Install scripts, Dependency health and 10 more. 2 items could not be completed, a gap on our side rather than a finding about Stori3D: License and Security disclosure. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.