pickfit

BrowseMCP servers

OpenHire · 开聘

MCP server and CLI that finds jobs in employers' own ATS while keeping your resume local.

Tested on Linux

Use it

Linux x86_64

You need first

  • Runtimes: python >= 3.11
  • System packages: uv
  1. Install openhire via uv tool install openhire

    uv tool install openhire

Add it to your agent

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

Add OpenHire as an MCP server in your MCP client, then ask the client to search for jobs; it uses the search_jobs tool.

What it does

  • Find jobs in employers' own hiring systems
    Not shown working
  • Check if job postings are still open
    Not shown working
  • Check if an employer is a real company
    Not shown working

How far pickfit got

Linux x86_64

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

macOS and Windows: the project says it runs there; pickfit hasn’t tried it.

Good for

  • check which applied postings have closed
  • find perception roles in Shanghai with original posting dates
  • watch an employer's careers page for new postings
  • check a posting before applying
  • verify employer background and trust signals

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 0.8.47

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

Differences the test machine hit

  • README: The server's tools/list shows each tool's description to the calling agent as is
    In the test: Tool salary_benchmark's description has instruction-like text aimed at the agent (text telling the model to keep something from the user). pickfit neither kept nor followed it; read what the server sends before enabling it.
  • README: The server's tools/list shows each tool's description to the calling agent as is
    In the test: Tool search_jobs's description has instruction-like text aimed at the agent (text telling the model to keep something from the user). pickfit neither kept nor followed it; read what the server sends before enabling it.

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.