Loadbearing

io.github.andypgrayPublished by GitHub account andypgrayv0.8.0Updated Oct 9, 2026

Checks .NET solutions against a fluent C# architecture spec and explains the rules to agents.

VerifiedSTDIODesktop onlyDeveloper Tools

Overview

AI-generated overview

Local MCP server that checks .NET solutions against a fluent C# architecture spec and explains the rules to an assistant.

What you can do
  • Check a .NET solution against an architecture spec written in fluent C# and report violations.
  • Explain the architecture rules to the assistant so it can reason about them.
  • Resolve which solution to check from an argument or from the configured solution path.
When to use it
Useful when working in a .NET codebase that has a Loadbearing architecture spec and you want an assistant to verify or discuss layering and dependency rules while editing code.
Requirements
Runs as a local process on the user's machine via dnx from the Zphil.LoadBearing.Cli NuGet package; desktop only, no web execution. The .NET tooling needed for dnx must be available. Optionally set LOADBEARING_SOLUTION_PATH to the solution to check when no solution argument is passed.
Before you install
The generated config passes no solution argument, so the solution path binds through LOADBEARING_SOLUTION_PATH; point it at the intended repository. No authentication is declared.

Installation

In SourceWeft

  1. Open Loadbearing in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.8.0LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.