Tapp MCP Server

What the code does

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

A value the model can set ends up inside a file or shell call. That is not a flaw by itself — for a terminal server it is the job — but it is where things go wrong when it is not.

        fs.writeFileSync(p, r.image.data);

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(command, 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.

    fs.createReadStream(path.join(root, file)).pipe(response);

  const child = spawn(invocation[0], invocation[1], { detached: true, stdio: "ignore", shell: false });

    .readdirSync(capturesDir, { withFileTypes: true })

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 tapp -- npx -y tapp-mcp

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

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

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

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