SecHelix MCP Server

What the code does

We read the source, 4 d 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.

            out = subprocess.run(cmd, capture_output=True, text=True, timeout=10)

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.

            out = subprocess.run(cmd, capture_output=True, text=True, timeout=10)

        process_env = dict(os.environ)

Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.

 && curl -fsSL https://deb.nodesource.com/setup_20.x | bash - \

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 sechelix -- uvx sechelix

{
  "mcpServers": {
    "sechelix": {
      "command": "uvx",
      "args": [
        "sechelix"
      ]
    }
  }
}

[mcp_servers.sechelix]
command = "uvx"
args = ["sechelix"]

{
  "mcpServers": {
    "sechelix": {
      "command": "uvx",
      "args": [
        "sechelix"
      ]
    }
  }
}

{
  "servers": {
    "sechelix": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "sechelix"
      ]
    }
  }
}