Model Lab
PYPI · MODELLAB-MCP
Draws rigged game gun models in Blender from parameters, checked against the real gun
Available components
Last scanned (23 hours ago)
Scores higher than 70% 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 Security100
- 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
- 1 of 29 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- 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 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability66
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 981 tokens (~98/item across 10 items; 10 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 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
Unverified: 1 category
A category scored 0 because we could not verify it: 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.
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.
- 15 Oct 26 +30
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: pass functional
- First check of Schema quality: good functional
- First check of Tool coverage: 100 functional
- Package version: 0.1.0 → 0.2.0 functional
- 14 Oct 26 39
First indexed and scored.
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 16 Oct 2026 · Analysed pypi/modellab-mcp@0.2.0
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 →
build_gun ~195
Builds a gun in Blender (15 to 30 s): the rig FBX, the hand magazine FBX, one FBX an attachment, the .blend (with the cycle as an action), facts.json and a sheet of labelled dev views; with motion, GIFs of the cycle. Returns the checks that failed (none when all_pass), the size and the files.
| Name | Type | Req | Description |
|---|---|---|---|
| motion | boolean | – | also render the moving parts' cycle as GIFs (about a minute more) |
| name | – | – | the model's name in its files (letters, digits, _) |
| params | – | – | parameters to set or change, e.g. {"barrel_in": 16} |
| platform | – | – | without a preset: the platform to build |
| preset | – | – | a preset to start from, e.g. M4A1 |
| scale | number | – | the whole model's scale; 1 is real size |
No output schema declared.
No examples provided.
build_gun_clips ~148
The gun's own clips on a build's rig, from real beats and timings at 60 frames a second: each measured (parts on their axes, the bolt's stroke, the cover open before the carrier, the magazine out of the well and seated, the bolt held on its catch), exported alone as FBX (A_<name>_<clip>.fbx) and shown as a GIF.
| Name | Type | Req | Description |
|---|---|---|---|
| build | string | yes | a build folder name from list_builds |
| clips | – | – | charge, chamber_check, fire, fire_last, reload, reload_empty, stock; leave out for all |
| render | boolean | – | render a labelled GIF a clip |
No output schema declared.
No examples provided.
compare_to_reference ~119
The real-gun check: draws the build's side outline at the reference photo's scale and alignment, measures both outlines column by column, and returns the stretches that differ by more than 0.4 cm, each with the parts there and its zone (the gun, or an attachment over the rail), and an overlay picture (the model in red over the photo).
| Name | Type | Req | Description |
|---|---|---|---|
| build | – | – | a build folder; leave out to build the reference's own configuration |
| reference | string | – | a reference id from list_references |
No output schema declared.
No examples provided.
describe_params ~48
A platform's parameters (type, range or choices, unit, meaning) and the sources its real numbers come from.
| Name | Type | Req | Description |
|---|---|---|---|
| platform | string | – | a platform id, e.g. ar15 |
No output schema declared.
No examples provided.
list_attachments ~70
The attachments a build can mount on the rails and M-LOK slots (optics, backup sights, the carry handle, a vertical grip, a light): what each is, the rails it fits, its states and moving parts. Pass them to build_gun as params.attachments.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_builds ~25
The latest builds, newest first: name, whether every check passed, size.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_platforms ~22
The gun families Model Lab can draw, with their parameter names.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_presets ~52
The ready guns (M4A1, M16A2, AR15, M4A1_Kitted, AR15_Optic): their parameters and the published lengths each build is checked against.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_references ~36
The real-gun photos compare_to_reference measures against: each photo's source, licence, scale and the build that matches it.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
read_build ~48
A build's facts: parameters, marks, moving parts, rails, attachments, the parts table, every check, files.
| Name | Type | Req | Description |
|---|---|---|---|
| build | string | yes | a build folder name from list_builds |
No output schema declared.
No examples provided.
How do I install the Model Lab MCP server?
Model Lab runs locally as a PyPI package, launched with uvx modellab-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 · modellab-mcp
claude mcp add hpdkhoa-modellab-mcp -- uvx modellab-mcp
What is the Model Lab MCP server?
Model Lab is an MCP server listed in the public MCP registry as io.github.hpdkhoa/modellab-mcp. Draws rigged game gun models in Blender from parameters, checked against the real gun. This page covers its PyPI package (modellab-mcp).
Is the Model Lab MCP server safe to use?
Model Lab scores 69 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 16 October 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 Model Lab MCP server expose?
Model Lab exposes 10 tools: list_platforms, describe_params, list_presets, list_attachments, list_references, and 5 more. Their descriptions and schemas cost roughly 763 tokens of context every time the server is loaded.
Is the Model Lab MCP server still maintained?
Model Lab is still listed as active in the MCP registry. We last reached this channel on 16 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 Model Lab MCP server under?
Model Lab declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.