pickfit

Same answers, in your agent

pickfit is an MCP server. Your coding agent gets the same verified data and the same matching as this page, and can install a pick for you with the steps that worked

Connect

Any MCP client that speaks streamable HTTP can connect to https://pickfit.app/mcp.

For Claude Code:

claude mcp add --transport http pickfit https://pickfit.app/mcp

For Claude Desktop, Cursor and other clients, add it to the MCP config:

{
  "mcpServers": {
    "pickfit": {
      "type": "http",
      "url": "https://pickfit.app/mcp"
    }
  }
}

Tools

ToolWhat it does
find_softwareTwo or three verified tools for a need and conditions (OS, CPU, free only, offline), with reasons, tradeoffs, the best free option and, when it fits, “built-in is enough”.
find_alternativesReplacements for a tool you use now, given what you don’t like about it and what you must keep.
get_install_guideThe steps that worked in pickfit’s run, for your OS, with what you do by hand and how to check the install.
report_outcomeDid it install, did it work, are you still using it. Failures queue the tool for a fresh run.
submit_softwareSend a GitHub project or a web app for review, the same as the form on /submit. It goes through the same read, install and replay as everything else.

Try it

Ask your agent in plain words, for example:

Find me a free tool that works offline on my Mac to turn meeting recordings into subtitles, and install it.

No sign-up, no ads

The MCP needs no account and returns no referral links. Answers carry a how_we_know line and the run’s evidence_url, so your agent can tell you where each claim came from.

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.