io.github.jeongho54/loadbench
PYPI · LOADBENCH-MCP · SCANNED SEP 21
MCP server for structural load & stability math: tipping, support reactions, beam checks.
Available components
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 native-build step with no shell scripting around it. View diagnostics → Pass
- 0 of 30 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency32
- 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
- License check failed: the license (MIT License) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 83 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability63
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 890 tokens (~296/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.jeongho54/loadbench MCP server?
io.github.jeongho54/loadbench runs locally as a PyPI package, launched with uvx loadbench-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 · loadbench-mcp
claude mcp add jeongho54-loadbench -- uvx loadbench-mcp
{
"mcpServers": {
"jeongho54-loadbench": {
"command": "uvx",
"args": [
"loadbench-mcp"
]
}
}
} {
"servers": {
"jeongho54-loadbench": {
"command": "uvx",
"args": [
"loadbench-mcp"
]
}
}
} codex mcp add jeongho54-loadbench -- uvx loadbench-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"jeongho54-loadbench": {
"type": "local",
"command": [
"uvx",
"loadbench-mcp"
],
"enabled": true
}
}
} openclaw mcp add jeongho54-loadbench --command uvx --arg loadbench-mcp
mcp_servers:
jeongho54-loadbench:
command: "uvx"
args: ["loadbench-mcp"] {
"McpServers": {
"jeongho54-loadbench": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"loadbench-mcp"
]
}
}
} assistant mcp add jeongho54-loadbench -t stdio -c uvx -a loadbench-mcp
{
"mcpServers": {
"jeongho54-loadbench": {
"command": "uvx",
"args": [
"loadbench-mcp"
]
}
}
} 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.
- 21 Sept 26 +16
- Malware scan: unverified → pass ▲ security
- 19 Sept 26 −2
- Stability: pass → 0.83 functional
- 18 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- Stability: 0.97 → pass security
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
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 21 Sept 2026 · Analysed pypi/loadbench-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 |
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 30 packages
| Packages resolved | 30 |
|---|---|
| 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 →
beam_check ~421
Check whether a beam or shelf holds a load: bending stress and deflection. Closed-form Euler–Bernoulli check. "point" puts the whole load at the centre (simply supported) or the free end (cantilever); "udl" spreads magnitude_n evenly along the span. Give the section either directly (section_modulus_m3 and inertia_m4) OR as a solid rectangle (width_m and height_m). Args: span_m: clear span / length, metres. support_type: "simply_supported" (held both ends) or "cantilever" (one end). load_type: "point" or "udl" (uniformly distributed). magnitude_n: total load in newtons (1 kg ≈ 9.81 N). e_pa: Young's modulus of the material, pascals (steel ≈ 2.0e11, pine ≈ 9e9). allowable_stress_pa: allowable bending stress of the material, pascals. section_modulus_m3: Z, if known. Else give width_m and height_m. inertia_m4: I, if known. Else give width_m and height_m. width_m, height_m: for a solid rectangle, used to compute Z and I. deflection_limit_ratio: optional, e.g. 250 means limit deflection to span/250. Returns: max_moment_nm, max_stress_pa, max_deflection_m, stress utilisation, pass/fail, governing check, and a short explanation.
| Name | Type | Req | Description |
|---|---|---|---|
| allowable_stress_pa | number | yes | – |
| deflection_limit_ratio | – | – | – |
| e_pa | number | yes | – |
| height_m | – | – | – |
| inertia_m4 | – | – | – |
| load_type | string | yes | – |
| magnitude_n | number | yes | – |
| section_modulus_m3 | – | – | – |
| span_m | number | yes | – |
| support_type | string | yes | – |
| width_m | – | – | – |
No output schema declared.
No examples provided.
check_tipping ~249
Check whether a collection of weights will tip over its support footprint. Computes the centre of mass and tests whether its vertical projection falls inside the support base (the polygon where the object touches the ground). If it falls outside, the object tips. Use this for shelving, stacked loads, machinery on legs, vehicles, or anything that could topple. Args: masses: list of point masses, each {"x": metres, "y": metres, "mass": kg}. x/y are top-down (plan-view) positions. Height does not affect whether it tips on level ground, only the horizontal centre of mass does. base_polygon: the support footprint as ordered vertices [{"x", "y"}, ...] in metres (e.g. the four feet of a shelf, or the contact outline). Returns: center_of_mass, is_stable (bool), tipping_margin_m (positive = inside the base with this much clearance; negative = already outside / tipping), tipping_direction (unit vector toward the closest base edge), and a short human-readable explanation.
| Name | Type | Req | Description |
|---|---|---|---|
| base_polygon | array | yes | – |
| masses | array | yes | – |
No output schema declared.
No examples provided.
solve_supports ~220
Compute how much vertical force each support (leg, bracket, foot) carries. Models a rigid object resting on point supports of equal stiffness and solves static equilibrium so the reactions balance every applied load in force and moment. Handles any number of supports. Flags supports that exceed their rated capacity, and supports with a negative reaction (the object is lifting off / would tip rather than rest evenly). Args: supports: [{"id": str, "x": m, "y": m, "capacity_n": N (optional)}]. loads: downward point loads [{"x": m, "y": m, "magnitude_n": N}]. self_weight_n: optional self-weight of the object (N), applied at the centroid of the supports. Returns: per-support reaction forces, over-capacity / lift-off flags, total load, max utilisation, any warnings, and a short explanation.
| Name | Type | Req | Description |
|---|---|---|---|
| loads | array | yes | – |
| self_weight_n | number | – | – |
| supports | array | yes | – |
No output schema declared.
No examples provided.
What is the io.github.jeongho54/loadbench MCP server?
io.github.jeongho54/loadbench is an MCP server listed in the public MCP registry as io.github.jeongho54/loadbench. MCP server for structural load & stability math: tipping, support reactions, beam checks. This page covers its PyPI package (loadbench-mcp).
Is the io.github.jeongho54/loadbench MCP server safe to use?
io.github.jeongho54/loadbench scores 76 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 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 io.github.jeongho54/loadbench MCP server expose?
io.github.jeongho54/loadbench exposes 3 tools: check_tipping, solve_supports, beam_check. Their descriptions and schemas cost roughly 890 tokens of context every time the server is loaded.
Is the io.github.jeongho54/loadbench MCP server still maintained?
io.github.jeongho54/loadbench is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.