Verified conversions across 205 color spaces: CSS strings, gamut checks, .cube LUTs
Nothing to run from here
B123d Print 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
20
downloads a day
local
runs on your machine
557
downloads in 30d
What it does
Vibe CAD for 3D printing: design, check and export printable parts with build123d.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user b123d-print-mcp '--' uvx b123d-print mcp
# 2 — ask your agent for something these tools do
# list_parts, use_printer, new_part and 30 more
B123d Print costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
KDAll 1 server
KD5RYN1 server
1 category
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 B123d Print 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 uv (docs.astral.sh/uv): uvx 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 b123d-print-mcp '--' uvx b123d-print 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 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
33 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.
List the part scripts in the workspace, with the settings in effect.
No parameter schema on file.
Optional printer profile (default is generic mode). search: find printer names ("bambu a1", "prusa mk4"). name: make it active (saved in the user's config, or over HTTP and SSH in this workspace's b123d-print.toml; "generic" clears it). material: pla, petg, asa, abs, tpu or the user's own. Only…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | no | — |
| material | string | no | — |
| search | string | no | — |
Create parts/<name>/<name>.py from the template (Dims dataclass, build(d), VARIANTS, views, checks). name: lower_snake_case. example: copy a bundled example instead (see list_parts), e.g. 'hole_coupon' to calibrate hole compensation. Returns a short confirmation;
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | — |
| description | string | no | — |
| example | string | no | — |
| show_code | boolean | no | — |
Return the current code of a part script.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | — |
Replace the whole part script with code (create the part with new_part first).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | — |
| code | string | yes | — |
Run the part script (sandboxed, with a timeout) and report, per variant and part: bounding box size and min/max (mm), volume (mm^3), solid count, is_valid, the Dims values, and any error with its traceback. Writes no files. variant: key from VARIANTS ('standard' = '').
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | — |
| variant | string | no | — |
Render six views (iso, top, front, right, iso from below, bottom) as a PNG image.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | — |
| variant | string | no | — |
| parts | string | no | — |
| size | string | no | — |
| inline | boolean | no | — |
Cross-section as a PNG image, each part in its own color. plane: 'XY' (at = Z height), 'XZ' (at = Y) or 'YZ' (at = X), in mm. parts: default the assembly if the script has one (shows fit and clearances), else all printable parts; or comma-separated names.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | — |
| plane | string | yes | — |
| at | number | yes | — |
| variant | string | no | — |
| parts | string | no | — |
| size | string | no | — |
| inline | boolean | no | — |
Run the print checks: validity, overlap between assembly parts (incl. stand-ins), overhangs > 45 deg from vertical in print orientation (bed face ignored) and bridge spans, thin features (walls under one line width fail), round-topped horizontal holes, fillets on bed edges, gaps between parts…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | — |
| variant | string | no | — |
Design numbers for the design review, per printable part: size and proportions, filament (simple estimate, roughly +-20 %) and cost, print time (rough estimate), supports, shallow slopes that show layer steps, edge treatment (sharp / filleted / chamfered shares, distinct radii and chamfer sizes),…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | — |
| variant | string | no | — |
| style | string | no | — |
| up | string | no | — |
| as_json | boolean | no | — |
Export printable parts to parts/<name>/out/. Default: every part, all variants.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | — |
| variant | string | no | — |
| formats | string | no | — |
| parts | string | no | — |
| embed | boolean | no | — |
The flat faces of a printable part, for picking one for a face fit-test template (make_template kind='face'): stable ids (1 = the largest; the same geometry always gets the same ids, changed geometry may renumber), outward normal and side (bottom, top, front, back, left, right), area, center,…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | — |
| variant | string | no | — |
| part | string | no | — |
| highlight | integer/string | no | — |
| size | string | no | — |
| inline | boolean | no | — |
A fit-test template: a quick thin print cut from the real part (same hole compensation and clearances) to check size, hole pattern and mating fits before printing the whole part. kind:
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | — |
| kind | string | yes | — |
| plane | string | no | — |
| at | number | no | — |
| face | integer/string | no | — |
| center | array/string | no | — |
| size | array/string | no | — |
| thickness | number | no | — |
| label | boolean/string | no | — |
| base | boolean | no | — |
| variant | string | no | — |
| part | string | no | — |
| formats | string | no | — |
| inline | boolean | no | — |
Bring a whole part home from a remote server, in the same layout a local install writes:
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | — |
| variant | string | no | — |
| formats | string | no | — |
| embed | boolean | no | — |
Compare a part with a reference model: bounding box, volume and surface area differences, surface distances (mean, Hausdorff) after aligning orientation, an F-score, a 0-100 score and pass/fail. reference, candidate: STL, 3MF or STEP files inside the workspace, as paths relative to it (e.g.…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| reference | string | yes | — |
| candidate | string | yes | — |
| thresholds | string | no | — |
| image | boolean | no | — |
| size | string | no | — |
| inline | boolean | no | — |
Get an original model (STL, 3MF or STEP) onto the server, into parts/<part>/ref/<filename>, to remix it (the part folder may not exist yet). With data_base64 (the whole file, base64) it is stored now, up to 50 MB; that is only practical for small files, since the model has to write out every byte.…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| part | string | yes | — |
| filename | string | yes | — |
| data_base64 | string | no | — |
| overwrite | boolean | no | — |
Inspect an original model before remixing it: format, units (and whether they look wrong), size, volume, triangles and faces before/after merging coplanar triangles, how much is curved (faceted), round holes (diameter, axis, center), repairs needed, the designer/license metadata the file carries,…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| part | string | yes | — |
| file | string | yes | — |
| scale | string | no | — |
| image | boolean | no | — |
| size | string | no | — |
| inline | boolean | no | — |
For a remix: the original and the remix side by side, and the original colored by how far the remix is from it (compare's deviation view: green = unchanged, red = changed), with compare's score and metrics. The original is what build() loads with import_model, or what the script's original(d)…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | — |
| variant | string | no | — |
| size | string | no | — |
| inline | boolean | no | — |
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
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 B123d Print 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.3.16 · scanned 29 Oct 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
Findings4 threat · 0 capability
Capabilityhigh
Coveragesource
Verificationsource
Surface digest764d56312079dbb1daeb4be223a15b02089639d03008c4eb46f7648ad7241be8
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 (33 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 |
|---|---|---|
| read_guide | no tags | |
| list_parts | no tags | |
| use_printer | no tags | |
| save_setup | no tags | |
| new_part | no tags | |
| read_part | no tags | |
| write_part | no tags | |
| params | no tags | |
| set_params | no tags | |
| build_part | no tags | |
| diagnose_failure | no tags | |
| check | no tags | |
| design_metrics | no tags | |
| measure | no tags | |
| save_version | no tags | |
| list_versions | no tags | |
| restore_version | no tags | |
| upload_reference | no tags | |
| describe_model | no tags | |
| before_after | no tags | |
| check_fit | no tags | |
| hardware_list | no tags | |
| recipe | no tags | |
| render_preview | untrusted-input | untrusted-input: keyword "download" |
| section | untrusted-input | untrusted-input: keyword "download" |
| suggest_orientation | no tags | |
| export | untrusted-input | untrusted-input: keyword "fetch_url" |
| list_faces | no tags | |
| list_edges | no tags | |
| make_template | no tags | |
| download_part | untrusted-input | untrusted-input: keyword "fetch_url" |
| compare | no tags | |
| trace_outline | no tags |
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 digest764d56312079dbb1
Scanned2026-10-29
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.3.16. Pin a release below and the command asks for exactly that one.
0.3.16
28 Oct 2026
latestNo release note was published with this version.
0.3.15
25 Oct 2026
No release note was published with this version.
0.3.14
25 Oct 2026
No release note was published with this version.
0.3.13
24 Oct 2026
No release note was published with this version.
0.3.12
23 Oct 2026
No release note was published with this version.
0.3.11
22 Oct 2026
No release note was published with this version.
0.3.10
21 Oct 2026
No release note was published with this version.
0.3.9
21 Oct 2026
No release note was published with this version.
0.3.8
20 Oct 2026
No release note was published with this version.
0.3.6
20 Oct 2026
No release note was published with this version.
0.3.5
20 Oct 2026
No release note was published with this version.
0.3.4
19 Oct 2026
No release note was published with this version.
0.3.3
19 Oct 2026
No release note was published with this version.
0.3.2
undated
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
—
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 B123d Print 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.