ldraw-mcp
PYPI · LDRAW-MCP
Render LDraw/LEGO models to images with real part geometry via headless Blender + ImportLDraw
Available components
Last scanned (1 hour ago)
Scores higher than 59% of PyPI servers
Category Design and Media
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 hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 29 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 (MIT).Pass
- Actively maintained (last published 42 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 566 tokens (~94/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management77
- Stability observed for 23 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
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (67% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 5 Nov 26 −19
- Malware scan: pass → unverified ▼ security
- Stability: pass → 0.77 functional
- Package version: 0.2.3 → 0.3.1 functional
- 31 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 30 Oct 26 +1
- Stability: 0.97 → pass security
- 29 Oct 26 −16
- Malware scan: pass → unverified ▼ security
- Stability: pass → 0.97 functional
- 26 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 19 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 18 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 16 Oct 26 +1
- Stability: 0.97 → pass security
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 pypi/ldraw-mcp@0.3.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
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 29 packages
| Packages resolved | 29 |
|---|---|
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
bill_of_materials ~162
Bill of materials for an LDraw model: part x colour x quantity rows. Give `path` (a .ldr/.mpd file) or `ldr` (inline LDraw text), not both. MPD sub-models are expanded with their multiplicity, and colour 16 inherits the colour of the line that referenced the sub-model. Part descriptions and colour names come from the LDraw library when one is installed; without it the counts are the same and those fields are null. A colour code that LDConfig.ldr does not define is listed in `unknown_color_codes`, and a part the library lacks in `parts_not_in_library`.
| Name | Type | Req | Description |
|---|---|---|---|
| ldr | string | – | – |
| path | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
check_renderer ~21
Report whether the LDraw rendering stack is available and why not.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
lookup_color ~91
Look up LDraw colours in the library's LDConfig.ldr. `query` is a colour code (`4`, or a direct colour `0x2FF8800`) or part of a name (`dark blue`, `Trans_Red`). Returns code, name, RGB, edge colour, alpha and finish for each match; an unknown code returns no matches.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
render_ldraw_file ~128
Render an LDraw model file (.ldr/.mpd/.dat) to a PNG image. Views are rendered at each comma-separated azimuth (degrees) and stitched side by side. Higher samples = cleaner but slower. Bounds: resolution 32..2048 px per view, samples 1..1024, 1..8 azimuths, and resolution^2 x samples x views at most 2**27.
| Name | Type | Req | Description |
|---|---|---|---|
| azimuths | string | – | – |
| path | string | yes | – |
| resolution | integer | – | – |
| samples | integer | – | – |
No output schema declared.
No examples provided.
render_ldraw_text ~78
Render inline LDraw content (the text of a .ldr file) to a PNG. Useful for quick experiments without writing a file first. Same bounds as render_ldraw_file.
| Name | Type | Req | Description |
|---|---|---|---|
| azimuths | string | – | – |
| ldr | string | yes | – |
| resolution | integer | – | – |
| samples | integer | – | – |
No output schema declared.
No examples provided.
search_parts ~86
Search the LDraw library's parts by description or file-name substring. Case-insensitive, runs of spaces collapsed (`brick 2 x 4` matches the header `Brick 2 x 4`). Returns at most `limit` parts (max 200) plus the total number of matches.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the ldraw-mcp server?
ldraw-mcp runs locally as a PyPI package, launched with uvx ldraw-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · ldraw-mcp
claude mcp add musharna-ldraw-mcp -- uvx ldraw-mcp
What is the ldraw-mcp server?
ldraw-mcp is listed in the public MCP registry as io.github.musharna/ldraw-mcp. Render LDraw/LEGO models to images with real part geometry via headless Blender + ImportLDraw. This page covers its PyPI package (ldraw-mcp).
Is the ldraw-mcp server safe to use?
ldraw-mcp scores 63 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 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.
What tools does the ldraw-mcp server expose?
ldraw-mcp exposes 6 tools: check_renderer, render_ldraw_file, render_ldraw_text, bill_of_materials, lookup_color, search_parts. Their descriptions and schemas cost roughly 566 tokens of context every time the server is loaded.
Is the ldraw-mcp server still maintained?
ldraw-mcp 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 ldraw-mcp server under?
ldraw-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.