# MeshMend (mcpb · meshmend-mcp-0.1.0.mcpb)

Check and repair STL and 3MF meshes on your own computer: holes, flipped faces, inside-out shells.

- Trust score: 39/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-17

## Components

- mcpb · `meshmend-mcp-0.1.0.mcpb`: 39/100 (this document), [markdown](https://verifymcp.io/servers/keith-cy-meshmend-mcp/meshmend-mcp.md), [page](https://verifymcp.io/servers/keith-cy-meshmend-mcp/meshmend-mcp)

## Channel facts

- Registry: `mcpb`
- Package: `https://github.com/Keith-CY/meshmend-mcp/releases/download/v0.1.0/meshmend-mcp-0.1.0.mcpb`
- Version: `0.1.0`
- Transport: `stdio`
- SHA-256: `cd047de0ed5769523886f31a639d2ba8a231b8391f75483d4a3b7a75ccd86faf`

## 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-10-17.

- **Supply Chain Security**: 0/100
  - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  - Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
- **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 0 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 65/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1115 tokens (~371/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 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.

**Unverified: 2 categories.** Categories scored 0 because we could not verify them: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the MeshMend MCP server?

MeshMend ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, cd047de0ed5769523886f31a639d2ba8a231b8391f75483d4a3b7a75ccd86faf; the commands to do that are on this page. If it does not match, do not open it.

- Download bundle: `https://github.com/Keith-CY/meshmend-mcp/releases/download/v0.1.0/meshmend-mcp-0.1.0.mcpb`
- SHA-256: `cd047de0ed5769523886f31a639d2ba8a231b8391f75483d4a3b7a75ccd86faf`

### Verify on macOS / Linux

```bash
echo "cd047de0ed5769523886f31a639d2ba8a231b8391f75483d4a3b7a75ccd86faf  meshmend-mcp-0.1.0.mcpb" | shasum -a 256 -c
```

### Verify on Windows (PowerShell)

```powershell
(Get-FileHash -Algorithm SHA256 .\meshmend-mcp-0.1.0.mcpb).Hash -eq "cd047de0ed5769523886f31a639d2ba8a231b8391f75483d4a3b7a75ccd86faf"
```

## 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-10-16 (score 39)

First indexed and scored.

## MCP tools (3)

### `check_mesh` (~294 tokens)

Check an STL or 3MF mesh

Use this when the user has an STL or 3MF file on their computer and asks whether it is printable, watertight or manifold, or why a slicer or printer complains about it: holes, open edges, gaps, flipped normals, inside-out faces, non-manifold edges or vertices, duplicate or zero-area triangles. Reads the file locally (it is never uploaded) and reports size in mm, triangle and shell counts, each problem with its count, and a verdict (ok / repairable / partly_repairable / needs_manual_review) based on a trial repair in memory, so it can say whether repair_mesh will actually fix the file. Read-only: nothing is written. Does not check self-intersections, wall thickness, overhangs or supports. Limits: 30 MiB and 250,000 triangles; 3MF build items and units are read from the file.

Input parameters:

- `item` (integer): 3MF only: the index of one build item (from check_mesh’s item list). Omit to use all build items together.
- `path` (string, required): Path of the file on this computer. Absolute paths are safest; ~ is expanded, and relative paths are resolved from the server’s working directory.
- `unit` (string): STL only: the unit the STL coordinates are in (STL files do not say). Default mm. Results are always in millimetres.

Output parameters:

- `file` (object)
- `nextStep` (string)
- `repairOutlook` (object)
- `report` (object)
- `warnings` (array)

### `repair_mesh` (~400 tokens)

Repair an STL or 3MF mesh

Use this when the user wants a broken STL or 3MF fixed for 3D printing (after check_mesh, or when they ask to repair, fix, make watertight or close holes). Writes a repaired binary STL (millimetres) next to the input or at output_path and never overwrites the original. It removes duplicate and zero-area faces, makes face winding consistent, turns inside-out shells outward and, with fill_holes: true, caps flat (planar) holes no wider than max_hole_span_mm. It is deliberately conservative: it never welds nearby vertices, never splits non-manifold geometry, leaves curved or larger holes open, and does not fix self-intersections, wall thickness or supports; those are reported for manual review. Runs locally; nothing is uploaded.

Input parameters:

- `fill_holes` (boolean): Cap flat (planar) holes. Default false, because some openings are intentional.
- `item` (integer): 3MF only: the index of one build item (from check_mesh’s item list). Omit to use all build items together.
- `max_hole_span_mm` (number): Largest hole to cap, as the diagonal of its bounding box in mm. Default 20, as on the website.
- `output_path` (string): Where to save the result; must end in .stl and its folder must exist. Default: next to the input, with a new name that never replaces an existing file.
- `overwrite` (boolean): Replace output_path if it already exists. Default false. The input file is never replaced.
- `path` (string, required): Path of the file on this computer. Absolute paths are safest; ~ is expanded, and relative paths are resolved from the server’s working directory.
- `unit` (string): STL only: the unit the STL coordinates are in (STL files do not say). Default mm. Results are always in millimetres.

Output parameters:

- `after` (object)
- `before` (object)
- `changes` (object)
- `file` (object)
- `nextStep` (string)
- `output` (object)
- `settings` (object)
- `warnings` (array)

### `convert_3mf_to_stl` (~244 tokens)

Convert 3MF to STL

Use this when the user has a 3MF file (from a slicer such as Bambu Studio, PrusaSlicer or Cura, or a CAD export) and needs an STL, for all build items together or one item. Applies the 3MF’s build transforms and unit, and writes a binary STL in millimetres without changing the geometry; colours, materials and print settings are not carried over. Also reports whether the result is watertight. Never overwrites the 3MF. Runs locally; nothing is uploaded.

Input parameters:

- `item` (integer): 3MF only: the index of one build item (from check_mesh’s item list). Omit to use all build items together.
- `output_path` (string): Where to save the result; must end in .stl and its folder must exist. Default: next to the input, with a new name that never replaces an existing file.
- `overwrite` (boolean): Replace output_path if it already exists. Default false. The input file is never replaced.
- `path` (string, required): Path of the .3mf file on this computer (absolute is safest).

Output parameters:

- `file` (object)
- `nextStep` (string)
- `output` (object)
- `report` (object)
- `warnings` (array)

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/keith-cy-meshmend-mcp/meshmend-mcp#diagnostics

## Score history

- 2026-10-17: 39
- 2026-10-16: 39

## Common questions

### What is the MeshMend MCP server?

MeshMend is an MCP server listed in the public MCP registry as io.github.Keith-CY/meshmend-mcp. Check and repair STL and 3MF meshes on your own computer: holes, flipped faces, inside-out shells. This page covers its MCPB bundle (https://github.com/Keith-CY/meshmend-mcp/releases/download/v0.1.0/meshmend-mcp-0.1.0.mcpb).

### Is the MeshMend MCP server safe to use?

MeshMend scores 39 out of 100 on VerifyMCP. 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 MeshMend MCP server expose?

MeshMend exposes 3 tools: check_mesh, repair_mesh, convert_3mf_to_stl. Their descriptions and schemas cost roughly 938 tokens of context every time the server is loaded.

### What licence is the MeshMend MCP server under?

MeshMend 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

- Repository: https://github.com/Keith-CY/meshmend-mcp
- Website: https://mesh-mend.pages.dev/
- Changelog RSS feed: https://verifymcp.io/servers/keith-cy-meshmend-mcp/meshmend-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/keith-cy-meshmend-mcp/meshmend-mcp.json
- HTML version of this page: https://verifymcp.io/servers/keith-cy-meshmend-mcp/meshmend-mcp