openscad-mcp-server

MCPattested
v1.0.6Filipe BoldoMITUpdated 7d agonpmGitHub

An MCP server that renders PNG previews and STL geometry from OpenSCAD (SCAD) source code.

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Attested build
A verified provenance attestation binds this artifact to the listed repository. Nobody has claimed the listing yet — this proves where the code was built, not who stands behind it.
397Downloads/wk
6GitHub stars
7d agoLast update
Package
AuthorFilipe Boldo
LicenseMIT
Version1.0.6
Sourcenpm+mcp-registry
npmopenscad-mcp-server
GitHubfboldo/openscad-mcp-server
SBOMCycloneDX 1.6 ↓
Trust Status
A
85/100Trusted
✓Listed in Forge index+10/10
✓Identity verified · attested build+20/20
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
✓npm Trusted Publishing (Sigstore)+5/5
—npm maintainer match+0/5
→ Publisher: add the verified GitHub login to the npm package's maintainers (npm owner add <login>)
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusIdentity verified
PublisherUnverified
SignatureUnsigned
Domain—
Provenance✓ Sigstore-verified · 3cf8b6b
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface2 tools · none privileged
Security scan✓ Cleanv1.0.6 · todayHow well does this scan work?
EvalsNone
IndexedSep 27, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

2 tools · none privileged
Statically extracted from the published packagev1.0.6 · 11h ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

export_scad_stlExport OpenSCAD (SCAD) source code into an STL and return it as an embedded resource blob.

Export OpenSCAD (SCAD) source code into an STL and return it as an embedded resource blob.

No input schema was published for this tool.

render_scad_pngRender OpenSCAD (SCAD) source code into a PNG preview image. Provide the SCAD text in `scadCode` and optionally set `width`/`height` (pixels). Optional camera control is available via `cameraPreset` (named preset) or `cameraPosition` ({x,y,z}).

Render OpenSCAD (SCAD) source code into a PNG preview image. Provide the SCAD text in `scadCode` and optionally set `width`/`height` (pixels). Optional camera control is available via `cameraPreset` (named preset) or `cameraPosition` ({x,y,z}).

No input schema was published for this tool.

2 of 2 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

An MCP server that renders PNG previews and STL geometry from OpenSCAD (SCAD) source code.

Keywords
mcpmodelcontextprotocolopenscadscadcadstlpng3d
Alternatives
Comparing tool surfaces…

Tools exposed

2 tools · none privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

Dependency tree

What one Forge scan resolved from npm metadata on 2026-10-01 — observed resolution, not a publisher declaration.

60 packages resolved · 7 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

60 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+48 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies, optionalDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.