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.

io.github.emirmrkaljevic/mesh2cad

PYPI · MESH2CAD

Mesh (STL/OBJ/PLY) to editable STEP, CadQuery or OpenSCAD: primitive fitting, fidelity report

Available components

49 Trust /100

Last scanned (12 hours ago)

Scores higher than 49% of PyPI 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 Security99
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 3 of 19 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to emirmrkaljevic/mesh2cad). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 0 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability0
  • Schema quality not yet verified: this package installed, but its server did not start, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: this package installed, but its server did not start, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: this package installed, but its server did not start, so we have no tool definitions to assess.Unverified
Tool Safety0
  • Tool safety not yet verified: this package installed, but its server did not start, so we have no tool text to scan.Unverified
Capabilities0
  • Protocol version not yet verified: this package installed, but its server did not start, so we never saw its MCP handshake.Unverified

Unverified: 5 categories

Categories scored 0 because our sandbox 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 →

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.

  • 22 Oct 26 0
    • Package version: 0.10.0 → 0.11.0 functional
  • 21 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
    • Package version: 0.9.0 → 0.10.0 functional
  • 20 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
    • Package version: 0.8.0 → 0.9.0 functional
  • 19 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
    • Package version: 0.6.0 → 0.8.0 functional
    • Package version: 0.6.0 → 0.7.0 functional
  • 18 Oct 26 0
    • Malware scan: unverified → pass ▲ security
    • Tool safety: Tool safety not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. security
    • Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
    • Capabilities: Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet. functional
    • Tool coverage: Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. functional
    • Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
    • Package version: 0.4.2 → 0.6.0 functional
    • Package version: 0.4.2 → 0.5.0 functional
  • 17 Oct 26 34

    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 22 Oct 2026 · Analysed pypi/mesh2cad@0.11.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo emirmrkaljevic/mesh2cad
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/emirmrkaljevic/mesh2cad/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3387429728
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:b290808ea6166bfdcd307663fc83f576b9ba534f6814eb0ad39fe4cf440a6fab

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted hatchling.build

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

Dependencies 19 packages
Packages resolved 19
Stale 1
No linked repository 2
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools

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 →

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.

Install

How do I install the io.github.emirmrkaljevic/mesh2cad MCP server?

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

pypi · mesh2cad

# add to Claude Code
claude mcp add emirmrkaljevic-mesh2cad -- uvx mesh2cad
Common questions

What is the io.github.emirmrkaljevic/mesh2cad MCP server?

io.github.emirmrkaljevic/mesh2cad is an MCP server listed in the public MCP registry as io.github.emirmrkaljevic/mesh2cad. Mesh (STL/OBJ/PLY) to editable STEP, CadQuery or OpenSCAD: primitive fitting, fidelity report. This page covers its PyPI package (mesh2cad).

Is the io.github.emirmrkaljevic/mesh2cad MCP server safe to use?

io.github.emirmrkaljevic/mesh2cad scores 49 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 October 2026. Its build provenance is signed and verified. 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 io.github.emirmrkaljevic/mesh2cad MCP server still maintained?

io.github.emirmrkaljevic/mesh2cad is still listed as active in the MCP registry. We last reached this channel on 22 October 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 io.github.emirmrkaljevic/mesh2cad MCP server under?

io.github.emirmrkaljevic/mesh2cad declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.