pickfit

BrowseMCP servers

InterMCP

Pure-Rust MCP engine and hub that multiplexes MCP servers with sandboxing and guardrails.

Tested on Linux

Use it

Linux x86_64

  1. install npm wrapper and download/extract native binary to ~/.intermcp/bin

    npm install -g intermcp && curl -sSL "https://github.com/Bharathcoorg/intermcp/releases/download/v0.3.0/intermcp-v0.3.0-x86_64-unknown-linux-gnu.tar.gz" -o /tmp/intermcp.tar.gz && mkdir -p ~/.intermcp/bin && tar xzf /tmp/intermcp.tar.gz -C ~/.intermcp/bin && chmod +x ~/.intermcp/bin/intermcp
Where the README and reality differ
  • README: npm install intermcp then npx intermcp serve works
    What worked: npm package is only a JS wrapper that spawns native binary; must also download native binary intermcp-v0.3.0-x86_64-unknown-linux-gnu.tar.gz to ~/.intermcp/bin
  • README: curl install.sh downloads intermcp-linux-x86_64.tar.gz via latest/download
    What worked: asset name is intermcp-v0.3.0-x86_64-unknown-linux-gnu.tar.gz, so install.sh 404s
  • README: pip install intermcp provides executables
    What worked: PyPI package has no executables (uv/pipx fail with No executables)

Check that it works

~/.intermcp/bin/intermcp --version 2>&1

The output should contain “intermcp 0.3.0”.

Add it to your agent

claude mcp add intermcp -- $HOME/.intermcp/bin/intermcp serve
JSON for Claude Desktop, Cursor and other clients
{
  "mcpServers": {
    "intermcp": {
      "command": "sh",
      "args": [
        "-c",
        "exec \"$HOME/.intermcp/bin/intermcp\" serve"
      ]
    }
  }
}

Add InterMCP as an MCP server in your MCP client, which then connects to it over stdio and lists its file, git and system tools.

What it does

These come from the README; pickfit didn’t check them one by one.

  • Combine several MCP servers into one connection
    Not tested
  • Route MCP requests to servers quickly
    Not tested
  • Limit file access to allowed directories
    Not tested
  • Set up editors without editing JSON by hand
    Not tested

How far pickfit got

Linux x86_64

  1. Installs
  2. Connects
  3. A tool call works
  4. Works offline

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

Good for

  • aggregate multiple external MCP servers into a single stdio pipe
  • auto-configure Claude Desktop, Cursor, Windsurf and Cline
  • serve MCP tools over remote HTTP/SSE gateway
  • sandbox filesystem access to authorized directories
  • record and replay JSON-RPC sessions for debugging

An alternative to @modelcontextprotocol/sdk and mcp.

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.3.0

An MCP client handshake over stdio listed 8 tools, and a call to system_info 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.