Freecad Robust MCP Server

freecad-robust-mcp PyPI v0.6.1

Published by spkane — 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.

Trust grade
A
93/100
Last scanned get badge →
Trust
A · 93/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
A Why this grade threat 100 − adoption risk = 93/100

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:

PointsAdoption-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 8

high Shell/command execution in server code (addon/FreecadRobustMCPBridge/freecad_mcp_bridge/server.py)MTC-SRC-002

In the server's implementation (`addon/FreecadRobustMCPBridge/freecad_mcp_bridge/server.py:587`): 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: "exec") exec(compiled, exec_globals) # noqa: S102 elapsed = (time.perf_counter() - start)

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 addon/FreecadRobustMCPBridge/freecad_mcp_bridge/server.py

high Shell/command execution in server code (src/freecad_mcp/bridge/embedded.py)MTC-SRC-002

In the server's implementation (`src/freecad_mcp/bridge/embedded.py:165`): 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: "exec") exec(compiled, exec_globals) # noqa: S102 elapsed = (time.perf_counter() - start)

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/freecad_mcp/bridge/embedded.py

high Shell/command execution in server code (src/freecad_mcp/bridge/socket.py)MTC-SRC-002

In the server's implementation (`src/freecad_mcp/bridge/socket.py:891`): 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: v in args.items(): exec(f"{{k}} = {{v!r}}") with open(macro_file, "r") as f: macro_code = f.read() exec(macro

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/freecad_mcp/bridge/socket.py

high Shell/command execution in server code (src/freecad_mcp/bridge/xmlrpc.py)MTC-SRC-002

In the server's implementation (`src/freecad_mcp/bridge/xmlrpc.py:873`): 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: v in args.items(): exec(f"{{k}} = {{v!r}}") # Execute macro with open(macro_file, "r") as f: macro_code = f.re

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/freecad_mcp/bridge/xmlrpc.py

low Shell/command execution in packaging/dev tooling (tests/just_commands/conftest.py)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`tests/just_commands/conftest.py:110`): 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: xt result = subprocess.run( # noqa: S603 cmd, cwd=self.project_root,

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 tests/just_commands/conftest.py

low Shell/command execution in packaging/dev tooling (tests/just_commands/test_docker.py)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`tests/just_commands/test_docker.py:39`): 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: ontext result = subprocess.run( ["docker", "info"], # noqa: S607 capture_output=True,

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 tests/just_commands/test_docker.py

low Shell/command execution in packaging/dev tooling (tests/just_commands/test_release.py)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`tests/just_commands/test_release.py:285`): 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: est context subprocess.run( # noqa: S603 ["git", "add", str(test_file)], # noqa: S607

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 tests/just_commands/test_release.py

low Shell/command execution in packaging/dev tooling (tests/unit/test_server.py)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`tests/unit/test_server.py:335`): 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: connect proc = subprocess.Popen( # noqa: S603 [ sys.executable, "-

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 tests/unit/test_server.py

Tools 83

Each tool and what it can reach — statically extracted from the published source.

  • activate_workbenchno sensitive capability
  • add_sketch_arcno sensitive capability
  • add_sketch_circleno sensitive capability
  • add_sketch_lineno sensitive capability
  • add_sketch_pointno sensitive capability
  • add_sketch_rectangleno sensitive capability
  • boolean_operationno sensitive capability
  • chamfer_edgesno sensitive capability
  • clear_selectionno sensitive capability
  • close_documentno sensitive capability
Show 73 more tools ↓
  • copy_objectno sensitive capability
  • create_boxno sensitive capability
  • create_coneno sensitive capability
  • create_cylinderno sensitive capability
  • create_documentno sensitive capability
  • create_helixno sensitive capability
  • create_holeno sensitive capability
  • create_macrono sensitive capability
  • create_macro_from_templateno sensitive capability
  • create_objectno sensitive capability
  • create_partdesign_bodyno sensitive capability
  • create_sketchno sensitive capability
  • create_sphereno sensitive capability
  • create_torusno sensitive capability
  • create_wedgeno sensitive capability
  • delete_macrono sensitive capability
  • delete_objectno sensitive capability
  • edit_objectno sensitive capability
  • execute_pythonno sensitive capability
  • export_3mfno sensitive capability
  • export_igesno sensitive capability
  • export_objno sensitive capability
  • export_stepno sensitive capability
  • export_stlno sensitive capability
  • fillet_edgesno sensitive capability
  • fit_allno sensitive capability
  • get_active_documentno sensitive capability
  • get_connection_statusno sensitive capability
  • get_console_logno sensitive capability
  • get_console_outputno sensitive capability
  • get_freecad_versionno sensitive capability
  • get_mcp_server_environmentno sensitive capability
  • get_screenshotno sensitive capability
  • get_selectionno sensitive capability
  • get_undo_redo_statusno sensitive capability
  • groove_sketchno sensitive capability
  • import_stepno sensitive capability
  • import_stlno sensitive capability
  • insert_part_from_libraryno sensitive capability
  • inspect_objectno sensitive capability
  • linear_patternno sensitive capability
  • list_documentsno sensitive capability
  • list_macrosno sensitive capability
  • list_objectsno sensitive capability
  • list_parts_libraryno sensitive capability
  • list_workbenchesno sensitive capability
  • loft_sketchesno sensitive capability
  • mirror_objectno sensitive capability
  • mirrored_featureno sensitive capability
  • open_documentno sensitive capability
  • pad_sketchno sensitive capability
  • pocket_sketchno sensitive capability
  • polar_patternno sensitive capability
  • read_macrono sensitive capability
  • recomputeno sensitive capability
  • recompute_documentno sensitive capability
  • redono sensitive capability
  • revolution_sketchno sensitive capability
  • rotate_objectno sensitive capability
  • run_macrono sensitive capability
  • save_documentno sensitive capability
  • scale_objectno sensitive capability
  • set_camera_positionno sensitive capability
  • set_display_modeno sensitive capability
  • set_object_colorno sensitive capability
  • set_object_visibilityno sensitive capability
  • set_placementno sensitive capability
  • set_selectionno sensitive capability
  • set_view_angleno sensitive capability
  • sweep_sketchno sensitive capability
  • undono sensitive capability
  • zoom_inno sensitive capability
  • zoom_outno sensitive capability

What this scan could not see

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.

VersionScoreFindingsEngineScanned
v0.6.1 latest A 93/100 8 1.9.0 2026-07-23

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.

MCP Trust Score: A · 93/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/freecad-robust-mcp/badge.svg)](https://mcptrustchecker.com/registry/freecad-robust-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/freecad-robust-mcp"><img src="https://mcptrustchecker.com/registry/freecad-robust-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/freecad-robust-mcp/badge.json via https://img.shields.io/endpoint?url=…

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 freecad-robust-mcp --online --registry pypi

Use the free API → How scoring works

More in Developer Tools