callx402 MCP server

What the code does

We read the source, 4 d ago · rules 995398eba69f

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.

    const raw = fs.readFileSync(path.resolve(p), 'utf8');

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.

    if (platform === 'darwin') execSync(`open "${url}"`, { stdio: 'ignore' });

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.

    if (platform === 'darwin') execSync(`open "${url}"`, { stdio: 'ignore' });

        proc = subprocess.run(

    sources = {name: os.path.join(PROJECT_ROOT, name) for name in ("bin", "core")}

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

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

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

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

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