Three.jsCAUTION
MCP server for controlling ThreeJs source code, only basic function
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
MCP server for controlling ThreeJs source code, only basic function
b8224f42697eOBSERVED · 2026-10-09Connect
Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control.
claude mcp add three-js-mcp -- npx -y [email protected]
{
"mcpServers": {
"three-js-mcp": {
"command": "npx",
"args": [
"-y",
"[email protected]"
]
}
}
}Exposed tools (7)
2 read · 4 write · 1 destructive. Blast radius: 1 tool can delete or overwrite — an agent that can be talked into calling a tool can be talked into calling this one.
| Tool | Risk | Description |
|---|---|---|
addObject | write | Add an object to the scene |
asset-creation-strategy | read | Defines the preferred strategy for creating assets in ThreeJS |
getSceneState | read | Get the current scene state |
moveObject | write | Move an object to a new position |
removeObject | destructive | Remove an object |
startRotation | write | Start rotating an object around the y-axis |
stopRotation | write | Stop rotating an object |
Trust audit
CAUTIONgrade B · trust 89/100 Install with care. The audit found things worth knowing before you trust its output.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | WARN |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | WARN |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- declared (1 observation(s))
- Network
- UNDECLARED (3 observation(s))
- Shell
- none-observed
- Dependencies
- not all pinned
- Secrets in source
- none-found
Findings (6)
import WebSocket, { WebSocketServer } from 'ws';let clientConnection: WebSocket | null = null;
wss.on('connection', (ws: WebSocket) => {removeObject
@modelcontextprotocol/sdk, express, ws, @types/express, @types/ws, typescript
network use found in code, not declared in the description
Gates applied: no_behavioural_pass.
b8224f42697efull audit observations/trust-audit/mcp-server/locchung__three-js.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-09 | b8224f42697e | CAUTION | B | 89 | first audit |
Questions
What is the Three.js MCP server?
MCP server for controlling ThreeJs source code, only basic function
What tools does Three.js expose?
7 in total: 2 read-only, 4 that write, and 1 that can delete or overwrite (removeObject). Every one is listed on this page with its risk.
Is Three.js safe to connect to an agent?
With care. The audit graded it B (89/100) and found 6 things worth knowing before you trust this server, listed below with the exact line each was found on. Separately from the audit: 1 of its tools can destroy data, so scope the token you give it to what you actually need.
What credentials does Three.js need?
No credential environment variables were found in its source, so it appears to need none.
How does Three.js run?
It speaks stdio, so it runs as a local process your client starts. It is published on npm as three-js-mcp at 1.0.0.
How current is this page?
The grade is for one exact copy of the source (b8224f42697e), read on 2026-10-09. The repository is watched and re-audited when it changes.