MCP.Market

Loadbench MCP server

by jeongho54·io.github.jeongho54/loadbench·v0.1.0

MCP server for structural load & stability math: tipping, support reactions, beam checks.

A88/100grade A
What users say
No reviews yet
Be the first
Safety scan
A88/100

full report

Adoption
New

0 stars

Reviews

Write one

Nobody has reviewed Loadbench yet.

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

Loadbench tools (3)

write = sends, deletes, buys or posts

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

  • beam_check

    Check whether a beam or shelf holds a load: bending stress and deflection.

  • check_tipping

    Check whether a collection of weights will tip over its support footprint.

  • solve_supports

    Compute how much vertical force each support (leg, bracket, foot) carries.

Public scan report

scanner v0.1.9 · 2026-09-26 · same rubric, same numbers if you re-run it

no findings
  • Code scan4 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 89 days ago12/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 88/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Loadbench compares

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

Safety score
88/100
higher than 75% of 48,255 servers
Tools
3
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break

What its tools let an agent do: 3 read

Install Loadbench in Claude Code, Cursor or VS Code

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

What the publisher says

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

<!-- mcp-name: io.github.jeongho54/loadbench -->

loadbench-mcp

An MCP server that does the structural load & stability math language models get wrong. AI assistants call it instead of guessing.

All math is verified against hand-computed answers (tests/test_physics.py).

Install & run

Once published to PyPI, any MCP client can launch it with no install step:

uvx loadbench-mcp

Or install it:

pip install loadbench-mcp
loadbench-mcp

Use it in Claude Desktop

Add to your claudedesktopconfig.json:

{
  "mcpServers": {
    "loadbench": {
      "command": "uvx",
      "args": ["loadbench-mcp"]
    }
  }
}

Restart Claude Desktop, then ask things like "A 2 m pine shelf on two brackets 0.3 m from each end — will it hold 40 kg in the middle?"

Local development

uv run --with mcp --with numpy python -m load_solver.server   # run from source
python -m pytest tests                                         # verify the math

Inputs are SI units (metres, kilograms, newtons; 1 kg ≈ 9.81 N). Tool docstrings carry the full argument details, which the model reads automatically.

Estimates for planning, not certified engineering. For loads where a failure

could cause injury or real damage, have a qualified engineer check the result.

License

MIT

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

Loadbench: common questions

Is Loadbench MCP server safe?
Yes, by our scan: it is graded A (88/100). Read the Loadbench safety report
How do I install Loadbench?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Loadbench need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Loadbench maintained?
The last commit was 128 days ago (2026-06-29). The latest release is v0.1.0.
How does Loadbench compare with other MCP servers?
safety score 88/100 (higher than 75% of 48,255 servers); tools 3 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.