Conversions across 221 color spaces, tested against cited sources: CSS strings, gamut, LUTs
Nothing to run from here
Slicewise is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
94/100
trust score
16
tools declared
local
runs on your machine
—
downloads a day
What it does
Pre-print checks for Bambu Studio: GUI-faithful CLI slicing, override audit, printability.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user slicewise-mcp '--' npx -y @gjlmotea/slicewise-mcp
# 2 — ask your agent for something these tools do
# bambu_get_status, bambu_list_presets, bambu_resolve_preset and 13 more
Slicewise costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
GJAll 3 servers
gjlmotea3 servers
2 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Slicewise as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user slicewise-mcp '--' npx -y @gjlmotea/slicewise-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it asks of you
Nothing is required, but it can take BAMBU_MODEL_DIR (Folders the model tools may read from, joined with the platform path delimiter (':' on macOS and Linux, ';' on Windows). Model reads are refused when unset), BAMBU_OUTPUT_DIR (Folder for sliced and composed 3MF output; also readable by the model tools. Writing tools are refused when unset), BAMBU_STUDIO_PATH (Bambu Studio executable; resolved from the default install location when unset), BAMBU_DATA_DIR (Bambu Studio data folder holding system and user presets; resolved per platform when unset), BAMBU_SLICE_TIMEOUT_MS (Slicing timeout in milliseconds), THINGIVERSE_TOKEN (Thingiverse app token; only the Thingiverse part of model search needs it) if you want to set them.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
16 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
Reports the BambuStudio data directory, whether the slicer executable is available, preset counts,
No parameter schema on file.
Lists machine, process or filament presets. By default only presets selectable in the UI are returned;
No parameter schema on file.
Flattens a preset's inherits chain into the complete settings and records which level each value comes from.
No parameter schema on file.
Flattens two presets of the same kind and lists the settings that differ. Use it to answer questions like
No parameter schema on file.
Explains what a parameter does, its unit, its typical range, the cost of raising or lowering it, and related parameters.
No parameter schema on file.
Takes an observed symptom (warping, stringing, layer separation, elephant's foot, holes in the top surface, ...)
No parameter schema on file.
Given what you want (safe and failure-free / fast / strong under load / good surface / economical), returns ordered
No parameter schema on file.
Creates an auto-stabilised copy of the given (or currently selected) process preset that can be used directly in Bambu Studio.
No parameter schema on file.
Creates a custom preset that inherits from a system preset, in the BambuStudio user profile directory;
No parameter schema on file.
Slices with the BambuStudio CLI and reports real statistics: layer count, print time, filament weight.
No parameter schema on file.
Parses an STL (binary or ASCII), 3MF or OBJ and reports triangle count, bounding box, volume, surface area,
No parameter schema on file.
Finds problems visible before slicing: exceeding the build volume, floating bodies that do not touch the plate,
No parameter schema on file.
Measures the smallest clearance between the parts in a 3MF or OBJ, to judge whether a print-in-place mechanism will fuse when printed.
No parameter schema on file.
Builds a Bambu project 3MF from a base body STL plus extra parts. A negative part (negative_part) cuts away where it overlaps,
No parameter schema on file.
Reads the objects and parts from a Bambu project 3MF, including each part's subtype and per-part settings.
No parameter schema on file.
Searches for models across platforms. Thingiverse uses its official API (requires THINGIVERSE_TOKEN).
No parameter schema on file.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Slicewise or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 94 / 100
Release 0.1.0 · scanned 8 Nov 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score94
Findings1 threat · 0 capability
Capabilityhigh
Coveragesource
Verificationsource
Surface digestd94fd3723d513c498456cc887364f5177bc8c861353121c6a483567c86af4bca
Score vectorthreat 100 → client 94
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (16 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. high is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| bambu_get_status | no tags | |
| bambu_list_presets | no tags | |
| bambu_resolve_preset | no tags | |
| bambu_compare_presets | no tags | |
| bambu_describe_parameters | no tags | |
| bambu_diagnose | no tags | |
| bambu_plan_settings | no tags | |
| bambu_optimize_print_in_place | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| bambu_save_user_preset | state-write | state-write: declares readOnlyHint: false |
| bambu_slice | state-write | state-write: declares readOnlyHint: false |
| bambu_inspect_model | no tags | |
| bambu_check_printability | no tags | |
| bambu_measure_clearance | no tags | |
| bambu_compose_model | state-write | state-write: declares readOnlyHint: false |
| bambu_inspect_project | no tags | |
| bambu_search_models | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digestd94fd3723d513c49
Scanned2026-11-08
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.1.0. Pin a release below and the command asks for exactly that one.
0.1.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Slicewise can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.