Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

KerfScript

NPM · @MYLASERTOOLS/KERFSCRIPT-MCP · 2 COMPONENTS

Write, check and render parametric laser-cutting designs in KerfScript, as SVG or DXF.

67 Trust /100

Last scanned (1 hour ago)

Scores higher than 34% of npm servers

Category Design and Media

Trust breakdown (7 categories)

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 Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
  • 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 3 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability59
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 381 tokens (~95/item across 4 items; 4 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
  • Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 13% 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
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 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
Changelog

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.

  • 4 Nov 26 +1

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

  • 2 Nov 26 +1

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

  • 1 Nov 26 65

    First indexed and scored.

Diagnostics

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 npm/@mylasertools/kerfscript-mcp@0.1.1

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 92 packages
Packages resolved 92
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 4 exposed · ~329 tokens

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 →

Tool Tokens
kerfscript_docs ~57

Read KerfScript language and JavaScript integration documentation for building laser-cutting generators. Omit topic to list guides. Long guides are paginated with nextOffset.

NameTypeReqDescription
offsetinteger––
topicstring––

No output schema declared.

No examples provided.

kerfscript_examples ~60

Find working parametric laser-cutting examples by title, id or tags. Supply an id from the results to get its .kerf source.

NameTypeReqDescription
idstring––
offsetinteger––
querystring––

No output schema declared.

No examples provided.

kerfscript_parameters ~40

Extract editable settings and customizer ranges from .kerf source to build a generator UI. Parses without rendering geometry.

NameTypeReqDescription
sourcestringyes–

No output schema declared.

No examples provided.

kerfscript_render ~172

Render .kerf source to SVG or DXF files, one per sheet, with part sizes, layers and warnings. Uses millimetres and bundled Atkinson font. No filesystem or network imports. Bounded to 100 parts and 10 sheets. For production generators install @mylasertools/kerfscript locally.

NameTypeReqDescription
formatstring––
gapnumber––
kerfnumber––
layoutstring––
librariesobject–Optional virtual libraries keyed by the exact use/include path. No files or URLs are fetched.
marginnumber––
paramsobject––
sheetarray––
sourcestringyesKerfScript program. Lengths are millimetres; angles are degrees.

No output schema declared.

No examples provided.

Install

How do I install the KerfScript MCP server?

KerfScript runs locally as an npm package, launched with npx -y @mylasertools/kerfscript-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @mylasertools/kerfscript-mcp

# add to Claude Code
claude mcp add com-mylasertools-kerfscript -- npx -y @mylasertools/kerfscript-mcp
Common questions

What is the KerfScript MCP server?

KerfScript is an MCP server listed in the public MCP registry as com.mylasertools/kerfscript. Write, check and render parametric laser-cutting designs in KerfScript, as SVG or DXF. This page covers its npm package (@mylasertools/kerfscript-mcp).

Is the KerfScript MCP server safe to use?

KerfScript scores 67 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 KerfScript MCP server expose?

KerfScript exposes 4 tools: kerfscript_docs, kerfscript_examples, kerfscript_parameters, kerfscript_render. Their descriptions and schemas cost roughly 329 tokens of context every time the server is loaded.

Is the KerfScript MCP server still maintained?

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

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