SolidWorks
PYPI · SOLIDWORKS-MCP · SCANNED OCT 1
Model, measure and verify parametric parts and assemblies in a running SolidWorks (Windows).
Available components
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 0 of 28 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to hjbaard/SolidWorks-MCP). 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 Usability79
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 5724 tokens (~104/item across 55 items; 54 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 54 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 56 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the SolidWorks MCP server?
SolidWorks runs locally as a PyPI package, launched with uvx solidworks-mcp. 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
claude mcp add hjbaard-solidworks-mcp -- uvx solidworks-mcp
{
"mcpServers": {
"hjbaard-solidworks-mcp": {
"command": "uvx",
"args": [
"solidworks-mcp"
]
}
}
} {
"servers": {
"hjbaard-solidworks-mcp": {
"command": "uvx",
"args": [
"solidworks-mcp"
]
}
}
} codex mcp add hjbaard-solidworks-mcp -- uvx solidworks-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"hjbaard-solidworks-mcp": {
"type": "local",
"command": [
"uvx",
"solidworks-mcp"
],
"enabled": true
}
}
} openclaw mcp add hjbaard-solidworks-mcp --command uvx --arg solidworks-mcp
mcp_servers:
hjbaard-solidworks-mcp:
command: "uvx"
args: ["solidworks-mcp"] {
"McpServers": {
"hjbaard-solidworks-mcp": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"solidworks-mcp"
]
}
}
} assistant mcp add hjbaard-solidworks-mcp -t stdio -c uvx -a solidworks-mcp
{
"mcpServers": {
"hjbaard-solidworks-mcp": {
"command": "uvx",
"args": [
"solidworks-mcp"
]
}
}
} 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.
- 1 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 +10
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 +16
- Stability: 0.03 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Malware scan: unverified → pass ▲ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- Schema quality: pass → fail ▼ functional
- Package version: 0.4.0 → 0.5.0 functional
- 26 Sept 26 +2
- Schema quality: 4309 → 4934 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- First check of Schema quality: 100 functional
- Package version: 0.3.0 → 0.4.0 functional
- 25 Sept 26 52
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 1 Oct 2026 · Analysed pypi/solidworks-mcp@0.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 | hjbaard/SolidWorks-MCP |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/hjbaard/SolidWorks-MCP/.github/workflows/publish.yml@refs/tags/v0.5.0 |
| Rekor log index | 2978522648 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:0d1e9263d3c650d5d8430ce401e14685286b706a8c6b4b442583280556d5130d |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 28 packages
| Packages resolved | 28 |
|---|---|
| Tree resolution | Complete |
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 →
set_dimension ~78
Set a named driving dimension (e.g. 'D1@BlockExtrude') in mm, rebuild, and remeasure. This is the parametric edit at the heart of the correction loop. Every modelling tool returns its dimensions by role in `dimensions`.
| Name | Type | Req | Description |
|---|---|---|---|
| dimension_name | string | yes | – |
| value_mm | number | yes | – |
No output schema declared.
No examples provided.
set_equation ~114
Add a global equation linking dimensions, then rebuild and remeasure. A SolidWorks equation string, e.g. '"D1@BlockExtrude" = 25' or '"D1@BlockExtrude" = 2 * "D1@Sketch1"'. A global variable is '"W" = 40'; link a dimension to it with '"width@Sketch1" = "W"'. Persists a relation (unlike set_dimension). Returns mass properties.
| Name | Type | Req | Description |
|---|---|---|---|
| equation | string | yes | – |
No output schema declared.
No examples provided.
set_material ~72
Assign a material by name (e.g. "6061 Alloy", "AISI 1020", "ABS"). Makes mass and density reflect a real material instead of the 1000 kg/m³ default. Returns mass properties including density.
| Name | Type | Req | Description |
|---|---|---|---|
| database | string | – | – |
| name | string | yes | – |
No output schema declared.
No examples provided.
slice_mesh ~128
Cross-sections of an STL/3MF mesh at the given heights along axis 'x'/'y'/'z'. For modelling a part that must fit something that only exists as a mesh. Returns each section's closed loops, largest first, as polygon points (mm) ready to use as profiles. frame (3MF): 'object' (the mesh's own frame) or 'build' (as placed on the slicer's plate).
| Name | Type | Req | Description |
|---|---|---|---|
| axis | string | yes | – |
| frame | string | – | – |
| heights_mm | array | yes | – |
| path | string | yes | – |
No output schema declared.
No examples provided.
What is the SolidWorks MCP server?
SolidWorks is an MCP server listed in the public MCP registry as io.github.hjbaard/solidworks-mcp. Model, measure and verify parametric parts and assemblies in a running SolidWorks (Windows). This page covers its PyPI package (solidworks-mcp).
Is the SolidWorks MCP server safe to use?
SolidWorks scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 1 October 2026. 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 exposes 54 tools: get_status, new_part, add_box, add_extruded_profile, add_extruded_spline, and 49 more. Their descriptions and schemas cost roughly 5,290 tokens of context every time the server is loaded.
Is the SolidWorks MCP server still maintained?
SolidWorks is still listed as active in the MCP registry. We last reached this channel on 1 October 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 declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.