MQ-Sentinel MCP Server

What the code does

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

            proc = subprocess.run(  # noqa: S603 — argv list, no shell, allowlisted

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.

            proc = subprocess.run(  # noqa: S603 — argv list, no shell, allowlisted

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 mq-sentinel -- uvx mq-sentinel

{
  "mcpServers": {
    "mq-sentinel": {
      "command": "uvx",
      "args": [
        "mq-sentinel"
      ]
    }
  }
}

[mcp_servers.mq-sentinel]
command = "uvx"
args = ["mq-sentinel"]

{
  "mcpServers": {
    "mq-sentinel": {
      "command": "uvx",
      "args": [
        "mq-sentinel"
      ]
    }
  }
}

{
  "servers": {
    "mq-sentinel": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "mq-sentinel"
      ]
    }
  }
}

Optional settings from the registry entry, left out of the block above: MQS_AUTH_DISABLE_AUTH_FOR_LOCAL_DEV (Set true for local demo only. Refused when environment=prod), MQS_SERVER_ENVIRONMENT (dev | staging | prod — used in audit and RBAC).