SolidWorks MCP
PYPI · SOLIDWORKS-MCP-PYTHON
Drive SolidWorks from AI agents: parts, assemblies, drawings and export over the COM API.
Available components
Last scanned (2 hours ago)
Scores higher than 74% of PyPI servers
Category Developer Tools
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 Security99
- No malware found by supply-chain analysis.Pass
- Known CVEs were checked across the 65 of 66 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- Dependency health was assessed across the 65 of 66 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to andrewbartels1/SolidworksMCP-python). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability64
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 10924 tokens (~70/item across 154 items; 154 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 98% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 4 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_feature" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 154 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 5 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 4 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 3 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 2 Nov 26 62
First indexed and scored.
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 5 Nov 2026 · Analysed pypi/solidworks-mcp-python@1.5.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | andrewbartels1/SolidworksMCP-python |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/andrewbartels1/SolidworksMCP-python/.github/workflows/release.yml@refs/tags/v1.5.0 |
| Rekor log index | 3637392254 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:066c1c5ab174174c8b9a615276c59168447339ce33192be62f8f32a5760e0fbf |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 65 packages
| Packages resolved | 65 |
|---|---|
| Stale | 7 |
| No linked repository | 2 |
| Tree resolution | Partial |
The dependency tree was only partially resolved, so these counts may be incomplete.
Background: SBOMs and build attestations, explained →
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 →
update_sheet_format Update Sheet Format ~59
Update the sheet format and title block information. Applies drawing templates and updates title block fields with project information, revision data, and drawing metadata. Essential for standardized documentation and drawing control.
| Name | Type | Req | Description |
|---|---|---|---|
| input_data | object | yes | The input data value. |
Structured output declared, but exposes no named fields.
No examples provided.
update_title_block Update Title Block ~52
Update title block fields for the active drawing. Applies drawing metadata such as title, drawing number, and approval fields to keep documentation aligned with standards.
| Name | Type | Req | Description |
|---|---|---|---|
| input_data | object | yes | The input data value. |
Structured output declared, but exposes no named fields.
No examples provided.
validate_drawing_completeness Validate Drawing Completeness ~31
Validate drawing completeness for production readiness.
| Name | Type | Req | Description |
|---|---|---|---|
| input_data | object | yes | The input data value. |
Structured output declared, but exposes no named fields.
No examples provided.
verify_model Verify Model ~332
Check the active part or assembly against what you meant to build. Call this as the last step of a build (and whenever a step looks suspicious). A modelling tool returning success does not prove the geometry is right; this reads the model back and compares it with your expectations. Give only the expectations you know; each becomes one check. With no expectations it just reports what it measured. Units: mm, mm³ and kg. ``bounding_box_mm`` is the overall size ``[x, y, z]`` in model axes (a sketch on the Front Plane extrudes along z). Widen ``relative_tolerance`` when your hand calculation ignores fillets or chamfers, and ``length_tolerance_mm`` when ``measured.bounding_box_method`` is ``assembly_box`` (SolidWorks' assembly box can be slightly larger than the parts). Mass depends on the assigned material; without one SolidWorks uses a default density. Each check reports ``expected``, ``actual``, ``tolerance`` and ``passed``: ``true``, ``false``, or ``null`` when the value could not be measured (never counted as a pass). ``verdict`` is ``pass``, ``fail``, ``inconclusive`` (nothing failed, something unmeasured) or ``report_only``. ``status`` stays ``success`` when the model does not match: the tool worked, the model is what failed.
| Name | Type | Req | Description |
|---|---|---|---|
| input_data | – | – | Expectations and tolerances. Defaults to None (report only). |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the SolidWorks MCP server?
SolidWorks MCP runs locally as a PyPI package, launched with uvx solidworks-mcp-python. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · solidworks-mcp-python
claude mcp add andrewbartels1-solidworks-mcp-python -- uvx solidworks-mcp-python
What is the SolidWorks MCP server?
SolidWorks MCP is listed in the public MCP registry as io.github.andrewbartels1/solidworks-mcp-python. Drive SolidWorks from AI agents: parts, assemblies, drawings and export over the COM API. This page covers its PyPI package (solidworks-mcp-python).
Is the SolidWorks MCP server safe to use?
SolidWorks MCP scores 77 out of 100 on VerifyMCP. Its build provenance is signed and verified. 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.
What tools does the SolidWorks MCP server expose?
SolidWorks MCP exposes 154 tools: open_model, create_part, create_assembly, create_drawing, close_model, and 149 more. Their descriptions and schemas cost roughly 10,924 tokens of context every time the server is loaded.
Is the SolidWorks MCP server still maintained?
SolidWorks MCP is still listed as active in the MCP registry. We last reached this channel on 5 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 SolidWorks MCP server under?
SolidWorks MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.