PartCAD
PYPI · PARTCAD
Inspect, render, test and export the parts and assemblies of PartCAD hardware packages
Available components
Last scanned (22 hours ago)
Scores higher than 56% of PyPI servers
Category IoT and Hardware
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 Security26
- Malware scan not yet available for this package.Unverified
- CVE check failed: a known high-severity CVE affects filelock 3.32.0, a direct dependency. A fixed version is available. View diagnostics → Fail
- Declares code that runs automatically (its declared build backend, an in-tree build backend) and that we could not recognise. It may be perfectly ordinary, but we have not established what it does. View diagnostics → Partial
- 7 of 69 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 2 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability76
- 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 1954 tokens (~139/item across 14 items; 12 tools + 2 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 Management50
- Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 14 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
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.
- 4 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 1 Nov 26 −14
- Malware scan: pass → unverified ▼ security
- Package version: 0.8.235 → 0.8.273 functional
- 30 Oct 26 +16
- Malware scan: unverified → pass ▲ security
- 29 Oct 26 0
- CVE-2026-112938 affects this package: high ▼ security
- CVE-2026-112915 affects this package: high ▼ security
- CVE-2026-112936 affects this package: high ▼ security
- CVE-2026-112911 affects this package: high ▼ security
- CVE-2026-112910 affects this package: high ▼ security
- CVE-2026-112935 affects this package: high ▼ security
- CVE-2026-112909 affects this package: high ▼ security
- CVE-2026-112939 affects this package: high ▼ security
- CVE-2026-112908 affects this package: high ▼ security
- 28 Oct 26 −14
- Malware scan: pass → unverified ▼ security
- 25 Oct 26 +16
- Malware scan: unverified → pass ▲ security
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 4 Nov 2026 · Analysed pypi/partcad@0.8.273
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Install scripts 2 scripts
| Hook | Tier | Command |
|---|---|---|
| build_backend | unreviewed | partcad_build_backend |
| backend_path | unreviewed | <in-tree backend, unreviewed> |
Background: Why install scripts are a supply-chain risk →
Vulnerabilities 12 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-567q-5qvw-pf92 | CVE-2026-112907 | low | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L | yes |
| GHSA-6627-m3xw-93mp | CVE-2026-112908 | medium | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:L | yes |
| GHSA-69hj-f68j-2879 | CVE-2026-112909 | medium | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N | yes |
| GHSA-8mx5-7m5m-r77g | CVE-2026-112910 | medium | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L | yes |
| GHSA-9c4x-gm8v-wgc4 | CVE-2026-112911 | medium | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:H | yes |
| GHSA-9vhv-jxww-xfm5 | CVE-2026-112913 | low | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L | yes |
| GHSA-cwqr-hh33-gh44 | CVE-2026-112915 | medium | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-fq56-3cx3-fjxp | CVE-2026-112935 | medium | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N | yes |
| GHSA-j8f7-rjxc-mr56 | CVE-2026-112936 | medium | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L | yes |
| GHSA-m462-7rxw-wvpg | CVE-2026-112938 | medium | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:H | yes |
| GHSA-rfpc-qcw5-3pc4 | CVE-2026-112939 | medium | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N | yes |
| GHSA-v4x8-3wr5-3wq8 | CVE-2026-112940 | high | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 69 packages
| Packages resolved | 69 |
|---|---|
| Stale | 6 |
| No linked repository | 1 |
| 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 →
bom Bill of materials ~131
What has to be bought or made to build a part, an assembly or a scene. `pc bom --json`.
| Name | Type | Req | Description |
|---|---|---|---|
| object | string | yes | The object: its name in the package, or fully qualified as '//package/path:name'. A name with '...' in its package ('//pub/examples...:bolt') reaches every package below that one. |
| package | – | – | The package, as '//package/path' or relative to the workspace's own; the workspace's own package when left out. |
| params | – | – | Values for the object's declared parameters, by name ('-p name=value' on the command line). |
No output schema declared.
No examples provided.
execute Run a daemon method ~155
Run any PartCAD daemon method -- everything the command line can do, and what the IDE asks for. The result carries the method's answer and its log.
| Name | Type | Req | Description |
|---|---|---|---|
| method | string | yes | The method, as list_methods names it, such as 'cae.analyze'. |
| params | – | – | Its parameters, as `pc` sends them: 'package' and 'object' for what it acts on, and 'params' for the values of the object's own parameters, as {name: value} or as ['name=value', ...] ('-p name=value'… |
No output schema declared.
No examples provided.
export Write an object to a file ~259
Export or render one object to a file in the workspace. `pc export` / `pc render` for one object, written where the agent says.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | yes | The file type: step, stl, 3mf, obj, gltf, brep, png, svg, ... |
| kind | – | – | What the object is. Looked up from its name when left out, which is the usual way to call this. |
| object | string | yes | The object: its name in the package, or fully qualified as '//package/path:name'. A name with '...' in its package ('//pub/examples...:bolt') reaches every package below that one. |
| options_package | – | – | A package whose 'export:' or 'render:' section implements the file type. |
| package | – | – | The package, as '//package/path' or relative to the workspace's own; the workspace's own package when left out. |
| params | – | – | Values for the object's declared parameters, by name ('-p name=value' on the command line). |
| path | string | yes | Where to write it, relative to the workspace: a file, or an existing directory to write it into under the name PartCAD chooses. Overwrites what is there. |
No output schema declared.
No examples provided.
info Show an object's declaration ~163
Show an object's configuration, parameters and properties, or the package's when no object is named. `pc info`.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | – | – | What the object is. Looked up from its name when left out, which is the usual way to call this. |
| object | – | – | The object: its name in the package, or fully qualified as '//package/path:name'. A name with '...' in its package ('//pub/examples...:bolt') reaches every package below that one. The package itself… |
| package | – | – | The package, as '//package/path' or relative to the workspace's own; the workspace's own package when left out. |
| params | – | – | Values for the object's declared parameters, by name ('-p name=value' on the command line). |
No output schema declared.
No examples provided.
instructions Assembly instructions ~165
The step-by-step build of an assembly: what goes where, in which order, with which parts. `pc instructions`, as data. The user's Build vs Buy choices on this machine are applied.
| Name | Type | Req | Description |
|---|---|---|---|
| object | string | yes | The object: its name in the package, or fully qualified as '//package/path:name'. A name with '...' in its package ('//pub/examples...:bolt') reaches every package below that one. |
| package | – | – | The package, as '//package/path' or relative to the workspace's own; the workspace's own package when left out. |
| params | – | – | Values for the object's declared parameters, by name ('-p name=value' on the command line). |
| subassemblies | boolean | – | Also write the steps of the subassemblies. |
No output schema declared.
No examples provided.
lint Lint a package ~70
Check a package's partcad.yaml, ASSY files and scripts for mistakes. `pc lint`.
| Name | Type | Req | Description |
|---|---|---|---|
| package | – | – | The package, as '//package/path' or relative to the workspace's own; the workspace's own package when left out. |
| recursive | boolean | – | Also lint the packages below this one. |
No output schema declared.
No examples provided.
list_methods List daemon methods ~44
The methods the PartCAD daemon serves, each with a one-line summary, for use with execute.
| Name | Type | Req | Description |
|---|---|---|---|
| filter | – | – | Only methods whose name or summary contains this, ignoring case. |
No output schema declared.
No examples provided.
list_objects List objects ~99
List the packages, parts, sketches, assemblies, scenes, interfaces, materials or software of a package. `pc list <kind>`. The listing is in the log of the result.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | What to list. |
| package | – | – | The package, as '//package/path' or relative to the workspace's own; the workspace's own package when left out. |
| recursive | boolean | – | Also list the packages below this one. |
No output schema declared.
No examples provided.
render Look at an object ~238
Render one part, assembly, scene or sketch and return the picture. `pc render`, returned instead of written. The first render of an object builds it, which can take minutes.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | The file type: png (the default) and jpg come back as an image, svg as text; anything else, such as pdf or dxf, is better written with export. |
| kind | – | – | What the object is. Looked up from its name when left out, which is the usual way to call this. |
| object | string | yes | The object: its name in the package, or fully qualified as '//package/path:name'. A name with '...' in its package ('//pub/examples...:bolt') reaches every package below that one. |
| options_package | – | – | A package whose 'render:' section implements the file type, such as a drawing style. |
| package | – | – | The package, as '//package/path' or relative to the workspace's own; the workspace's own package when left out. |
| params | – | – | Values for the object's declared parameters, by name ('-p name=value' on the command line). |
No output schema declared.
No examples provided.
search Search objects ~140
Find parts, sketches, assemblies, scenes, interfaces or packages by keyword or by interface. `pc search`. The matches are in the log of the result.
| Name | Type | Req | Description |
|---|---|---|---|
| interface | – | – | Only objects that implement this interface, or one derived from it. |
| keyword | string | – | Words to look for in names and descriptions. |
| kind | string | – | What to look for. |
| package | – | – | Where to look; the workspace root, '//', when left out. '//pub' is the public catalog. |
| recursive | boolean | – | Also look in the packages below. Below '//pub' that is the whole public catalog, fetched over the network the first time. |
No output schema declared.
No examples provided.
test Test objects ~148
Check objects against the requirements and tests they declare. `pc test`. ok is false when any check failed, and the errors say which.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | – | – | What the object is. Looked up from its name when left out, which is the usual way to call this. |
| object | – | – | The object to test; every object of the package when left out. |
| package | – | – | The package, as '//package/path' or relative to the workspace's own; the workspace's own package when left out. |
| params | – | – | Values for the object's declared parameters, by name ('-p name=value' on the command line). |
| recursive | boolean | – | Also test the packages below this one. |
No output schema declared.
No examples provided.
version PartCAD version ~26
The version of this server and of the daemon serving the workspace, which should be the same.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the PartCAD MCP server?
PartCAD runs locally as a PyPI package, launched with uvx partcad. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · partcad
claude mcp add partcad-partcad -- uvx partcad
What is the PartCAD MCP server?
PartCAD is an MCP server listed in the public MCP registry as io.github.partcad/partcad. Inspect, render, test and export the parts and assemblies of PartCAD hardware packages. This page covers its PyPI package (partcad).
Is the PartCAD MCP server safe to use?
PartCAD scores 56 out of 100 on VerifyMCP. We recorded 12 known advisories against it as of 4 November 2026. 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 PartCAD MCP server expose?
PartCAD exposes 12 tools: list_objects, info, render, export, test, and 7 more. Their descriptions and schemas cost roughly 1,638 tokens of context every time the server is loaded.
Is the PartCAD MCP server still maintained?
PartCAD is still listed as active in the MCP registry. We last reached this channel on 4 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 PartCAD MCP server under?
PartCAD declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.