Loadbearing MCP server
Checks .NET solutions against a fluent C# architecture spec and explains the rules to agents.
B83/100grade B
Adoption
New
0 stars
Reviews
Write oneNobody has reviewed Loadbearing yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Loadbearing tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.5 · 2026-09-19 · same rubric, same numbers if you re-run it
no findings
- –Code scanpackage could not be scannedn/a
- –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 4 days ago15/15
- Maintainer identityregistry namespace matches repository owner6/10
Overall 83/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON
Install directly
The registry entry has no remote endpoint or installable package.
Loadbearing: common questions
- Is Loadbearing MCP server safe?
- Mostly: it is graded B (83/100). Read the Loadbearing safety report
- Does Loadbearing need an API key?
- No secret keys are declared. It reads 1 setting from the environment.
- Is Loadbearing maintained?
- The last commit was 5 days ago (2026-09-15). The latest release is v0.8.0.