pickfit

BrowseMCP servers

PkgDiet

Dependency policy tool that blocks risky AI-suggested npm installs via hooks and MCP.

Tested on Linux

Use it

Linux x86_64

You need first

  • Runtimes: Node.js >=20
  1. install pkgdiet globally via npm

    npm install -g pkgdiet

Check that it works

pkgdiet --version

The output should contain “2.0.1”.

Add it to your agent

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

Run pkgdiet mcp to start the MCP server, then connect it from your MCP client.

What it does

  • Check a package against your dependency policy
    How to use it
    1. Start the server with pkgdiet mcp and connect your MCP client.
    2. Call the check_dependency tool with packageName set to <package>.
    3. Read the returned verdict text.
    Tested
  • Get modern alternatives for blocked packages
    How to use it
    1. Start the server with pkgdiet mcp and connect your MCP client.
    2. Call the suggest_alternative tool with packageName set to <package>.
    3. Review the suggested replacements in the returned text.
    Tested
  • Block unapproved installs before they run
    Not shown working
  • Audit existing dependencies for policy and health
    Not shown working

How far pickfit got

Linux x86_64

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

Good for

  • evaluate npm packages against repository dependency policy
  • block risky AI-generated dependency before install
  • audit existing dependencies for policy, health and size
  • suggest modern lighter alternatives for blocked packages
  • enforce dependency policy on branch changes in CI

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 31 Oct 2026
  • Version 2.0.1

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

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.