MCP.Market

Weapon Lab MCP server

by hpdkhoa·io.github.hpdkhoa/weaponlab-mcp·v0.1.0·1 stars
No reviews yet

Find and fix first-person weapon bugs behind a gate: your game's probe measures, the Gate judges

A92/100grade A
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
A92/100

full report

Adoption
New

1 stars

Reviews

Write one

Nobody has reviewed Weapon Lab yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Weapon Lab tools (30, 3 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • contract_check

    Checks a file a probe reads or writes against the probe contract.

  • gate_add_case

    Adds or replaces a case.

  • gate_approve

    Marks a passed proposal approved. Only on a person's word.

  • gate_cases

    The cases (each a known bug as a metric, a weapon, an action and a pass rule).

  • gate_evals

    Each provider's eval: faults caught, good cases passed, trusted.

  • gate_metrics

    Every metric: provider, unit, which way is better, tolerance.

  • gate_proposals

    Every proposal: passed, approved.

  • gate_propose

    A staged change measured and judged; the proposal waits for a person's approval.

  • gate_runwrite action

    Measures the weapons with the providers (probe, rig, or the project's own) and stores the run.

  • gate_set_baseline

    A run's rows become the baseline (merged over the old).

  • gate_verdict

    Pass only if the target cases pass, nothing else got worse past its tolerance and the checks are trusted.

  • gate_weapons

    The project's weapons.

  • motion_render

    Dev views of parts dumps (not the game's view).

  • motion_roll

    One clip's hand turned about its forearm, the twist bones sharing it.

  • motion_roll_profile

    The hand's roll about its forearm through a clip (0 thumb up; past 80 degrees breaks the forearm's range).

  • motion_roll_set

    A set of clips rolled, each from its own start, saved under new names (<name>_<suffix>).

  • motion_track

    A sliding part's track rebuilt on its axis from its seat.

  • probe_plan

    The job's weapons the probe would get.

  • probe_runwrite action

    One probe run: rows, and screenshots and parts dumps at the moments.

  • probe_status

    The processes that must not run with the probe, running now.

  • project_info

    The project in use: its folder, data, specs and work folders, the probe command, Blender.

  • rig_align

    A magazine's line into its well over a reload's moments: worst offset and tilt while in the well.

  • rig_facts

    The weapon spec's facts (order, side, below, in) on a dump.

  • rig_fist

    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).

  • rig_part_line

    A sliding part's path against its axis: line_cm and seat_cm.

  • rig_pieces

    A parts dump's pieces (triangles, centre, bounds, extents) and twins (a piece drawn twice).

  • spec_list

    Every weapon spec: marks, actions, marks still proposed.

  • spec_read

    One weapon's spec, with the default limits filled in.

  • spec_validate

    Every problem with a spec, as sentences (empty: whole).

  • spec_writewrite action

    Saves a whole spec and returns what changed.

Public scan report

scanner v0.1.10 · 2026-10-14 · same rubric, same numbers if you re-run it

no findings
  • Code scan15 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 0 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 92/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Weapon Lab compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
92/100
higher than 90% of 48,273 servers
Tools
30
the typical server has 7
Tools that change things
10%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
1
more than 65% of 28,534 servers

What its tools let an agent do: 27 read · 3 change

Install Weapon Lab in Claude Code, Cursor or VS Code

claude mcp add weaponlab-mcp -- uvx weaponlab-mcp
Add to Cursor

What the publisher says

From the Weapon Lab repository's README, as published. We do not edit it. Read it on GitHub

Weapon Lab

<!-- mcp-name: io.github.hpdkhoa/weaponlab-mcp -->

An MCP server that finds and fixes first-person weapon bugs behind a gate: hands off the gun, a magazine crooked in its well, a blade held wrong, arms covering the screen.

Each bug becomes a case: a metric, a weapon, an action and a pass rule. Your game's own probe measures the weapons. The Gate passes a change only when its target cases pass and nothing else got worse. Fix each kind of bug once, then check every weapon with it.

Weapon Lab never runs your game itself. You write a small probe for your engine that follows the probe contract: a job file in, a rows file out. Everything else works on what the probe writes back.

What it does

Try it on the demo

The demo is a toy game with two planted bugs and a probe in about 150 lines. It needs no engine.

pip install -e .
cd examples/demo
weaponlab gate run probe,rig

(python -m weaponlab works the same when pip's scripts folder is not on your PATH.)

The rifle's left hand misses its handguard by 3.75 cm. The knife's hilt lies 90 degrees across the fist. tests/test_demo.py walks the whole loop: measure, find the fix, try it by tune, judge it.

Use it in your game

Set its command in weaponlab.json.

  1. weaponlab init in your project. It writes weaponlab.json and empty data files.
  2. Write your probe from the contract, starting from examples/demo/probe/demo_probe.py.
  1. List your weapons in weaponlab/data/weapons.json and their actions in actions.json.
  2. Add a case for each bug you know. Measure everything once and set the baseline.
  3. Fix through the loop: try by tune or staging, look at the screenshots, propose, approve, import.

Check your probe on its own with weaponlab contract job|rows|parts .

Add it to an MCP client

{"mcpServers": {"weaponlab": {"command": "weaponlab-mcp", "env": {"WEAPONLAB_PROJECT": "C:/path/to/your/game"}}}}

Requirements

the forearm roll.

  • Python 3.10 or later.
  • Blender 4.4 or later for Motion Lab and renders. Nothing else needs it.
  • Hand bones named as Unreal's mannequin names them (handr, index01r, lowerarmr) for the fist measure and

Where it came from

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Weapon Lab: common questions

Is Weapon Lab MCP server safe?
Yes, by our scan: it is graded A (92/100). Read the Weapon Lab safety report
How do I install Weapon Lab?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Weapon Lab need an API key?
No secret keys are declared. It reads 2 settings from the environment.
Is Weapon Lab maintained?
The last commit was 19 days ago (2026-10-14). The latest release is v0.1.0.
How does Weapon Lab compare with other MCP servers?
safety score 92/100 (higher than 90% of 48,273 servers); tools 30 (the typical server has 7); tools that change things 10% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

More from hpdkhoa →