Caid MCP Server

caid-mcp PyPI v0.6.0

Published by an unidentified publisher — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.

Trust grade
A
92/100
Last scanned get badge →
Trust
A · 92/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.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 92/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 − 8 = 92. 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
−2 publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read

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 7

high Tool "shell_object" exposes command/code executionMTC-CAP-001

Tool "shell_object" appears to run shell commands or evaluate code (keyword "shell" in tool name). 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 shell_object

high Shell/command execution in server code (caid_mcp/core.py)MTC-SRC-002

In the server's implementation (`caid_mcp/core.py:237`): 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: try: proc = subprocess.run( [sys.executable, "-c", script], capture_output=True, tex

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 caid_mcp/core.py

high Shell/command execution in server code (caid_mcp/tools/advanced.py)MTC-SRC-002

In the server's implementation (`caid_mcp/tools/advanced.py:53`): 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: try: proc = subprocess.run( [sys.executable, "-c", wrapper], 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 caid_mcp/tools/advanced.py

high Shell/command execution in server code (caid_mcp/tools/parts_user.py)MTC-SRC-002

In the server's implementation (`caid_mcp/tools/parts_user.py:154`): 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: try: proc = subprocess.run( [sys.executable, "-c", wrapper], capture_output=True, te

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 caid_mcp/tools/parts_user.py

medium Untrusted input can drive an external actionMTC-FLOW-005

Untrusted-input tools ([freecad_library_browse, freecad_library_import]) co-exist with external-action tools ([shell_object]). A prompt injection could cause unwanted external actions, though no direct sensitive-data leak path was found.

Evidence: untrusted [freecad_library_browse, freecad_library_import] → sinks [shell_object]

Fix: Require confirmation for state-changing/egress actions triggered after processing untrusted content.

Location: flow freecad_library_browse → shell_object

low Mutating tool "shell_object" declares no destructiveHintMTC-CAP-005

Tool "shell_object" 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 shell_object

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

In a packaging/dev/install script (shipped, but not the server runtime) (`tests/test_caid_mcp.py:529`): 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: "scene": scene} exec("result = caid.box(5, 5, 5)", exec_globals) assert "result" in exec_globals

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/test_caid_mcp.py

Tools 107

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

  • freecad_library_browseingests untrusted input
  • freecad_library_importingests untrusted input
  • shell_objectruns code / shell
  • add_clearance_holeno sensitive capability
  • add_holeno sensitive capability
  • add_tap_holeno sensitive capability
  • align_objectsno sensitive capability
  • assembly_addno sensitive capability
  • assembly_mergeno sensitive capability
  • assembly_moveno sensitive capability
Show 97 more tools ↓
  • assembly_rotateno sensitive capability
  • boolean_cutno sensitive capability
  • boolean_intersectno sensitive capability
  • boolean_unionno sensitive capability
  • chamfer_solid_edgesno sensitive capability
  • chamfer_wire_cornersno sensitive capability
  • check_object_validno sensitive capability
  • clear_sceneno sensitive capability
  • combine_objectsno sensitive capability
  • compare_rendersno sensitive capability
  • create_arcno sensitive capability
  • create_array_on_curveno sensitive capability
  • create_assemblyno sensitive capability
  • create_belt_wireno sensitive capability
  • create_boltno sensitive capability
  • create_boxno sensitive capability
  • create_circleno sensitive capability
  • create_circular_patternno sensitive capability
  • create_coneno sensitive capability
  • create_cylinderno sensitive capability
  • create_extruded_polygonno sensitive capability
  • create_groupno sensitive capability
  • create_layerno sensitive capability
  • create_lineno sensitive capability
  • create_linear_patternno sensitive capability
  • create_nutno sensitive capability
  • create_polylineno sensitive capability
  • create_pulley_assemblyno sensitive capability
  • create_revolved_profileno sensitive capability
  • create_sphereno sensitive capability
  • create_splineno sensitive capability
  • create_torusno sensitive capability
  • create_warehouse_bearingno sensitive capability
  • create_warehouse_fastenerno sensitive capability
  • create_washerno sensitive capability
  • delete_objectno sensitive capability
  • distribute_objectsno sensitive capability
  • duplicate_objectno sensitive capability
  • exploded_viewno sensitive capability
  • export_brepno sensitive capability
  • export_stepno sensitive capability
  • export_stlno sensitive capability
  • extend_curveno sensitive capability
  • extrude_surfaceno sensitive capability
  • fillet_solid_edgesno sensitive capability
  • fillet_wire_cornersno sensitive capability
  • find_edges_near_pointno sensitive capability
  • find_faces_near_pointno sensitive capability
  • find_partsno sensitive capability
  • freecad_library_searchno sensitive capability
  • get_object_propertiesno sensitive capability
  • heal_objectno sensitive capability
  • import_brepno sensitive capability
  • import_partno sensitive capability
  • import_stepno sensitive capability
  • inspect_objectno sensitive capability
  • intersect_curvesno sensitive capability
  • join_curvesno sensitive capability
  • list_edgesno sensitive capability
  • list_facesno sensitive capability
  • list_fastener_sizesno sensitive capability
  • list_groupsno sensitive capability
  • list_layersno sensitive capability
  • list_objectsno sensitive capability
  • list_snapshotsno sensitive capability
  • list_warehouse_partsno sensitive capability
  • list_warehouse_sizesno sensitive capability
  • loft_circle_to_rectno sensitive capability
  • loft_profilesno sensitive capability
  • mass_propertiesno sensitive capability
  • measure_distanceno sensitive capability
  • mirror_objectno sensitive capability
  • offset_curveno sensitive capability
  • orient_objectno sensitive capability
  • project_curveno sensitive capability
  • render_objectno sensitive capability
  • render_sceneno sensitive capability
  • restore_snapshotno sensitive capability
  • reverse_curveno sensitive capability
  • rotate_objectno sensitive capability
  • run_cadquery_scriptno sensitive capability
  • save_snapshotno sensitive capability
  • scale_objectno sensitive capability
  • scan_part_libraryno sensitive capability
  • search_partsno sensitive capability
  • section_viewno sensitive capability
  • server_infono sensitive capability
  • set_object_propertiesno sensitive capability
  • simplify_objectno sensitive capability
  • split_with_objectno sensitive capability
  • split_with_planeno sensitive capability
  • sweep_along_pathno sensitive capability
  • sweep_circle_along_pathno sensitive capability
  • translate_objectno sensitive capability
  • undono sensitive capability
  • ungroupno sensitive capability
  • unroll_surfaceno 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

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.0 latest A 92/100 7 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 · 92/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/caid-mcp/badge.svg)](https://mcptrustchecker.com/registry/caid-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/caid-mcp"><img src="https://mcptrustchecker.com/registry/caid-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/caid-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 caid-mcp --online --registry pypi

Use the free API → How scoring works

More in Developer Tools