# SlicerBridge (pypi · slicerbridge)

A Rosetta Stone for multicolor 3MF files: one project in, a checked file for every printer out.

- Trust score: 84/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- pypi · `slicerbridge`: 84/100 (this document), [markdown](https://verifymcp.io/servers/unicorngraveyard-slicerbridge/slicerbridge.md), [page](https://verifymcp.io/servers/unicorngraveyard-slicerbridge/slicerbridge)

## Channel facts

- Registry: `pypi`
- Package: `slicerbridge`
- Version: `0.4.2`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it.
  - 1 of 29 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to UnicornGraveyard/SlicerBridge).
  - Clear OSI-approved license (GPL-3.0-or-later).
  - Actively maintained (last published 5 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 64/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### 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.

### Claude

```bash
claude mcp add unicorngraveyard-slicerbridge -- uvx slicerbridge
```

### Cursor

```json
{
  "mcpServers": {
    "unicorngraveyard-slicerbridge": {
      "command": "uvx",
      "args": [
        "slicerbridge"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "unicorngraveyard-slicerbridge": {
      "command": "uvx",
      "args": [
        "slicerbridge"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add unicorngraveyard-slicerbridge -- uvx slicerbridge
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "unicorngraveyard-slicerbridge": {
      "type": "local",
      "command": [
        "uvx",
        "slicerbridge"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add unicorngraveyard-slicerbridge --command uvx --arg slicerbridge
```

### Hermes

```yaml
mcp_servers:
  unicorngraveyard-slicerbridge:
    command: "uvx"
    args: ["slicerbridge"]
```

### Netclaw

```json
{
  "McpServers": {
    "unicorngraveyard-slicerbridge": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "slicerbridge"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add unicorngraveyard-slicerbridge -t stdio -c uvx -a slicerbridge
```

### Other

```json
{
  "mcpServers": {
    "unicorngraveyard-slicerbridge": {
      "command": "uvx",
      "args": [
        "slicerbridge"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 84, +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.

### 2026-11-03 (score 83, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-02 (score 68, −14)

- [security regression] Malware scan: pass → unverified

### 2026-11-01 (score 82, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-31 (score 67, −14)

- [security regression] Malware scan: pass → unverified
- [functional] Package version: 0.4.1 → 0.4.2

### 2026-10-29 (score 81, +15)

- [security improvement] Malware scan: unverified → pass
- [functional regression] Security disclosure: pass → unverified
- [functional] Package version: 0.3.1 → 0.4.1
- [functional] Package version: 0.3.1 → 0.4.0

### 2026-10-28 (score 66, +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.

### 2026-10-27 (score 65, 0)

- [functional improvement] Stability: unverified → 0.03
- [functional] Package version: 0.2.0 → 0.3.1
- [functional] Package version: 0.2.0 → 0.3.0

## MCP tools (6)

### `list_printers` (~99 tokens)

Every printer SlicerBridge writes for: its key, name, engine, slicer, the colors it holds, and the sets it's in.

Input parameters:

- `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.

Output parameters:

- `result` (string)

### `inspect_model` (~123 tokens)

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).

Input parameters:

- `model_path` (string, required): 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.

Output parameters:

- `result` (string)

### `convert_model` (~333 tokens)

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.

Input parameters:

- `model_path` (string, required): 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'.

Output parameters:

- `result` (string)

### `verify_files` (~95 tokens)

Re-run SlicerBridge's checks on files it wrote (colors, paint, plates, size, settings), and optionally slice each one.

Input parameters:

- `paths` (array, required): .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.

Output parameters:

- `result` (string)

### `brand_check` (~133 tokens)

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.

Input parameters:

- `paths` (array, required): .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.

Output parameters:

- `result` (string)

### `doctor` (~25 tokens)

Which slicers SlicerBridge finds, their versions, and where it keeps its templates.

Output parameters:

- `result` (string)

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/unicorngraveyard-slicerbridge/slicerbridge#diagnostics

## Score history

- 2026-11-05: 84
- 2026-11-04: 84
- 2026-11-03: 83
- 2026-11-02: 68
- 2026-11-01: 82
- 2026-10-31: 67
- 2026-10-30: 81
- 2026-10-29: 81
- 2026-10-28: 66
- 2026-10-27: 65
- 2026-10-26: 65

## Common questions

### 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 5 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 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 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.

## Links

- PyPI project: https://pypi.org/project/slicerbridge/
- Socket report: https://socket.dev/pypi/package/slicerbridge
- Repository: https://github.com/UnicornGraveyard/SlicerBridge
- Changelog RSS feed: https://verifymcp.io/servers/unicorngraveyard-slicerbridge/slicerbridge.xml
- Changelog JSON feed: https://verifymcp.io/servers/unicorngraveyard-slicerbridge/slicerbridge.json
- HTML version of this page: https://verifymcp.io/servers/unicorngraveyard-slicerbridge/slicerbridge