Weapon Lab
PYPI · WEAPONLAB-MCP
Find and fix first-person weapon bugs behind a gate: your game's probe measures, the Gate judges
Available components
Last scanned (18 hours ago)
Scores higher than 51% of PyPI servers
Category Testing and QA
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 & 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 Usability48
- AI-judged instruction clarity (poor).Fail
- Tool/resource definitions use about 1427 tokens (~47/item across 30 items; 30 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 Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 13% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 30 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 31 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 +24
- 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 Schema quality: poor functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: pass functional
- First check of Tool coverage: 13 functional
- 14 Oct 26 24
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/weaponlab-mcp@0.1.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 →
contract_check ~53
Checks a file a probe reads or writes against the probe contract.
| Name | Type | Req | Description |
|---|---|---|---|
| job_path | – | – | for rows: the job they answer |
| kind | string | yes | job, rows or parts |
| path | string | yes | – |
No output schema declared.
No examples provided.
gate_add_case ~40
Adds or replaces a case.
| Name | Type | Req | Description |
|---|---|---|---|
| case | object | yes | {id, weapon, action, metric, rule {op, value}, about, source} |
No output schema declared.
No examples provided.
gate_approve ~42
Marks a passed proposal approved. Only on a person's word.
| Name | Type | Req | Description |
|---|---|---|---|
| approved_by | string | yes | who approved, in their words |
| proposal | string | yes | – |
No output schema declared.
No examples provided.
gate_cases ~39
The cases (each a known bug as a metric, a weapon, an action and a pass rule).
| Name | Type | Req | Description |
|---|---|---|---|
| status | – | – | – |
| weapon | – | – | – |
No output schema declared.
No examples provided.
gate_evals ~23
Each provider's eval: faults caught, good cases passed, trusted.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
gate_metrics ~22
Every metric: provider, unit, which way is better, tolerance.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
gate_proposals ~16
Every proposal: passed, approved.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
gate_propose ~60
A staged change measured and judged; the proposal waits for a person's approval.
| Name | Type | Req | Description |
|---|---|---|---|
| actions | – | – | – |
| name | string | yes | – |
| providers | array | yes | – |
| staging | – | – | – |
| targets | array | yes | – |
| weapons | – | – | – |
No output schema declared.
No examples provided.
gate_run ~51
Measures the weapons with the providers (probe, rig, or the project's own) and stores the run.
| Name | Type | Req | Description |
|---|---|---|---|
| actions | – | – | – |
| providers | array | yes | – |
| staging | – | – | – |
| weapons | – | – | – |
No output schema declared.
No examples provided.
gate_set_baseline ~31
A run's rows become the baseline (merged over the old).
| Name | Type | Req | Description |
|---|---|---|---|
| run_id | string | yes | – |
No output schema declared.
No examples provided.
gate_verdict ~43
Pass only if the target cases pass, nothing else got worse past its tolerance and the checks are trusted.
| Name | Type | Req | Description |
|---|---|---|---|
| run_id | string | yes | – |
| targets | – | – | – |
No output schema declared.
No examples provided.
gate_weapons ~13
The project's weapons.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
motion_render ~34
Dev views of parts dumps (not the game's view).
| Name | Type | Req | Description |
|---|---|---|---|
| objs | array | yes | – |
| out_folder | string | yes | – |
No output schema declared.
No examples provided.
motion_roll ~67
One clip's hand turned about its forearm, the twist bones sharing it.
| Name | Type | Req | Description |
|---|---|---|---|
| degrees | string | – | a number, or auto: the clip starts thumb up |
| out_fbx | string | yes | – |
| side | string | – | – |
| src_fbx | string | yes | – |
No output schema declared.
No examples provided.
motion_roll_profile ~51
The hand's roll about its forearm through a clip (0 thumb up; past 80 degrees breaks the forearm's range).
| Name | Type | Req | Description |
|---|---|---|---|
| fbx | string | yes | – |
| side | string | – | – |
No output schema declared.
No examples provided.
motion_roll_set ~70
A set of clips rolled, each from its own start, saved under new names (<name>_<suffix>).
| Name | Type | Req | Description |
|---|---|---|---|
| degrees | string | – | – |
| fbx_files | array | yes | – |
| out_folder | string | yes | – |
| side | string | – | – |
| suffix | string | yes | – |
No output schema declared.
No examples provided.
motion_track ~63
A sliding part's track rebuilt on its axis from its seat.
| Name | Type | Req | Description |
|---|---|---|---|
| axis | – | – | – |
| bone | string | yes | – |
| out_fbx | string | yes | – |
| root | string | yes | – |
| seat | – | – | – |
| src_fbx | string | yes | – |
No output schema declared.
No examples provided.
probe_plan ~27
The job's weapons the probe would get.
| Name | Type | Req | Description |
|---|---|---|---|
| actions | – | – | – |
| weapons | – | – | – |
No output schema declared.
No examples provided.
probe_run ~98
One probe run: rows, and screenshots and parts dumps at the moments.
| Name | Type | Req | Description |
|---|---|---|---|
| actions | – | – | – |
| at | – | – | {action: [seconds]} for screenshots and dumps |
| parts | – | – | – |
| shots | – | – | – |
| slomo | – | – | – |
| staging | – | – | a folder whose stage.json overrides assets |
| tune | – | – | {weapon: {field: value}}: a fix tried without writing it |
| weapons | array | yes | – |
No output schema declared.
No examples provided.
probe_status ~21
The processes that must not run with the probe, running now.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
project_info ~29
The project in use: its folder, data, specs and work folders, the probe command, Blender.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
rig_align ~67
A magazine's line into its well over a reload's moments: worst offset and tilt while in the well.
| Name | Type | Req | Description |
|---|---|---|---|
| axis | – | – | – |
| bone | string | yes | – |
| moment_objs | array | yes | – |
| seated_obj | string | yes | – |
| well_depth_cm | number | – | – |
No output schema declared.
No examples provided.
rig_facts ~41
The weapon spec's facts (order, side, below, in) on a dump.
| Name | Type | Req | Description |
|---|---|---|---|
| obj | string | yes | – |
| weapon | string | yes | – |
No output schema declared.
No examples provided.
rig_fist ~76
A melee hilt against the fist's grip channel, and the turn and move that lay it in (try them with probe_run's tune; a palm-down fist can hold the hilt right and still point the blade sideways: look at the screenshot).
| Name | Type | Req | Description |
|---|---|---|---|
| obj | string | yes | – |
| side | string | – | – |
No output schema declared.
No examples provided.
rig_part_line ~54
A sliding part's path against its axis: line_cm and seat_cm.
| Name | Type | Req | Description |
|---|---|---|---|
| axis | array | yes | – |
| bone | string | yes | – |
| moment_objs | array | yes | – |
| seated_obj | string | yes | – |
No output schema declared.
No examples provided.
rig_pieces ~40
A parts dump's pieces (triangles, centre, bounds, extents) and twins (a piece drawn twice).
| Name | Type | Req | Description |
|---|---|---|---|
| obj | string | yes | – |
No output schema declared.
No examples provided.
spec_list ~20
Every weapon spec: marks, actions, marks still proposed.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
spec_read ~27
One weapon's spec, with the default limits filled in.
| Name | Type | Req | Description |
|---|---|---|---|
| weapon | string | yes | – |
No output schema declared.
No examples provided.
spec_validate ~41
Every problem with a spec, as sentences (empty: whole).
| Name | Type | Req | Description |
|---|---|---|---|
| spec | – | – | a spec to check; or name a saved one |
| weapon | – | – | – |
No output schema declared.
No examples provided.
spec_write ~24
Saves a whole spec and returns what changed.
| Name | Type | Req | Description |
|---|---|---|---|
| spec | object | yes | – |
No output schema declared.
No examples provided.
How do I install the Weapon Lab MCP server?
Weapon Lab runs locally as a PyPI package, launched with uvx weaponlab-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 · weaponlab-mcp
claude mcp add hpdkhoa-weaponlab-mcp -- uvx weaponlab-mcp
What is the Weapon Lab MCP server?
Weapon Lab is an MCP server listed in the public MCP registry as io.github.hpdkhoa/weaponlab-mcp. Find and fix first-person weapon bugs behind a gate: your game's probe measures, the Gate judges. This page covers its PyPI package (weaponlab-mcp).
Is the Weapon Lab MCP server safe to use?
Weapon Lab scores 48 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 Weapon Lab MCP server expose?
Weapon Lab exposes 30 tools: project_info, contract_check, spec_list, spec_read, spec_validate, and 25 more. Their descriptions and schemas cost roughly 1,283 tokens of context every time the server is loaded.
Is the Weapon Lab MCP server still maintained?
Weapon 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 Weapon Lab MCP server under?
Weapon 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.