SlicerBridge
PYPI · SLICERBRIDGE
A Rosetta Stone for multicolor 3MF files: one project in, a checked file for every printer out.
Available components
Last scanned (1 day ago)
Scores higher than 87% 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 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
- 1 of 29 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to UnicornGraveyard/SlicerBridge). View diagnostics → Pass
- Clear OSI-approved license (GPL-3.0-or-later).Pass
- Actively maintained (last published 4 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability64
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 974 tokens (~162/item across 6 items; 6 tools + 0 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 Management30
- Stability observed for 9 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 2 Nov 26 −14
- Malware scan: pass → unverified ▼ security
- 1 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 31 Oct 26 −14
- Malware scan: pass → unverified ▼ security
- Package version: 0.4.1 → 0.4.2 functional
- 29 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- Security disclosure: pass → unverified ▼ functional
- Package version: 0.3.1 → 0.4.1 functional
- Package version: 0.3.1 → 0.4.0 functional
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- Package version: 0.2.0 → 0.3.1 functional
- Package version: 0.2.0 → 0.3.0 functional
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/slicerbridge@0.4.2
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 | UnicornGraveyard/SlicerBridge |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/UnicornGraveyard/SlicerBridge/.github/workflows/release.yml@refs/tags/v0.4.2 |
| Rekor log index | 3609045891 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:6264d9df437ce737d7a2c798f3d47926e2d32b1a4d1b47ee82977758405c4f9d |
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 29 packages
| Packages resolved | 29 |
|---|---|
| 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 →
brand_check ~133
Slice each file in the slicer its printer's maker ships (Creality Print, ElegooSlicer, Anycubic Slicer Next, Flash Studio, QIDI Studio), where installed, and report what that slicer makes of it.
| Name | Type | Req | Description |
|---|---|---|---|
| paths | array | yes | .3mf files, or folders of them. |
| printers | string | – | Which printers: 'all', a set (popular), a vendor (bambu, creality, elegoo, anycubic, flashforge, qidi, wondermaker, prusa, snapmaker), or printer keys from list_printers, comma-separated. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
convert_model ~333
Write a ready file per printer for a multicolor .3mf project (from Bambu Studio, OrcaSlicer, a maker's fork, or a file SlicerBridge wrote), each one checked before it is kept. Files go in <out_dir>/<name>/, named '<prefix><name> - <printer>.3mf', or '<prefix><name> - <printer> - <suffix>.3mf' with a suffix. A printer the model can't go to (more colors than it holds, an unknown filament type) is refused with the reason; nothing wrong is written.
| Name | Type | Req | Description |
|---|---|---|---|
| model_path | string | yes | Path to the .3mf project. |
| name | string | – | The model's name in file names; default: the file's name, less any printer in it. |
| out_dir | string | – | Output folder; default: an 'out' folder beside the model. |
| prefix | string | – | Text before every file name, e.g. 'My Shop - '. |
| printers | string | – | Which printers: 'all', a set (popular), a vendor (bambu, creality, elegoo, anycubic, flashforge, qidi, wondermaker, prusa, snapmaker), or printer keys from list_printers, comma-separated. |
| slice_first | boolean | – | Slice each file in its slicer before keeping it (a minute or two per printer). |
| suffix | string | – | Text after the printer in every file name, e.g. 'My Shop' for 'Dragon - Prusa XL - My Shop.3mf'. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
doctor ~25
Which slicers SlicerBridge finds, their versions, and where it keeps its templates.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
inspect_model ~123
Describe a multicolor .3mf project: its palette, the filament slots it actually uses, each plate's size, and whether it fits each printer's bed (and at what scale if not).
| Name | Type | Req | Description |
|---|---|---|---|
| model_path | string | yes | Path to the .3mf project. |
| printers | string | – | Which printers: 'all', a set (popular), a vendor (bambu, creality, elegoo, anycubic, flashforge, qidi, wondermaker, prusa, snapmaker), or printer keys from list_printers, comma-separated. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_printers ~99
Every printer SlicerBridge writes for: its key, name, engine, slicer, the colors it holds, and the sets it's in.
| Name | Type | Req | Description |
|---|---|---|---|
| printers | string | – | Which printers: 'all', a set (popular), a vendor (bambu, creality, elegoo, anycubic, flashforge, qidi, wondermaker, prusa, snapmaker), or printer keys from list_printers, comma-separated. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
verify_files ~95
Re-run SlicerBridge's checks on files it wrote (colors, paint, plates, size, settings), and optionally slice each one.
| Name | Type | Req | Description |
|---|---|---|---|
| paths | array | yes | .3mf files, or folders of them. |
| slice_files | boolean | – | Also slice each file in its slicer (a minute or two each). |
| source_path | string | – | The project they were made from; enables the color and size checks. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
How do I install the SlicerBridge MCP server?
SlicerBridge runs locally as a PyPI package, launched with uvx slicerbridge. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · slicerbridge
claude mcp add unicorngraveyard-slicerbridge -- uvx slicerbridge
What is the SlicerBridge MCP server?
SlicerBridge is an MCP server listed in the public MCP registry as io.github.UnicornGraveyard/slicerbridge. A Rosetta Stone for multicolor 3MF files: one project in, a checked file for every printer out. This page covers its PyPI package (slicerbridge).
Is the SlicerBridge MCP server safe to use?
SlicerBridge scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 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 SlicerBridge MCP server expose?
SlicerBridge exposes 6 tools: list_printers, inspect_model, convert_model, verify_files, brand_check, doctor. Their descriptions and schemas cost roughly 808 tokens of context every time the server is loaded.
Is the SlicerBridge MCP server still maintained?
SlicerBridge 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 SlicerBridge MCP server under?
SlicerBridge declares the GPL-3.0-or-later licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.