pickfit

BrowseMCP servers

@agentage/find-mcp

Stdio client that lets AI apps search a directory of 17,000+ MCP servers.

Tested on Linux

Use it

Linux x86_64

You need first

  • Needs the network
  1. install @agentage/find-mcp globally via npm

    npm install -g @agentage/find-mcp

Check that it works

agentage-find-mcp --version

The output should contain “1.13.3”.

Add it to your agent

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

Add agentage-find-mcp as a stdio MCP server in your AI app's MCP settings, then ask it to find servers.

What it does

  • Search MCP servers by keyword with filters
    How to use it
    1. Connect agentage-find-mcp to your AI app as an MCP server.
    2. Call the mcp_search tool with a query, for example {"query":"<keyword>"}.
    Tested
  • Get a server's packages, tools and install command
    How to use it
    1. Find the server's slug with mcp_search.
    2. Call the mcp_get tool with {"slug":"<server-slug>"}.
    Tested
  • List category, language and license filters
    How to use it
    1. Call the mcp_categories tool with no arguments ({}).
    Tested

How far pickfit got

Linux x86_64

  1. Installs
  2. Connects
  3. 3 of 3 features work
  4. Needs the network

Good for

  • Find a tool that connects AI to Postgres
  • Check for a Notion MCP server and how to install it
  • List popular tools for browser automation

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
  • Needed the network
  • Checked on 31 Oct 2026
  • Version 1.13.3

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

Differences the test machine hit

  • README: launch via npx -y @agentage/find-mcp and binary assumed find-mcp
    In the test: global install provides binary agentage-find-mcp (bin.agentage-find-mcp); probe used agentage-find-mcp, npx -y @agentage/find-mcp equivalent for ephemeral use

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.