pickfit

BrowseDeveloper CLIs

mcp-audit

Offline security scanner for MCP server configurations across AI coding clients.

Tested on macOS and Linux

Use it

macOS arm64

  1. Install via uv tool

    uv tool install mcp-audit-scanner

Check that it works

mcp-audit --help 2>&1

The output should contain “Scan MCP configurations for security issues.”.

First thing to try

mcp-audit discover 2>&1

Run mcp-audit discover to find the MCP configurations on your machine.

Linux x86_64

  1. install mcp-audit via uv tool install mcp-audit-scanner

    uv tool install mcp-audit-scanner

Check that it works

mcp-audit --help 2>&1

The output should contain “scan”.

First thing to try

mcp-audit version 2>&1

Run mcp-audit discover to find the MCP configurations on your machine.

What it does

  • Scan MCP server configs for security risks
    How to use it
    1. Run mcp-audit check --path <config file> on an MCP config such as mcp.json.
    2. Read the grade and score (out of 100) in the output.
    Tested
  • Open an interactive attack graph dashboard
    How to use it
    1. Run mcp-audit dashboard --path <config file> --no-open --port <port>.
    2. Open http://127.0.0.1:<port>/ in your browser to view the Attack Graph.
    Tested
  • Save approved MCP servers to a lock file
    Not tested
  • Find risky combinations across servers
    Not shown working

How far pickfit got

macOS arm64

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

Linux x86_64

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

Good for

  • scan detected MCP configs for security issues
  • verify approved MCP servers have not drifted in CI
  • export scan results to SARIF for GitHub Security tab

How pickfit tested it

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

macOS arm64

Its service answers requests

  • Replayed from scratch
  • Works offline
  • Checked on 30 Oct 2026
  • Version 0.25.1

Differences the test machine hit

  • README: CLI help implies standard --version flag
    In the test: use `mcp-audit --help` or `mcp-audit version`; `--version` errors with No such option
  • README: mcp-audit check / mcp-audit scan with no args
    In the test: use --path /tmp/mcpdemo/mcp.json to scan a chosen file; bare scan/discover only check auto-discovered client paths
  • README: mcp-audit lock # Write mcp-lock.json
    In the test: add --offline to avoid online package version lookup so replay works with network off
  • README: mcp-audit dashboard # Open interactive attack graph dashboard
    In the test: use mcp-audit dashboard --path <config> --no-open --port <port> and query http://127.0.0.1:<port>/; server keeps running until stopped

Linux x86_64

Its main function works

  • Replayed from scratch
  • Works offline
  • Checked on 30 Oct 2026
  • Version 0.25.1

Differences the test machine hit

  • README: `mcp-audit --version` flag
    In the test: use `mcp-audit version` (subcommand) or `mcp-audit --help`
  • README: `mcp-audit scan` on a risky config exits non-zero
    In the test: exit code 1 is the documented outcome when findings are detected, not a failure

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.