3d Printer MCP Server
mcp-3d-printer-server
npm
v1.2.5
Published by dmontgomery40 — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.
MCP server for connecting Claude with 3D printer management systems
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 7 = 93. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −6 | capability blast radius (high) — client exposure if the model is manipulated |
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 16
high Sensitive-source and external-sink co-existMTC-FLOW-004
Tools that read sensitive data ([list_printer_files]) and tools that can send data out ([check_fulu_orca_setup, fulu_bambu_network_rpc, blender_mcp_edit_model]) are exposed together. An agent can move private data to the sink.
Evidence: sources [list_printer_files] → sinks [check_fulu_orca_setup, fulu_bambu_network_rpc, blender_mcp_edit_model]
Fix: Keep secret-reading and egress capabilities on separate, separately-approved servers.
Location: flow list_printer_files → check_fulu_orca_setup
high Tool "check_fulu_orca_setup" exposes command/code executionMTC-CAP-001
Tool "check_fulu_orca_setup" appears to run shell commands or evaluate code (parameter "command"). Arbitrary execution driven by model input is one of the most dangerous MCP capabilities; combined with any untrusted input it becomes RCE.
Fix: Sandbox execution, allowlist commands/arguments, and never pass model output to a shell unescaped.
Location: tool check_fulu_orca_setup
high Tool "fulu_bambu_network_rpc" exposes command/code executionMTC-CAP-001
Tool "fulu_bambu_network_rpc" appears to run shell commands or evaluate code (parameter "command"). Arbitrary execution driven by model input is one of the most dangerous MCP capabilities; combined with any untrusted input it becomes RCE.
Fix: Sandbox execution, allowlist commands/arguments, and never pass model output to a shell unescaped.
Location: tool fulu_bambu_network_rpc
high Tool "blender_mcp_edit_model" exposes command/code executionMTC-CAP-001
Tool "blender_mcp_edit_model" appears to run shell commands or evaluate code (parameter "command"). Arbitrary execution driven by model input is one of the most dangerous MCP capabilities; combined with any untrusted input it becomes RCE.
Fix: Sandbox execution, allowlist commands/arguments, and never pass model output to a shell unescaped.
Location: tool blender_mcp_edit_model
high Shell/command execution in server code (dist/fulu-orca.js)MTC-SRC-002
In the server's implementation (`dist/fulu-orca.js:4`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: rt { spawn } from "node:child_process"; const BRIDGE_MAGIC = 0x52424a50; const FRAME_TYPE_JSON_REQUEST = 1; const FRAME_
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/fulu-orca.js
high Shell/command execution in server code (dist/index.js)MTC-SRC-002
In the server's implementation (`dist/index.js:1868`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: } = await import("node:child_process"); const result = await new Promise((resolve, reject) => { con
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/index.js
high Shell/command execution in server code (dist/stl/stl-manipulator.js)MTC-SRC-002
In the server's implementation (`dist/stl/stl-manipulator.js:10`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: port { execFile } from 'child_process'; const readFileAsync = promisify(fs.readFile); const writeFileAsync = promisify(f
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/stl/stl-manipulator.js
high Shell/command execution in server code (src/fulu-orca.ts)MTC-SRC-002
In the server's implementation (`src/fulu-orca.ts:4`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: rt { spawn } from "node:child_process"; const BRIDGE_MAGIC = 0x52424a50; const FRAME_TYPE_JSON_REQUEST = 1; const FRAME
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server src/fulu-orca.ts
high Shell/command execution in server code (src/index.ts)MTC-SRC-002
In the server's implementation (`src/index.ts:2275`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: } = await import("node:child_process"); const result = await new Promise<{ stdout: string; stderr: string }>((resol
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server src/index.ts
high Shell/command execution in server code (src/stl/stl-manipulator.ts)MTC-SRC-002
In the server's implementation (`src/stl/stl-manipulator.ts:10`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: port { execFile } from 'child_process'; const readFileAsync = promisify(fs.readFile); const writeFileAsync = promisify(
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server src/stl/stl-manipulator.ts
medium Unconstrained command parameter "bridge_command" on "check_fulu_orca_setup"MTC-CAP-006
Tool "check_fulu_orca_setup" takes a command-shaped parameter "bridge_command" with no enum/pattern constraint. Free-form, model- or attacker-controlled arguments reaching a shell is the command-injection precondition.
Fix: Constrain the parameter (enum/pattern), or build the command from a fixed template with escaped args.
Location: tool check_fulu_orca_setup · inputSchema.properties.bridge_command
medium Unconstrained command parameter "bridge_command" on "fulu_bambu_network_rpc"MTC-CAP-006
Tool "fulu_bambu_network_rpc" takes a command-shaped parameter "bridge_command" with no enum/pattern constraint. Free-form, model- or attacker-controlled arguments reaching a shell is the command-injection precondition.
Fix: Constrain the parameter (enum/pattern), or build the command from a fixed template with escaped args.
Location: tool fulu_bambu_network_rpc · inputSchema.properties.bridge_command
medium Unconstrained command parameter "bridge_command" on "blender_mcp_edit_model"MTC-CAP-006
Tool "blender_mcp_edit_model" takes a command-shaped parameter "bridge_command" with no enum/pattern constraint. Free-form, model- or attacker-controlled arguments reaching a shell is the command-injection precondition.
Fix: Constrain the parameter (enum/pattern), or build the command from a fixed template with escaped args.
Location: tool blender_mcp_edit_model · inputSchema.properties.bridge_command
low Mutating tool "check_fulu_orca_setup" declares no destructiveHintMTC-CAP-005
Tool "check_fulu_orca_setup" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.
Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.
Location: tool check_fulu_orca_setup
low Mutating tool "fulu_bambu_network_rpc" declares no destructiveHintMTC-CAP-005
Tool "fulu_bambu_network_rpc" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.
Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.
Location: tool fulu_bambu_network_rpc
low Mutating tool "blender_mcp_edit_model" declares no destructiveHintMTC-CAP-005
Tool "blender_mcp_edit_model" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.
Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.
Location: tool blender_mcp_edit_model
Tools 26
Each tool and what it can reach — statically extracted from the published source.
blender_mcp_edit_modelruns code / shellcheck_fulu_orca_setupruns code / shellfulu_bambu_network_rpcruns code / shelllist_printer_filesreads sensitive data3D Printer Filesno sensitive capability3D Printer Statusno sensitive capabilitycancel_printno sensitive capabilitycenter_modelno sensitive capabilityconfirm_temperaturesno sensitive capabilityextend_stl_baseno sensitive capability
Show 16 more tools ↓
generate_stl_visualizationno sensitive capabilityget_printer_statusno sensitive capabilityget_stl_infono sensitive capabilitylay_flatno sensitive capabilitymcp-3d-printer-serverno sensitive capabilitymerge_verticesno sensitive capabilitymodify_stl_sectionno sensitive capabilityprint_3mfno sensitive capabilityprocess_and_print_stlno sensitive capabilityrotate_stlno sensitive capabilityscale_stlno sensitive capabilityset_printer_temperatureno sensitive capabilityslice_stlno sensitive capabilitystart_printno sensitive capabilitytranslate_stlno sensitive capabilityupload_gcodeno sensitive capability
Toxic flows 1
Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).
What this scan could not see
- Tools were statically extracted from the published source (26 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 1
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v1.2.5 latest |
A 93/100 | 16 | 1.13.0 | 2026-09-09 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan mcp-3d-printer-server --onlineMore in Developer Tools
Hotel booking MCP server — 300K+ properties, real confirmation numbers, loyalty programs. Builders monetize every booking via Stripe Connect. The first MCP server that completes real hotel reservations inside AI conversations.
Manage AdGuard Home through AI assistants
Read-only Azure DevOps for MCP clients using only your existing browser session — no PAT, no Azure CLI. Browse work items, pull requests, comments, attachments and Artifacts feeds across every project, repo and feed you can access.
MCP server for Adobe Experience Manager Assets integration development
Servidor MCP para el tiempo oficial de España (API pública OpenData de AEMET). Predicción, observación y avisos como herramientas MCP tipadas.
A standalone MCP stdio bridge for Affinity by Canva's local MCP SSE server.