B2match (unofficial) MCP Server

What the code does

We read the source, 8 h ago · rules 995398eba69f

Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.

  return spawn(options.executable, buildChromiumLaunchArgs(options), {

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

  return spawn(options.executable, buildChromiumLaunchArgs(options), {

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add b2match-mcp -- npx -y b2match-mcp

{
  "mcpServers": {
    "b2match-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "b2match-mcp"
      ]
    }
  }
}

[mcp_servers.b2match-mcp]
command = "npx"
args = ["-y", "b2match-mcp"]

{
  "mcpServers": {
    "b2match-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "b2match-mcp"
      ]
    }
  }
}

{
  "servers": {
    "b2match-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "b2match-mcp"
      ]
    }
  }
}