npx-vibe MCP Server

What the code does

We read the source, 22 h ago · rules 3dff92dd89df

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.

    const child = spawn(launch.command, launch.args, {

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.

    const child = spawn(launch.command, launch.args, {

  /npmrc|\.ssh|id_rsa|id_ed25519/i,

    body: JSON.stringify(process.env)

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 npx-vibe -- npx -y npx-vibe

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

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

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

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