Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
CutOptim Engine 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.
99/100
trust score
8
downloads a day
local
or remote
359
downloads in 30d
What it does
Cutting optimization: 2D panels, 1D bars, timber and true-shape nesting via the CutOptim API.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user cutoptim-engine-mcp '--' npx -y @cutoptim/mcp
# 2 — ask your agent for something these tools do
# optimize_1d, optimize_wood, validate_2d and 5 more
Remote: no sign-in · Package: API key.
CutOptim Engine costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
PublisherVerified · since 2026
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one can run either way — at an address its publisher runs, or as a process under your own user, with your files and your network — and this marketplace is in the path of neither.
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 cutoptim-engine-mcp '--' npx -y @cutoptim/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Or connect to its publisher’s address
Its publisher also runs it at https://api.cutoptim.com/mcp: nothing to start on your machine, and this marketplace is not in the path.
claude mcp add --scope user --transport http cutoptim-engine-mcp https://api.cutoptim.com/mcpFree 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 CUTOPTIM_API_KEY (Your CutOptim API key (co_live_…, co_test_…, or the public demo key). Not needed for validate_*.) if you want to set it.
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
8 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.
Metered: one Engine API call. Cut lengths from bars, tubes, profiles or rolls and get the cutting pattern per bar. 1D / linear optimization (bars, profiles, tube). Cut parts of a given length from stock bars. Returns the rods used, the position of every part along each rod, the leftover length and…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| parts | array | yes | — |
| stock | array | yes | — |
| options | object | no | The 1D option set is deliberately smaller: there is no firstCut, maxCutStages or minimizeRotations, because none of them means anything on a bar. |
| engine | string | no | max is not offered here: it is a 2D (and, separately, nesting) tier, and engine: "max" on this path is a 400 before a call is charged. In 1D balanced resolves to the same packer as `heuristi |
| include | array | no | Three kinds of token. NARROWING (cutPlan, offcuts): omit the field entirely to get both; a present array keeps only the narrowing tokens it lists (an empty array drops both). ADDITIVE EXPORT (`svg |
Metered: one Engine API call. Cut timber parts grouped by cross-section from matching stock lengths. Timber optimization (cross-section-aware 1D). Cut lengths from bars that have a CROSS-SECTION. Unlike /v1/optimize/1d, where every bar can serve every part, a 50×150 part can only come out of…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| parts | array | yes | — |
| stock | array | yes | At most 50 rows. Since every cross-section needs at least one stock row, this is also the practical ceiling on cross-sections in a single job; a wider catalogue should be split into several requests. |
| options | object | no | Identical to Options1D — a cross-section changes what fits, not how a bar is cut. |
| engine | string | no | As in 1D, max is not offered here (a 400 before a call is charged). balanced resolves to the same packer as heuristic: within a section a timber job is a length problem, and free nesting has |
| include | array | no | Three kinds of token. NARROWING (cutPlan, offcuts): omit the field entirely to get both; a present array keeps only the narrowing tokens it lists (an empty array drops both). ADDITIVE EXPORT (`svg |
Free, no key needed: checks a 2D request without solving it. Same arguments as optimize_2d (field descriptions there). Validate a 2D request — free, no key, no quota, no solve. Schema-validate the SAME body /v1/optimize/2d takes, WITHOUT solving or spending a call. 200 {valid:true, warnings}…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| parts | array | yes | — |
| stock | array | yes | — |
| options | object | no | — |
| engine | string | no | — |
| include | array | no | — |
| matchedSets | no | — |
Free, no key needed: checks a 1D request without solving it. Same arguments as optimize_1d (field descriptions there). Validate a 1D request — free, no key, no quota, no solve. Schema-validate the SAME body /v1/optimize/1d takes, WITHOUT solving or spending a call. See /v1/validate/2d.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| parts | array | yes | — |
| stock | array | yes | — |
| options | object | no | — |
| engine | string | no | — |
| include | array | no | — |
Free, no key needed: checks a timber request without solving it. Same arguments as optimize_wood (field descriptions there). Validate a wood request — free, no key, no quota, no solve. Schema-validate the SAME body /v1/optimize/wood takes, WITHOUT solving or spending a call. Warnings flag parts…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| parts | array | yes | — |
| stock | array | yes | — |
| options | object | no | — |
| engine | string | no | — |
| include | array | no | — |
Free, no key needed: checks a nesting request without solving it. Same arguments as optimize_nest (field descriptions there). Validate a nest request — free, no key, no quota, no solve. Schema-validate the SAME body /v1/optimize/nest takes, WITHOUT solving or spending a call. Reports…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| parts | array | yes | — |
| stock | array | yes | — |
| options | object | no | — |
| engine | string | no | — |
| include | array | no | — |
Free (needs the key that submitted the job). Reads an engine "max" job; when it succeeded, the plan is in result. Poll an async max-engine job. Fetch the status (and, when finished, the plan) of a job submitted with engine: "max". A job is queued, then running, then succeeded (with…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| jobId | string | yes | The jobId from the 202 submission. |
Free (needs an API key). Shows the plan, the calls used and left this month, and when the period ends. The account's current-month usage and quota. Read-only. Does not consume quota and does not send rate-limit headers. The period is the UTC calendar month.
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 CutOptim Engine 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 99 / 100
Release 0.1.0 · scanned 28 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 score99
Findings0 threat · 0 capability
Capabilityminimal
Coveragesource
Verificationrepo
Surface digestaf2f16353ecdd4eb40582f863f7320ac37a02430c0ddbde9f3c1417d2777d629
Score vectorthreat 100 → client 99
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| 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 surfacenot available
Implementation sourceread
Package metadataread
Live transportnot available
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, 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. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
No tool surface was enumerated, so there is nothing to attribute a capability to.
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 digestaf2f16353ecdd4eb
Scanned2026-10-28
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 CutOptim Engine 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.