pickfit

BrowseMCP servers

RepoGuard

Architecture guardrail generator and auditor that keeps AI-generated code clean

Tested on Linux

Use it

Linux x86_64

  1. install repoguard globally via npm install -g repoguard-rules

    npm install -g repoguard-rules
Where the README and reality differ
  • README: npm package is repoguard-rules with bin repoguard-rules / npx repoguard-rules
    What worked: global install provides bin `repoguard` (and `repoguard-cli`), not `repoguard-rules`; launch is `repoguard mcp`

Add it to your agent

claude mcp add repoguard -- repoguard mcp
JSON for Claude Desktop, Cursor and other clients
{
  "mcpServers": {
    "repoguard": {
      "command": "repoguard",
      "args": [
        "mcp"
      ]
    }
  }
}

Add repoguard mcp as an MCP server in your AI client, then call its tools such as repoguard_audit.

What it does

  • Audit the architectural health of a codebase
    How to use it
    1. Connect your MCP client to the server started with repoguard mcp.
    2. Call the repoguard_audit tool with {"directory": "<project directory>"}.
    3. Read the text report it returns.
    Tested
  • Generate AI context files tailored to your project
    Not tested
  • Audit uncommitted git changes
    Not shown working
  • Find leaked secrets and credentials
    Not shown working

How far pickfit got

Linux x86_64

  1. Installs
  2. Connects
  3. 1 of 4 features work
  4. Works offline

How pickfit tested it

Each run starts from a clean machine and follows the steps above. How pickfit verifies

Linux x86_64

An MCP client called one of its tools

  • Replayed from scratch
  • Works offline
  • Checked on 1 Nov 2026
  • Version 1.7.0

An MCP client handshake over stdio listed 4 tools, and a call to repoguard_audit returned a result.

Differences the test machine hit

  • README: npx repoguard-rules mcp launches server
    In the test: installed globally works as `repoguard mcp` without npx -y fetch

How to read a tool card

Stitching
pickfit installed this tool itself. Everything under the stitches comes from that run. A tool pickfit has not run never gets stitches.
Verified on your OS
The install steps ran on the system you chose. “Ran on Linux only” means it has not been run on yours yet.
macOS, Linux and WindowsWhere it ran
Green OS marks: pickfit ran the install steps there. Grey ones: the README says it runs there, and pickfit has not tried.
How far the run got
Installs and starts, its main function works, its service answers, it produces model output. A window means a desktop app opened; a plug, an MCP client used it. The mark sits beside the run’s result, under “Why it fits and how we know” and in “How pickfit tested it”.
Visual check
pickfit looked at screenshots of the app. Green: it looks right. Amber with a number: things that look wrong; open it to see them. Grey and dashed: not checked yet.
Known vulnerabilities
Known high or critical vulnerabilities (OSV.dev) in what it installs. Green: none known. Red with a number: how many; open it for the list, and read it before you install. Grey and dashed: not checked, which does not mean safe.
About the run
The day it ran, and the version that ran.
Source of a reason
Every reason a pick fits rests on one profile field. Open the reason to see the field and the value it relies on.
Hidden gem
High quality, little known.
Quality and popularity
Two scores out of 100. Quality: how well it installed and worked when pickfit tried it, and how good its install docs and upkeep are. Popularity: from stars, downloads and Hacker News.
Features checked
Of the main features the README advertises, how many the run actually exercised (green), and how many failed (red). Grey ones were not checked, and the card says why.
Not verified
A well-known tool Fitz mentions from general knowledge. No run record, no steps, no score.