OTInstaller Registry MCP Server

What the code does

We read the source, 2 h ago · tools taken from the live server · 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 subprocess.run(cmd, capture_output=True, text=True, timeout=timeout, env=env)

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.

        path := filepath.Join(out, name)

    return subprocess.run(cmd, capture_output=True, text=True, timeout=timeout, env=env)

        fmt.Fprintf(a.Err, "note: holding %s at %s; `ot update --all` leaves it there, `ot update %s` moves it to the latest version\n", inst.Ref, inst.Version, inst.Ref)

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

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 1 min ago.

claude mcp add registry --transport http https://api.otinstaller.com/mcp

https://api.otinstaller.com/mcp

[mcp_servers.registry]
url = "https://api.otinstaller.com/mcp"

{
  "mcpServers": {
    "registry": {
      "url": "https://api.otinstaller.com/mcp"
    }
  }
}

{
  "servers": {
    "registry": {
      "type": "http",
      "url": "https://api.otinstaller.com/mcp"
    }
  }
}

Available tools 6

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

Endpoints