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.

three.ws 3D Agent Tools

NPM · @THREE-WS/MCP-SERVER

MCP tools from three.ws: free + paid text-to-3D, rigging, agent reputation, market intel.

0 this week 31 Trust /100

Last scanned (23 hours ago)

Scores higher than 3% 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 Security72
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • Dependency health was assessed across the 400 of 1547 dependencies we could resolve, so this covers what we could see, not the whole tree. 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 (Apache-2.0).Pass
  • Actively maintained (last published 70 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability0
  • Schema quality not yet verified: this package could not be installed in a clean environment, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: this package could not be installed in a clean environment, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: this package could not be installed in a clean environment, so we have no tool definitions to assess.Unverified
Tool Safety0
  • Tool safety not yet verified: this package could not be installed in a clean environment, so we have no tool text to scan.Unverified
Capabilities0
  • Protocol version not yet verified: this package could not be installed in a clean environment, so we never saw its MCP handshake.Unverified

Unverified: 5 categories

Categories scored 0 because our sandbox has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →

What we tested

Checks we ran (9)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure

Checks we could not complete (5)

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.

  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema quality not yet verified: this package could not be installed in a clean environment, so we have no schema to assess.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: this package could not be installed in a clean environment, so we have no schema to compare.
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: this package could not be installed in a clean environment, so we have no tool definitions to assess.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: this package could not be installed in a clean environment, so we have no tool text to scan.
  • Capabilities in Capabilities (scores 0 for this)Protocol version not yet verified: this package could not be installed in a clean environment, so we never saw its MCP handshake.

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.

  • 6 Nov 26 0
    • CVE-2026-102282 affects this package: high ▼ security
    • CVE-2026-114104 affects this package: high ▼ security
    • CVE-2026-39244 affects this package: high ▼ security
    • CVE-2026-114102 affects this package: high ▼ security
    • CVE-2026-92000 affects this package: high ▼ security
    • CVE-2026-77301 affects this package: high ▼ security
    • CVE-2026-114103 affects this package: high ▼ security
  • 27 Oct 26 0
    • CVE-2026-114142 affects this package: high ▼ security
  • 24 Oct 26 0
    • CVE-2023-54404 affects this package: high ▼ security
    • Known CVEs: CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. security
  • 23 Oct 26 31
    • CVE-2026-114144 affects this package: high ▼ security
    • CVE-2026-114143 affects this package: high ▼ security
    • CVE-2026-114141 affects this package: high ▼ security
  • 17 Oct 26 0
    • CVE-2026-45783 affects this package: high ▼ security
    • CVE-2026-16729 no longer affects this package ▲ security
    • GHSA-c6fg-446q-cg94 no longer affects this package ▲ security
    • CVE-2026-1527 no longer affects this package ▲ security
    • CVE-2026-1526 no longer affects this package ▲ security
    • CVE-2026-9679 no longer affects this package ▲ security
    • CVE-2026-77301 no longer affects this package ▲ security
    • CVE-2026-16728 no longer affects this package ▲ security
    • CVE-2026-45736 no longer affects this package ▲ security
    • GHSA-8238-w5pm-2374 no longer affects this package ▲ security
    • CVE-2026-6733 no longer affects this package ▲ security
    • CVE-2026-92000 no longer affects this package ▲ security
    • CVE-2026-18540 no longer affects this package ▲ security
    • CVE-2026-15157 no longer affects this package ▲ security
    • CVE-2026-102282 no longer affects this package ▲ security
    • CVE-2026-2229 no longer affects this package ▲ security
    • CVE-2026-1525 no longer affects this package ▲ security
    • CVE-2026-39244 no longer affects this package ▲ security
    • CVE-2026-22036 no longer affects this package ▲ security
    • CVE-2026-48779 no longer affects this package ▲ security
    • GHSA-p634-w6r4-rjp2 no longer affects this package ▲ security
    • CVE-2026-11525 no longer affects this package ▲ security
    • CVE-2026-12151 no longer affects this package ▲ security
  • 14 Oct 26 0
    • CVE-2026-11525 affects this package: high ▼ security
    • CVE-2026-1527 affects this package: high ▼ security
    • CVE-2026-102282 affects this package: high ▼ security
    • CVE-2026-9679 affects this package: high ▼ security
    • CVE-2026-16728 affects this package: high ▼ security
    • CVE-2026-1525 affects this package: high ▼ security
    • CVE-2026-15157 affects this package: high ▼ security
    • CVE-2026-39244 affects this package: high ▼ security
    • CVE-2026-92000 affects this package: high ▼ security
    • CVE-2026-6733 affects this package: high ▼ security
    • CVE-2026-22036 affects this package: high ▼ security
    • CVE-2026-16729 affects this package: high ▼ security
    • CVE-2026-77301 affects this package: high ▼ security
    • GHSA-8238-w5pm-2374 affects this package: high ▼ security
    • CVE-2026-12151 affects this package: high ▼ security
    • CVE-2026-2229 affects this package: high ▼ security
    • CVE-2026-18540 affects this package: high ▼ security
    • CVE-2026-1526 affects this package: high ▼ security
    • CVE-2026-48779 affects this package: high ▼ security
    • GHSA-p634-w6r4-rjp2 affects this package: high ▼ security
    • GHSA-c6fg-446q-cg94 affects this package: high ▼ security
    • CVE-2026-45736 affects this package: high ▼ security
    • CVE-2026-45783 no longer affects this package ▲ security
  • 11 Oct 26 0
    • CVE-2026-45783 affects this package: high ▼ security
    • CVE-2026-16729 no longer affects this package ▲ security
    • GHSA-c6fg-446q-cg94 no longer affects this package ▲ security
    • CVE-2026-1527 no longer affects this package ▲ security
    • CVE-2026-1526 no longer affects this package ▲ security
    • CVE-2026-9679 no longer affects this package ▲ security
    • CVE-2026-77301 no longer affects this package ▲ security
    • CVE-2026-16728 no longer affects this package ▲ security
    • CVE-2026-45736 no longer affects this package ▲ security
    • GHSA-8238-w5pm-2374 no longer affects this package ▲ security
    • CVE-2026-6733 no longer affects this package ▲ security
    • CVE-2026-92000 no longer affects this package ▲ security
    • CVE-2026-18540 no longer affects this package ▲ security
    • CVE-2026-15157 no longer affects this package ▲ security
    • CVE-2026-102282 no longer affects this package ▲ security
    • CVE-2026-2229 no longer affects this package ▲ security
    • CVE-2026-1525 no longer affects this package ▲ security
    • CVE-2026-39244 no longer affects this package ▲ security
    • CVE-2026-22036 no longer affects this package ▲ security
    • CVE-2026-48779 no longer affects this package ▲ security
    • GHSA-p634-w6r4-rjp2 no longer affects this package ▲ security
    • CVE-2026-11525 no longer affects this package ▲ security
    • CVE-2026-12151 no longer affects this package ▲ security
    • License: unverified → pass ▲ functional
    • Licence: Apache-2.0 functional
    • Package version: 1.2.2 → 1.2.3 functional
  • 9 Oct 26 0
    • CVE-2026-11525 affects this package: high ▼ security
    • CVE-2026-1527 affects this package: high ▼ security
    • CVE-2026-102282 affects this package: high ▼ security
    • CVE-2026-9679 affects this package: high ▼ security
    • CVE-2026-16728 affects this package: high ▼ security
    • CVE-2026-1525 affects this package: high ▼ security
    • CVE-2026-15157 affects this package: high ▼ security
    • CVE-2026-39244 affects this package: high ▼ security
    • CVE-2026-104183 affects this package: high ▼ security
    • CVE-2026-92000 affects this package: high ▼ security
    • CVE-2026-6733 affects this package: high ▼ security
    • CVE-2026-22036 affects this package: high ▼ security
    • CVE-2026-16729 affects this package: high ▼ security
    • CVE-2026-77301 affects this package: high ▼ security
    • GHSA-8238-w5pm-2374 affects this package: high ▼ security
    • CVE-2026-12151 affects this package: high ▼ security
    • CVE-2026-2229 affects this package: high ▼ security
    • CVE-2026-18540 affects this package: high ▼ security
    • CVE-2026-104182 affects this package: high ▼ security
    • CVE-2026-1526 affects this package: high ▼ security
    • CVE-2026-48779 affects this package: high ▼ security
    • GHSA-p634-w6r4-rjp2 affects this package: high ▼ security
    • GHSA-c6fg-446q-cg94 affects this package: high ▼ security
    • CVE-2026-45736 affects this package: high ▼ security
    • CVE-2026-45783 no longer affects this package ▲ security
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 Nov 2026 · Analysed npm/@three-ws/mcp-server@1.2.3

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 →

Vulnerabilities 20 findings
ID CVE Severity Vector Fix available
GHSA-32mq-hpph-xfvr CVE-2026-45783 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-7q85-xj36-vmfc CVE-2026-77301 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-8238-w5pm-2374 CVE-2026-114102 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-c6fg-446q-cg94 CVE-2026-114103 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L yes
GHSA-j5f4-cc29-5x44 CVE-2026-102282 high CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N yes
GHSA-p634-w6r4-rjp2 CVE-2026-114104 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N yes
GHSA-rcw4-f5rp-g42v CVE-2026-92000 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-xcpc-8h2w-3j85 CVE-2026-39244 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-3gc7-fjrx-p6mg CVE-2025-3194 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H no
GHSA-528h-pc64-c93x CVE-2026-71429 medium CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-hqr4-qq8f-hg3x CVE-2026-104182 medium CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-mjw6-4jj6-33hc CVE-2026-104183 medium CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L yes
GHSA-4qx8-w7c3-pj3p CVE-2026-114141 high yes
GHSA-82x6-q7mm-w9cf CVE-2026-77465 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-9j65-hcg3-gc64 CVE-2026-114143 high yes
GHSA-9qmh-m7c6-f92p CVE-2026-114144 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-h895-cgqg-jf52 CVE-2026-114142 high yes
GHSA-v5mp-jgw5-2x6j CVE-2026-63376 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L yes
GHSA-w5hq-g745-h8pq CVE-2026-41907 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N yes
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 400 packages
Packages resolved 400
Deprecated 2
Stale 88
No linked repository 6
Tree resolution Partial

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

Background: SBOMs and build attestations, explained →

MCP tools

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 →

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.

Install

How do I install the three.ws 3D Agent Tools MCP server?

three.ws 3D Agent Tools runs locally as an npm package, launched with npx -y @three-ws/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @three-ws/mcp-server

# add to Claude Code
claude mcp add nirholas-3d-agent-mcp -- npx -y @three-ws/mcp-server
Common questions

What is the three.ws 3D Agent Tools MCP server?

three.ws 3D Agent Tools is an MCP server listed in the public MCP registry as io.github.nirholas/3d-agent-mcp. MCP tools from three.ws: free + paid text-to-3D, rigging, agent reputation, market intel. This page covers its npm package (@three-ws/mcp-server).

Is the three.ws 3D Agent Tools MCP server safe to use?

three.ws 3D Agent Tools scores 31 out of 100 on VerifyMCP. We recorded 20 known advisories against it as of 21 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.

Is the three.ws 3D Agent Tools MCP server still maintained?

three.ws 3D Agent Tools is still listed as active in the MCP registry. We last reached this channel on 21 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 three.ws 3D Agent Tools MCP server under?

three.ws 3D Agent Tools 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.

What did VerifyMCP test on the three.ws 3D Agent Tools MCP server?

VerifyMCP ran 9 checks on three.ws 3D Agent Tools, covering Malware scan, Known CVEs, Install scripts, Dependency health and 5 more. 5 items could not be completed, a gap on our side rather than a finding about three.ws 3D Agent Tools: Schema quality, Stability, Tool coverage, Tool safety and 1 more. 5 categories score 0 for that reason, because we only credit what we can confirm. 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.