# CutOptim Engine (npm · @cutoptim/mcp)

Cutting optimization: 2D panels, 1D bars, timber and true-shape nesting via the CutOptim API.

- Trust score: 71/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `api.cutoptim.com`: 74/100, [markdown](https://verifymcp.io/servers/cutoptim-engine/api.md), [page](https://verifymcp.io/servers/cutoptim-engine/api)
- npm · `@cutoptim/mcp`: 71/100 (this document), [markdown](https://verifymcp.io/servers/cutoptim-engine/cutoptim-mcp.md), [page](https://verifymcp.io/servers/cutoptim-engine/cutoptim-mcp)

## Channel facts

- Registry: `npm`
- Package: `@cutoptim/mcp`
- Version: `0.1.0`
- 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**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 30 of 93 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 13 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 50/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 5358 tokens (~535/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 47/100
  - Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 82/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 37% 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 10 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the CutOptim Engine MCP server?

CutOptim Engine runs locally as an npm package, launched with npx -y @cutoptim/mcp. 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 cutoptim-engine -- npx -y @cutoptim/mcp
```

### Cursor

```json
{
  "mcpServers": {
    "cutoptim-engine": {
      "command": "npx",
      "args": [
        "-y",
        "@cutoptim/mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "cutoptim-engine": {
      "command": "npx",
      "args": [
        "-y",
        "@cutoptim/mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add cutoptim-engine -- npx -y @cutoptim/mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cutoptim-engine": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@cutoptim/mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add cutoptim-engine --command npx --arg -y --arg @cutoptim/mcp
```

### Hermes

```yaml
mcp_servers:
  cutoptim-engine:
    command: "npx"
    args: ["-y", "@cutoptim/mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "cutoptim-engine": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@cutoptim/mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add cutoptim-engine -t stdio -c npx -a -y @cutoptim/mcp
```

### Other

```json
{
  "mcpServers": {
    "cutoptim-engine": {
      "command": "npx",
      "args": [
        "-y",
        "@cutoptim/mcp"
      ]
    }
  }
}
```

## 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-05 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-28 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-26 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-24 (score 65, +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-22 (score 64)

First indexed and scored.

## MCP tools (10)

### `optimize_2d` (~1197 tokens)

Optimize 2D panels

Metered: one Engine API call. Cut rectangular parts from sheets (panels, plywood, glass, sheet metal) and get the layout, cut plan and yield. 2D panel optimization. Nest rectangular parts into rectangular sheets. Returns the placement of every part, the remaining offcuts, the guillotine cut plan and the yield metrics. Parts named in `matchedSets` (grain matching) are cut side by side from one piece of board, one kerf apart; each placed member says which set and position it is.

Input parameters:

- `engine` (string): Which optimizer to run. `heuristic` is the guillotine multi-strategy packer: highest yield, every layout edge-to-edge saw-cuttable, always a full `cutPlan`. `balanced` is a MaxRects free-nesting pack…
- `include` (array): 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 (`sv…
- `matchedSets`: Matched sets (grain matching): groups of parts cut side by side from one piece of board. Send a NON-EMPTY ARRAY of sets (at most 50); members are named by `parts[].id`. Only a non-empty array switche…
- `options` (object)
- `parts` (array, required)
- `stock` (array, required)

### `optimize_1d` (~644 tokens)

Optimize 1D bars

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 the yield metrics.

Input parameters:

- `engine` (string): `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 `heurist…
- `include` (array): 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 (`sv…
- `options` (object): The 1D option set is deliberately smaller: there is no `firstCut`, `maxCutStages` or `minimizeRotations`, because none of them means anything on a bar.
- `parts` (array, required)
- `stock` (array, required)

Output parameters:

- `contractVersion` (string)
- `csv` (string)
- `cutPlan` (array|null)
- `deterministic` (boolean)
- `dxf` (string)
- `engine` (string)
- `engineVersion` (string)
- `materials` (array)
- `metrics` (object)
- `rods` (array)
- `timing` (object)
- `unmatchedMaterials` (array)
- `unplaced` (array)
- `warnings` (array)

### `optimize_wood` (~796 tokens)

Optimize timber

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 50×150 stock — so the job is split by cross-section, each section is matched to its own stock and solved separately, and the response carries both per-section and job-wide totals.

Fanning the same job out into several `/v1/optimize/1d` calls is not equivalent: it costs one call per section against your quota, moves the stock matching to your code, and cannot distinguish "no material of this section" from "did not fit" — which this endpoint reports separately as `unmatched` and `unplaced`.

\`sw` and `sh` may be given in either order: 50×100 and 100×50 are the same bar turned over and are matched as one section. The response reports the normalised short/long form.

Input parameters:

- `engine` (string): 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 ha…
- `include` (array): 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 (`sv…
- `options` (object): Identical to `Options1D` — a cross-section changes what fits, not how a bar is cut.
- `parts` (array, required)
- `stock` (array, required): 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.

Output parameters:

- `contractVersion` (string)
- `csv` (string)
- `cutPlan` (array|null)
- `deterministic` (boolean)
- `dxf` (string)
- `engine` (string)
- `engineVersion` (string)
- `metrics` (object)
- `sections` (array)
- `timing` (object)
- `unmatched` (array)
- `unplaced` (array)
- `warnings` (array)

### `optimize_nest` (~1575 tokens)

Nest true shapes

Metered: one Engine API call (needs an API key; not available with the demo key). Nest free-form polygon parts on sheets. True-shape (irregular / polygon) nesting. Pack ARBITRARY POLYGONS onto fixed sheets, letting parts interlock into each other's concave pockets — an L-bracket, a gasket, a laser-cut profile. This is a different class from the rectangular modes: a part is an outline (`polygon`, optional interior `holes`), not a width×height, so a bounding-box packer's notch-air is reclaimed. On a representative 272-part job it uses 6 sheets where the same parts by bounding box need 9 (−33 % material).

Two things the rectangular API cannot express come for free here: per-sheet EXCLUSION ZONES (`stock[].exclusions` — a defect, a clamp footprint, a pre-printed area; a `quality`-0 zone is a no-go region for any part), and true-shape holes. Material partition (`material`) and the opaque `meta` passthrough work exactly as on the other modes.

⚠️ `density` is the placed POLYGON area over used sheet area — the honest fill, with concave pockets counted as empty. It is NOT comparable to a rectangular packer's `yieldPct` (which counts each bounding box as solid and so reads higher for a worse result); the cross-comparable metric is `sheetCount` on the same parts.

A placed part carries the rigid transform (`rotation` in degrees, then `x`/`y` translation), NOT a re-emitted polygon: your input outline plus that transform reconstructs the placement exactly. Deterministic (a pinned seed); set `options.seed` to reproduce a layout.

Engines: `lbf` (default) is synchronous and instant. Besides its own pass it tries the parts restricted to the right angles they allow, and their bounding boxes packed by an exact rectangle packer — which finds grids a sampling search misses (three 500-wide parts on a 1500-wide sheet at zero spacing) — and keeps whichever ranks best; on a tie, the plan that fills its sheets front to back, then the one with fewer parts off the right angles. `max` is AS…

Input parameters:

- `engine` (string): `lbf` (default) is single-pass, synchronous and instant. `max` is ASYNCHRONOUS: 202 + poll `GET /v1/jobs/{id}`; it runs `lbf` first, then a time-budgeted search that fills sheets one at a time lookin…
- `include` (array): Additive inline export of the achieved layout. `svg` returns a self-contained, styled `<svg>` string (one titled band per sheet, parts drawn as filled polygons with holes, exclusion zones hatched); `…
- `options` (object): Solve options. All optional.
- `parts` (array, required): One or more parts to nest, one NestPart per row.
- `stock` (array, required): One or more sheet types, one NestStock per row.

### `validate_2d` (~242 tokens)

Validate a 2D request

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}` (warnings flag parts that fit no stock — an approximate, solve-free probe), or 400 with the exact bad field path. Open like `/v1/health`: validate payloads during integration before you even have a key. The engine verdict matches the optimize path exactly, `engine: "max"` included: a body this endpoint accepts is one `/v1/optimize/2d` will accept, and one it refuses (400 for an option the max tier cannot model, 503 where that tier is not enabled) is refused there too.

Input parameters:

- `engine` (string)
- `include` (array)
- `matchedSets`
- `options` (object)
- `parts` (array, required)
- `stock` (array, required)

Output parameters:

- `contractVersion` (string)
- `engineEnabled` (boolean)
- `mode` (string)
- `parts` (object)
- `stock` (object)
- `valid` (boolean)
- `warnings` (array)

### `validate_1d` (~126 tokens)

Validate a 1D request

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

Input parameters:

- `engine` (string)
- `include` (array)
- `options` (object)
- `parts` (array, required)
- `stock` (array, required)

Output parameters:

- `contractVersion` (string)
- `engineEnabled` (boolean)
- `mode` (string)
- `parts` (object)
- `stock` (object)
- `valid` (boolean)
- `warnings` (array)

### `validate_wood` (~131 tokens)

Validate a timber request

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 with no matching-section stock long enough. See `/v1/validate/2d`.

Input parameters:

- `engine` (string)
- `include` (array)
- `options` (object)
- `parts` (array, required)
- `stock` (array, required)

Output parameters:

- `contractVersion` (string)
- `engineEnabled` (boolean)
- `mode` (string)
- `parts` (object)
- `stock` (object)
- `valid` (boolean)
- `warnings` (array)

### `validate_nest` (~192 tokens)

Validate a nesting request

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 `engineEnabled` (whether the nesting engine is built into this deployment) and warns about parts whose bounding box fits no stock sheet. For `engine: "max"` the verdict matches the optimize path exactly: 400 for anything outside the preview scope, 503 where the async tier is not enabled, and otherwise a warning that the job will be asynchronous. See `/v1/validate/2d`.

Input parameters:

- `engine` (string)
- `include` (array)
- `options` (object)
- `parts` (array, required)
- `stock` (array, required)

Output parameters:

- `contractVersion` (string)
- `engineEnabled` (boolean)
- `mode` (string)
- `parts` (object)
- `stock` (object)
- `valid` (boolean)
- `warnings` (array)

### `get_job` (~240 tokens)

Get an async job

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 `result` = the same response shape a synchronous solve of that `mode` returns, carrying `engine: "max"` — a 2D plan for `mode: "2d"`, a nest for `mode: "nest"`) or `failed` (with `error`). Polling spends no quota, but the key must still be usable: a revoked key or a lapsed API subscription is refused with 403 here exactly as it is on every other authenticated path. A caller sees only its own jobs — a job id belonging to another account is reported as 401 "job not found", indistinguishable from one that does not exist, so ids cannot be probed.

Input parameters:

- `jobId` (string, required): The jobId from the 202 submission.

Output parameters:

- `createdAt` (string)
- `engine` (string)
- `error` (string)
- `finishedAt` (string|null)
- `jobId` (string)
- `mode` (string)
- `result`
- `status` (string)

### `get_usage` (~65 tokens)

Get API usage

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.

Output parameters:

- `contractVersion` (string)
- `env` (string)
- `keyClass` (string)
- `keyPrefix` (string)
- `limit` (integer)
- `periodEnd` (string)
- `plan` (string)
- `remaining` (integer)
- `used` (integer)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/cutoptim-engine/cutoptim-mcp#diagnostics

## Score history

- 2026-11-05: 71
- 2026-11-04: 70
- 2026-11-03: 70
- 2026-11-02: 69
- 2026-11-01: 69
- 2026-10-31: 68
- 2026-10-30: 68
- 2026-10-29: 67
- 2026-10-28: 67
- 2026-10-27: 66
- 2026-10-26: 66
- 2026-10-25: 65
- 2026-10-24: 65
- 2026-10-23: 64
- 2026-10-22: 64

## Common questions

### What is the CutOptim Engine MCP server?

CutOptim Engine is an MCP server listed in the public MCP registry as io.github.cutoptim/engine. Cutting optimization: 2D panels, 1D bars, timber and true-shape nesting via the CutOptim API. This page covers its npm package (@cutoptim/mcp).

### Is the CutOptim Engine MCP server safe to use?

CutOptim Engine scores 71 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. 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 CutOptim Engine MCP server expose?

CutOptim Engine exposes 10 tools: optimize_2d, optimize_1d, optimize_wood, optimize_nest, validate_2d, and 5 more. Their descriptions and schemas cost roughly 5,208 tokens of context every time the server is loaded.

### Is the CutOptim Engine MCP server still maintained?

CutOptim Engine 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 CutOptim Engine MCP server under?

CutOptim Engine declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/@cutoptim/mcp
- Socket report: https://socket.dev/npm/package/@cutoptim/mcp
- Repository: https://github.com/cutoptim/engine-mcp
- Website: https://cutoptim.com/engine/reference/guides/mcp
- Changelog RSS feed: https://verifymcp.io/servers/cutoptim-engine/cutoptim-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/cutoptim-engine/cutoptim-mcp.json
- HTML version of this page: https://verifymcp.io/servers/cutoptim-engine/cutoptim-mcp