Loadbearing runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 12 Sep 2026.
Checks .NET solutions against a fluent C# architecture spec and explains the rules to agents.
What the code does
We read the source, 21 h ago · rules 3dff92dd89df
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
var psi = new ProcessStartInfo("git")
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Alternatives to Loadbearing
same job, measured the same wayRepo rules enforcement for AI agents. Checks diffs against repo conventions.
Analyze any codebase — get architecture, file roles, execution flows, and agent context.
Your architecture in your agents' context: checks, specs, ADRs and docs over MCP, at write time.
Architecture governance for AI agents: query the live model, get target patterns, check files.
MCP server exposing CAST Imaging software architecture insights to AI agents
Checks the context files a coding agent reads against the git index, and reports what drifted.
Call the real API and check the response against your OpenAPI spec.
Pre-spend firewall for AI agents. Approves, blocks, flags transactions against policy rules.
Loadbearing — questions
Answers built from our own checks of this server.