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.

Kiln

PYPI · KILN3D · SCANNED SEP 23

Kiln MCP server for agents: design, slice, print, monitor, and recover physical objects safely.

Available components

−15 this week 29 Trust /100
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 Security50
  • Malware scan not yet available for this package.Unverified
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs setuptools.build_meta at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
  • 4 of 50 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-or-later).Pass
  • Actively maintained (last published 34 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability0
  • Schema quality not yet verified: the captured schema was too large for us to store in full, so we will not judge it on a partial copy.Unverified
Stability & Change Management0
  • Stability not yet verified: the captured schema was too large for us to store in full, and comparing a partial copy would report our own trimming as a change.Unverified
Tool Coverage0
  • Tool coverage not yet verified: the captured tool definitions were too large for us to store in full, so we will not judge them on a partial copy.Unverified
Tool Safety0
  • Tool safety not yet verified: the captured tool definitions were too large for us to store in full, and the trim removes the very descriptions this category reads.Unverified
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
  • Supports UI / widget rendering.Pass

Unverified: 4 categories

Categories scored 0 because our sandbox run of this package has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →

Install

How do I install the Kiln MCP server?

Kiln runs locally as a PyPI package, launched with uvx kiln3d. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · kiln3d

# add to Claude Code
claude mcp add codeofaxel-kiln -- uvx kiln3d
// .cursor/mcp.json
{
  "mcpServers": {
    "codeofaxel-kiln": {
      "command": "uvx",
      "args": [
        "kiln3d"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "codeofaxel-kiln": {
      "command": "uvx",
      "args": [
        "kiln3d"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add codeofaxel-kiln -- uvx kiln3d
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "codeofaxel-kiln": {
      "type": "local",
      "command": [
        "uvx",
        "kiln3d"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add codeofaxel-kiln --command uvx --arg kiln3d
# ~/.hermes/config.yaml
mcp_servers:
  codeofaxel-kiln:
    command: "uvx"
    args: ["kiln3d"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "codeofaxel-kiln": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "kiln3d"
      ]
    }
  }
}
# add to Vellum
assistant mcp add codeofaxel-kiln -t stdio -c uvx -a kiln3d
// mcp.json
{
  "mcpServers": {
    "codeofaxel-kiln": {
      "command": "uvx",
      "args": [
        "kiln3d"
      ]
    }
  }
}
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.

  • 23 Sept 26 −15
    • Malware scan: pass → unverified security
  • 15 Sept 26 +15
    • Malware scan: unverified → pass security
  • 14 Sept 26 −15
    • Malware scan: pass → unverified security
  • 12 Sept 26 +15
    • Malware scan: unverified → pass security
  • 11 Sept 26 −15
    • Malware scan: pass → unverified security
  • 27 Aug 26 +1

    No change was recorded against any check on this day. Supply Chain Security went from 99 to 100.

  • 26 Aug 26 −1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 20 Aug 26 0
    • Malware scan: unverified → pass security
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 23 Sept 2026 · Analysed pypi/kiln3d@1.4.1

Provenance No attestation

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

Result No attestation
Ecosystem pypi

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted setuptools.build_meta

Background: Why install scripts are a supply-chain risk →

Dependencies 50 packages
Packages resolved 50
Stale 3
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 468 exposed · ~92,016 tokens partial

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
uptime_report ~60

No description provided.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

validate_and_prepare ~310

No description provided.

NameTypeReqDescription
input_pathstringyes
materialstring
printer_idstring

Structured output declared, but exposes no named fields.

No examples provided.

validate_and_prepare_mesh ~528

No description provided.

NameTypeReqDescription
auto_repairboolean
auto_scaleboolean
build_volume_x
build_volume_y
build_volume_z
file_pathstringyes
layer_heightnumber
materialstring
min_printability_scoreinteger
nozzle_diameternumber
printer_idstring

No output schema declared.

No examples provided.

validate_assembly ~184

No description provided.

NameTypeReqDescription
assembly_jsonstringyes
printer_id

No output schema declared.

No examples provided.

validate_design_for_requirements ~152

No description provided.

NameTypeReqDescription
file_pathstringyes
material
requirementsstringyes

No output schema declared.

No examples provided.

validate_gcode ~164

No description provided.

NameTypeReqDescription
commandsstringyes

No output schema declared.

No examples provided.

validate_gcode_safe ~106

No description provided.

NameTypeReqDescription
commandsstringyes
printer_idstring

No output schema declared.

No examples provided.

validate_generated_mesh ~80

No description provided.

NameTypeReqDescription
file_pathstringyes

No output schema declared.

No examples provided.

validate_openscad_code ~87

No description provided.

NameTypeReqDescription
codestringyes

No output schema declared.

No examples provided.

validate_print_quality ~131

No description provided.

NameTypeReqDescription
job_id
printer_name
save_snapshot

No output schema declared.

No examples provided.

validate_scad_parameters ~106

No description provided.

NameTypeReqDescription
material
scad_codestringyes

No output schema declared.

No examples provided.

validate_shipping_address ~175

No description provided.

NameTypeReqDescription
citystringyes
countrystringyes
postal_codestring
statestring
streetstringyes

No output schema declared.

No examples provided.

verify_audit_integrity ~58

No description provided.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

visualize_model ~457

No description provided.

NameTypeReqDescription
angles
colorstring
file_pathstringyes
heightinteger
widthinteger

No output schema declared.

No examples provided.

watch_print ~532

No description provided.

NameTypeReqDescription
cancel_at_percentnumber
max_snapshotsinteger
poll_intervalinteger
printer_name
save_to_diskboolean
snapshot_intervalinteger
stall_timeoutinteger
timeoutinteger

No output schema declared.

No examples provided.

watch_print_status ~443

No description provided.

NameTypeReqDescription
block_until_eventboolean
event_types
timeoutinteger
watch_idstringyes

No output schema declared.

No examples provided.

webcam_stream ~90

No description provided.

NameTypeReqDescription
actionstring
portinteger
printer_name

No output schema declared.

No examples provided.

wrap_gcode_as_3mf ~497

No description provided.

NameTypeReqDescription
bed_tempinteger
filament_colors
filament_typestring
filament_types
gcode_pathstringyes
hotend_tempinteger
num_filamentsinteger
resume_modeboolean
source_3mf_path
stl_path
thumbnail_path

No output schema declared.

No examples provided.

Common questions

What is the Kiln MCP server?

Kiln is an MCP server listed in the public MCP registry as io.github.codeofaxel/kiln. Kiln MCP server for agents: design, slice, print, monitor, and recover physical objects safely. This page covers its PyPI package (kiln3d).

Is the Kiln MCP server safe to use?

Kiln scores 29 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 23 September 2026. 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.

Is the Kiln MCP server still maintained?

Kiln is still listed as active in the MCP registry. We last reached this channel on 23 September 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 Kiln MCP server under?

Kiln declares the AGPL-3.0-or-later licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.