io.github.MaxEllis/orcaslicer-mcp
PYPI · ORCASLICER-MCP
Work a running OrcaSlicer with AI: slice, tune, and understand what each setting costs
Available components
Last scanned (21 hours 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 hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 32 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- 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 (AGPL-3.0-only).Pass
- Actively maintained (last published 2 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability83
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 7568 tokens (~132/item across 57 items; 56 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage78
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 33% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 57 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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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
- 3 Nov 26 0
- Schema quality: 6694 → 7568 ▼ functional
- Package version: 0.1.18 → 0.1.19 functional
- 2 Nov 26 0
- MCP protocol: Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28. functional
- Package version: 0.1.17 → 0.1.18 functional
- 1 Nov 26 0
- Provenance: unverified → fail ▼ security
- 31 Oct 26 0
- Stability: 0.97 → pass security
- 30 Oct 26 0
- Provenance: fail → unverified ▼ security
- Stability: pass → 0.97 functional
- 29 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 24 Oct 26 0
- Stability: 0.97 → pass security
- Security disclosure: unverified → fail ▼ 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 5 Nov 2026 · Analysed pypi/orcaslicer-mcp@0.1.19
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 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | Known build tool | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 32 packages
| Packages resolved | 32 |
|---|---|
| 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 →
set_object_config Set per-object config ~67
Set per-object config overrides on an object by id, e.g. {"wall_loops": 4, "sparse_infill_density": "30%"}. Atomic (nothing applied if any key is invalid).
| Name | Type | Req | Description |
|---|---|---|---|
| changes | object | yes | – |
| object_id | integer | yes | – |
No output schema declared.
No examples provided.
slice Start slicing ~101
Start slicing the current plate in the background and return immediately, without waiting for the result. The reply is 'started' (a slice began), 'already_valid' (the plate is unchanged and the last result still holds), or a conflict if a slice is already running. Fire-and-forget: poll get_slice_status for progress and stats, or cancel_slice to stop it. Prefer slice_and_wait when you want the finished stats back in one call.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
slice_and_wait Slice and wait for result ~130
Slice the current plate and block until it finishes, then return the final stats and warnings in one call. If the plate is already sliced and unchanged, it returns the existing result without re-slicing. This is the usual way to slice when you want the outcome immediately. For a non-blocking start, use slice then poll get_slice_status; to sweep one setting across values, use compare_settings.
| Name | Type | Req | Description |
|---|---|---|---|
| timeout | integer | – | Maximum seconds to wait for the slice to finish before returning the last known state. Default 300; raise it for large or textured plates that slice slowly. |
No output schema declared.
No examples provided.
transform_object Transform object ~140
Move/rotate/scale an object by id. translate=[dx,dy,dz] mm (relative), rotate=[rx,ry,rz] degrees (relative), scale=[sx,sy,sz] absolute factor. Provide at least one. On fork v2.4.2-mcp.13 and later the object then belongs to whichever plate it sits on, as after a drag in the window; list_objects shows the plate. To send an object to another plate, move_object_to_plate is simpler than working out coordinates.
| Name | Type | Req | Description |
|---|---|---|---|
| object_id | integer | yes | – |
| rotate | – | – | – |
| scale | – | – | – |
| translate | – | – | – |
No output schema declared.
No examples provided.
wait_for_printer Wait for the printer ~319
Wait until the printer reaches a point in a print, checking every 5 seconds. Returns as soon as it happens (met: true), or at the timeout with the latest status (met: false). It also returns early, with stopped_early saying why, when the printer reports a fault, when the job ends before the point it waits for (a cancelled print, say), or after losing contact ("Lost contact with the printer"). A job that completes successfully while the wait is for 'printing' or 'first_layer_done' counts as met (a one-layer print passes both at once). A met result can carry stopped_early too, for example a job that finished with an error. Waiting for 'finished' when nothing is printing returns at once with the note 'nothing is printing'. Read-only: it never sends commands.
| Name | Type | Req | Description |
|---|---|---|---|
| timeout_s | integer | – | Seconds to wait before returning the latest status. Default 300, at most 1800. Call again to keep waiting. |
| until | string | yes | What to wait for. 'heated': every heater with a target is within 3 °C of it. 'printing': extrusion has started. OctoPrint reports no extrusion, so there it means the job is running with the heaters a… |
No output schema declared.
No examples provided.
watch_events Watch OrcaSlicer events ~33
Collect live events (slice.*/config.changed/project.opened) over a bounded window.
| Name | Type | Req | Description |
|---|---|---|---|
| seconds | integer | – | – |
No output schema declared.
No examples provided.
How do I install the io.github.MaxEllis/orcaslicer-mcp server?
io.github.MaxEllis/orcaslicer-mcp runs locally as a PyPI package, launched with uvx orcaslicer-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 · orcaslicer-mcp
claude mcp add maxellis-orcaslicer-mcp -- uvx orcaslicer-mcp
What is the io.github.MaxEllis/orcaslicer-mcp server?
io.github.MaxEllis/orcaslicer-mcp is listed in the public MCP registry as io.github.MaxEllis/orcaslicer-mcp. Work a running OrcaSlicer with AI: slice, tune, and understand what each setting costs. This page covers its PyPI package (orcaslicer-mcp).
Is the io.github.MaxEllis/orcaslicer-mcp server safe to use?
io.github.MaxEllis/orcaslicer-mcp scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 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 io.github.MaxEllis/orcaslicer-mcp server expose?
io.github.MaxEllis/orcaslicer-mcp exposes 56 tools: get_status, get_config, set_config, slice, get_slice_status, and 51 more. Their descriptions and schemas cost roughly 7,537 tokens of context every time the server is loaded.
Is the io.github.MaxEllis/orcaslicer-mcp server still maintained?
io.github.MaxEllis/orcaslicer-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 io.github.MaxEllis/orcaslicer-mcp server under?
io.github.MaxEllis/orcaslicer-mcp declares the AGPL-3.0-only licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the io.github.MaxEllis/orcaslicer-mcp server?
VerifyMCP ran 16 checks on io.github.MaxEllis/orcaslicer-mcp, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.