docker-mcp-server 2.1.0__tar.gz → 2.1.2__tar.gz

docker_mcp_server-2.1.2/.claude/settings.json

@@ -0,0 +1,15 @@
+{
+  "hooks": {
+    "PostToolUse": [
+      {
+        "matcher": "Edit|Write|MultiEdit",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "python3 -c \"import json,sys,os; d=json.load(sys.stdin); fp=(d.get('tool_input') or {}).get('file_path',''); root=os.environ.get('CLAUDE_PROJECT_DIR') or os.getcwd(); print(json.dumps({'hookSpecificOutput':{'hookEventName':'PostToolUse','additionalContext':'You edited CLAUDE.md \\u2014 MIRROR RULE: make the equivalent change in .github/copilot-instructions.md (it drives GitHub Copilot review of every PR). Treat the change as incomplete until both files reflect it.'}})) if fp and os.path.normpath(os.path.join(root, fp)) == os.path.normpath(os.path.join(root, 'CLAUDE.md')) else None\""
+          }
+        ]
+      }
+    ]
+  }
+}

{docker_mcp_server-2.1.0 → docker_mcp_server-2.1.2}/.github/PULL_REQUEST_TEMPLATE.md

@@ -9,6 +9,6 @@
 ## Checklist
 
 - [ ] `uv run pytest -v`, `uv run ruff check .`, `uv run ruff format --check .`, and `uv run pyright` all pass locally
-- [ ] If this adds or changes a tool: the ["Checklist when adding a new tool module"](https://github.com/GavinLucas/docker-mcp/blob/main/CONTRIBUTING.md#checklist-when-adding-a-new-tool-module) in `CONTRIBUTING.md` has been followed (tests, prompts, resources, README, naming convention)
+- [ ] If this adds or changes a tool: the ["Checklist when adding a new tool module"](https://github.com/L337-org/docker-mcp/blob/main/CONTRIBUTING.md#checklist-when-adding-a-new-tool-module) in `CONTRIBUTING.md` has been followed (tests, prompts, resources, README, naming convention)
 - [ ] If this changes project structure, conventions, env vars, or the tool/prompt/resource surface: both `CLAUDE.md` and `.github/copilot-instructions.md` are updated (see the mirror rule at the top of `CLAUDE.md`)
 - [ ] If this changes a dependency: `uv.lock` is updated (`uv lock`) and committed alongside `pyproject.toml`

{docker_mcp_server-2.1.0 → docker_mcp_server-2.1.2}/.github/copilot-instructions.md

@@ -4,7 +4,7 @@ This file provides guidance to GitHub Copilot when working with code in this rep
 
 ## Project
 
-`docker-mcp` is a Python MCP (Model Context Protocol) server that exposes the Docker SDK for Python — plus selected docker CLI features (Compose, Context, Buildx, Scout) and direct OCI-registry HTTPS access — as MCP tools. It requires Python >=3.14 and is managed with `uv`. It is published to PyPI as **`docker-mcp-server`** and as a container image to GHCR (`ghcr.io/gavinlucas/docker-mcp-server`), mirrored to Docker Hub (`gavinlucas/docker-mcp-server`) when the opt-in `DOCKERHUB_*` release secrets are configured (the import package stays `docker_mcp`, the repo stays `…/docker-mcp`); two console scripts — `docker-mcp` and `docker-mcp-server` — both target `docker_mcp:main`. A third distribution channel packages the server as a **Claude Desktop Extension (`.mcpb`)** attached to each GitHub Release (see "Desktop Extension (MCPB)" below). A fourth channel (**Homebrew tap**) exists in `gavinlucas/homebrew-tap` but is currently **paused** — see "Homebrew tap" below.
+`docker-mcp` is a Python MCP (Model Context Protocol) server that exposes the Docker SDK for Python — plus selected docker CLI features (Compose, Context, Buildx, Scout) and direct OCI-registry HTTPS access — as MCP tools. It requires Python >=3.14 and is managed with `uv`. It is published to PyPI as **`docker-mcp-server`** and as a container image to GHCR (`ghcr.io/l337-org/docker-mcp-server`), mirrored to Docker Hub (`gavinlucas/docker-mcp-server`) when the opt-in `DOCKERHUB_*` release secrets are configured (the import package stays `docker_mcp`, the repo stays `…/docker-mcp`); two console scripts — `docker-mcp` and `docker-mcp-server` — both target `docker_mcp:main`. A third distribution channel packages the server as a **Claude Desktop Extension (`.mcpb`)** attached to each GitHub Release (see "Desktop Extension (MCPB)" below). A fourth channel (**Homebrew tap**) exists in `gavinlucas/homebrew-tap` but is currently **paused** — see "Homebrew tap" below.
 
 The `docker` dep uses the `[ssh]` extra (paramiko), so `DOCKER_HOST=ssh://…` works via a pure-Python transport (no system `ssh` binary; works in the container images). docker-py auto-selects paramiko for `ssh://`, so there's no transport code — only the `ssh://` branch in `system._connection_help`. CLI-backed tools (Compose, Buildx, Context, Scout) shell out to `docker`, which would otherwise need the system `ssh` client — instead, `_cli.py:run_docker` detects `DOCKER_HOST=ssh://…` and routes the subprocess through a per-call local TCP proxy (`docker_mcp/tools/_ssh_proxy.py`) that opens its own paramiko connection and runs `docker system dial-stdio` over it, so the CLI authenticates the same way the docker-py-backed tools do, with no system `ssh` binary involved (except a `ProxyCommand` in `~/.ssh/config` for bastion/jump-host setups, which paramiko runs as an external command — commonly `ssh -W %h:%p ...` — for both tool families alike).
 
@@ -97,11 +97,11 @@ The infrastructure exists (`scripts/docker-mcp-server.rb.tpl`, `.github/workflow
 
 ### MCP Registry (`server.json`)
 
-A discovery listing in the official MCP Registry (`registry.modelcontextprotocol.io`), which stores only metadata pointing at the existing artifacts. `server.json` (repo root, name `io.github.GavinLucas/docker-mcp-server`) declares three package types — `pypi`, `oci` (GHCR image), `mcpb` (release `.mcpb`). The `registry` job in `.github/workflows/publish.yaml` stamps the tag version + the published `.mcpb`'s `fileSha256` into `server.json`, authenticates via GitHub OIDC (`id-token: write`, no secret), and runs `mcp-publisher publish`. Ownership is verified per package against `server.json`'s `name`, so three markers must equal it: the `<!-- mcp-name: … -->` comment in `README.md` (PyPI), the `io.modelcontextprotocol.server.name` image label in the `images` job (OCI), and the `.mcpb` URL + hash (MCPB). Keep them in sync with `server.json`'s `name`.
+A discovery listing in the official MCP Registry (`registry.modelcontextprotocol.io`), which stores only metadata pointing at the existing artifacts. `server.json` (repo root, name `io.github.L337-org/docker-mcp-server`) declares three package types — `pypi`, `oci` (GHCR image), `mcpb` (release `.mcpb`). The `registry` job in `.github/workflows/publish.yaml` stamps the tag version + the published `.mcpb`'s `fileSha256` into `server.json`, authenticates via GitHub OIDC (`id-token: write`, no secret), and runs `mcp-publisher publish`. Ownership is verified per package against `server.json`'s `name`, so three markers must equal it: the `<!-- mcp-name: … -->` comment in `README.md` (PyPI), the `io.modelcontextprotocol.server.name` image label in the `images` job (OCI), and the `.mcpb` URL + hash (MCPB). Keep them in sync with `server.json`'s `name`.
 
 ### Release pipeline (`.github/workflows/publish.yaml`)
 
-All publishing runs through one workflow on each **published GitHub Release**: `preflight` → `pypi` ∥ `images`(→`dockerhub-description`) ∥ `mcpb` → `registry` → `verify`, plus a `notify` job on failure. `preflight` resolves the tag once (every job checks out **the tag ref**) and fails fast if the tag disagrees with the committed `pyproject.toml` / `manifest.json` / `uv.lock` self-entry versions — preventing a split-brain release where PyPI ships the pyproject version and everything else ships the tag version. `verify` confirms all channels serve the version (PyPI JSON API, both GHCR tags, `.mcpb` asset + checksum, registry listing). `notify` files a deduplicated `ci-failure` + `wf:release` issue via `.github/actions/file-failure-issue` (one open issue per failure stream; a scheduled Claude responder routine polls `ci-failure` issues). Re-runs go through `workflow_dispatch` with the tag and are idempotent end-to-end (`skip-existing` on PyPI, re-pushed image tags, `--clobber` on the `.mcpb`, duplicate-tolerant registry publish). **PyPI Trusted Publishing pins the workflow *filename* (`publish.yaml`)** — when reviewing a PR that renames or splits this workflow, flag that the PyPI trusted publisher must be updated first. `.github/release.yml` (GitHub's release-*notes* config — a different file) groups generated notes; `publish-homebrew.yaml` (paused, dispatch-only) stays separate. When reviewing changes to the pipeline's job graph, ownership markers, or re-run semantics, check this section stays accurate.
+All publishing runs through one workflow on each **published GitHub Release**: `preflight` → `pypi` ∥ `images`(→`dockerhub-description`) ∥ `mcpb` → `registry` → `verify`, plus a `notify` job on failure. `preflight` resolves the tag once (every job checks out **the tag ref**) and fails fast if the tag disagrees with the committed `pyproject.toml` / `manifest.json` / `uv.lock` self-entry versions — preventing a split-brain release where PyPI ships the pyproject version and everything else ships the tag version. It also refuses to run when `github.repository_owner` isn't `L337-org`, so a release published from a fork (or mis-timed around a repo transfer) fails before anything ships rather than half-publishing. `verify` confirms all channels serve the version (PyPI JSON API, both GHCR tags, `.mcpb` asset + checksum, registry listing). `notify` files a deduplicated `ci-failure` + `wf:release` issue via `.github/actions/file-failure-issue` (one open issue per failure stream; a scheduled Claude responder routine polls `ci-failure` issues). Re-runs go through `workflow_dispatch` with the tag and are idempotent end-to-end (`skip-existing` on PyPI, re-pushed image tags, `--clobber` on the `.mcpb`, duplicate-tolerant registry publish). **PyPI Trusted Publishing pins the workflow *filename* (`publish.yaml`)** — when reviewing a PR that renames or splits this workflow, flag that the PyPI trusted publisher must be updated first. `.github/release.yml` (GitHub's release-*notes* config — a different file) groups generated notes; `publish-homebrew.yaml` (paused, dispatch-only) stays separate. When reviewing changes to the pipeline's job graph, ownership markers, or re-run semantics, check this section stays accurate.
 
 ## Conventions
 

{docker_mcp_server-2.1.0 → docker_mcp_server-2.1.2}/.github/workflows/canary.yaml

@@ -41,7 +41,7 @@ jobs:
         uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
 
       - name: Set up uv
-        uses: astral-sh/setup-uv@fac544c07dec837d0ccb6301d7b5580bf5edae39 # v8.2.0
+        uses: astral-sh/setup-uv@11f9893b081a58869d3b5fccaea48c9e9e46f990 # v8.3.2
         with:
           # Pinned (matching the Dockerfile's uv image tag) so this step never needs the
           # live "resolve latest" fetch to raw.githubusercontent.com — that network call
@@ -102,7 +102,7 @@ jobs:
         os: [macos-latest, macos-15-intel, windows-latest]
     steps:
       - name: Set up uv
-        uses: astral-sh/setup-uv@fac544c07dec837d0ccb6301d7b5580bf5edae39 # v8.2.0
+        uses: astral-sh/setup-uv@11f9893b081a58869d3b5fccaea48c9e9e46f990 # v8.3.2
         with:
           # This job deliberately has no checkout — it tests the *published* package, not the
           # repo — so disable the repo-keyed cache and the empty-workdir warning it triggers.

{docker_mcp_server-2.1.0 → docker_mcp_server-2.1.2}/.github/workflows/codeql.yaml

@@ -31,12 +31,12 @@ jobs:
         uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
 
       - name: Initialize CodeQL
-        uses: github/codeql-action/init@54f647b7e1bb85c95cddabcd46b0c578ec92bc1a # v4
+        uses: github/codeql-action/init@99df26d4f13ea111d4ec1a7dddef6063f76b97e9 # v4
         with:
           languages: ${{ matrix.language }}
 
       - name: Autobuild
-        uses: github/codeql-action/autobuild@54f647b7e1bb85c95cddabcd46b0c578ec92bc1a # v4
+        uses: github/codeql-action/autobuild@99df26d4f13ea111d4ec1a7dddef6063f76b97e9 # v4
 
       - name: Perform CodeQL Analysis
-        uses: github/codeql-action/analyze@54f647b7e1bb85c95cddabcd46b0c578ec92bc1a # v4
+        uses: github/codeql-action/analyze@99df26d4f13ea111d4ec1a7dddef6063f76b97e9 # v4

{docker_mcp_server-2.1.0 → docker_mcp_server-2.1.2}/.github/workflows/premerge.yaml

@@ -33,7 +33,7 @@ jobs:
           python-version: "3.14"
 
       - name: Set up uv
-        uses: astral-sh/setup-uv@fac544c07dec837d0ccb6301d7b5580bf5edae39 # v8.2.0
+        uses: astral-sh/setup-uv@11f9893b081a58869d3b5fccaea48c9e9e46f990 # v8.3.2
 
       - name: Install dependencies
         # --locked fails if uv.lock disagrees with pyproject.toml instead of silently
@@ -62,7 +62,7 @@ jobs:
           python-version: "3.14"
 
       - name: Set up uv
-        uses: astral-sh/setup-uv@fac544c07dec837d0ccb6301d7b5580bf5edae39 # v8.2.0
+        uses: astral-sh/setup-uv@11f9893b081a58869d3b5fccaea48c9e9e46f990 # v8.3.2
 
       - name: Install dependencies
         # --locked fails if uv.lock disagrees with pyproject.toml instead of silently
@@ -91,7 +91,7 @@ jobs:
           python-version: "3.14"
 
       - name: Set up uv
-        uses: astral-sh/setup-uv@fac544c07dec837d0ccb6301d7b5580bf5edae39 # v8.2.0
+        uses: astral-sh/setup-uv@11f9893b081a58869d3b5fccaea48c9e9e46f990 # v8.3.2
 
       - name: Install dependencies
         # --locked fails if uv.lock disagrees with pyproject.toml instead of silently
@@ -158,7 +158,7 @@ jobs:
           python-version: "3.14"
 
       - name: Set up uv
-        uses: astral-sh/setup-uv@fac544c07dec837d0ccb6301d7b5580bf5edae39 # v8.2.0
+        uses: astral-sh/setup-uv@11f9893b081a58869d3b5fccaea48c9e9e46f990 # v8.3.2
 
       - name: Install dependencies
         # --locked fails if uv.lock disagrees with pyproject.toml instead of silently

{docker_mcp_server-2.1.0 → docker_mcp_server-2.1.2}/.github/workflows/publish-homebrew.yaml

@@ -64,7 +64,7 @@ jobs:
         run: git fetch --depth=1 origin main && git checkout origin/main -- scripts/docker-mcp-server.rb.tpl
 
       - name: Install uv
-        uses: astral-sh/setup-uv@fac544c07dec837d0ccb6301d7b5580bf5edae39 # v8.2.0
+        uses: astral-sh/setup-uv@11f9893b081a58869d3b5fccaea48c9e9e46f990 # v8.3.2
 
       - name: Resolve version, Python target, and macOS floor
         run: |

{docker_mcp_server-2.1.0 → docker_mcp_server-2.1.2}/.github/workflows/publish.yaml

@@ -15,7 +15,7 @@ name: Release
 # channel actually converged so a partial release is loud instead of silent.
 #
 # PyPI Trusted Publishing pins the WORKFLOW FILENAME: the trusted publisher on PyPI must list
-# `publish.yaml` (owner GavinLucas, repo docker-mcp). If the pypi job fails with an OIDC
+# `publish.yaml` (owner L337-org, repo docker-mcp). If the pypi job fails with an OIDC
 # `invalid-publisher` error, that registration is missing — add it on PyPI, then re-run.
 #
 # Partial-failure semantics: no rollback is attempted (PyPI files are immutable anyway). The
@@ -55,6 +55,16 @@ jobs:
       tag: ${{ steps.resolve.outputs.tag }}
       version: ${{ steps.resolve.outputs.version }}
     steps:
+      - name: Assert canonical repository owner
+        # The GHCR path, MCP Registry name, and PyPI trusted publisher are all pinned to the
+        # L337-org identity. Publishing from anywhere else (a fork, or the window between the
+        # identity sweep landing and the repo transfer) would half-publish — PyPI first, then
+        # fail on GHCR/registry. Fail fast before anything ships; every other job needs preflight.
+        if: github.repository_owner != 'L337-org'
+        run: |
+          echo "::error::This pipeline publishes the L337-org identity but is running in ${GITHUB_REPOSITORY}. Refusing to publish."
+          exit 1
+
       - name: Resolve tag and version
         id: resolve
         env:
@@ -142,7 +152,7 @@ jobs:
           python-version: "3.14"
 
       - name: Install uv
-        uses: astral-sh/setup-uv@fac544c07dec837d0ccb6301d7b5580bf5edae39 # v8.2.0
+        uses: astral-sh/setup-uv@11f9893b081a58869d3b5fccaea48c9e9e46f990 # v8.3.2
 
       - name: Build sdist and wheel
         run: uv build
@@ -160,7 +170,7 @@ jobs:
     # Publishes the container images:
     #   full     -> docker-mcp-server:latest    + :<version>
     #   no-scout -> docker-mcp-server:no-scout   + :<version>-no-scout
-    # Images go to GHCR (ghcr.io/gavinlucas/docker-mcp-server) always, and are mirrored to Docker
+    # Images go to GHCR (ghcr.io/l337-org/docker-mcp-server) always, and are mirrored to Docker
     # Hub (docker.io/gavinlucas/docker-mcp-server) when the DOCKERHUB_USER / DOCKERHUB_TOKEN repo
     # secrets are set. The Hub mirror is opt-in: with the secrets unset the Hub login/tags steps
     # are skipped and only GHCR is pushed, so a release never fails for lack of Hub credentials.
@@ -202,7 +212,7 @@ jobs:
           VERSION: ${{ needs.preflight.outputs.version }}
         run: |
           # GHCR always; mirror to Docker Hub only when the credentials are present (see header).
-          registries="ghcr.io/gavinlucas/docker-mcp-server"
+          registries="ghcr.io/l337-org/docker-mcp-server"
           if [ -n "$DOCKERHUB_USER" ] && [ -n "$DOCKERHUB_TOKEN" ]; then
             registries="$registries docker.io/gavinlucas/docker-mcp-server"
           fi
@@ -254,9 +264,9 @@ jobs:
           # match `name` in server.json so the registry can verify we own this image (see the
           # registry job below). image.version is the v-stripped version, matching the image tags.
           labels: |
-            org.opencontainers.image.source=https://github.com/GavinLucas/docker-mcp
+            org.opencontainers.image.source=https://github.com/L337-org/docker-mcp
             org.opencontainers.image.version=${{ needs.preflight.outputs.version }}
-            io.modelcontextprotocol.server.name=io.github.GavinLucas/docker-mcp-server
+            io.modelcontextprotocol.server.name=io.github.L337-org/docker-mcp-server
           build-args: |
             INSTALL_CLI=${{ matrix.install_cli }}
             INSTALL_SCOUT=${{ matrix.install_scout }}
@@ -341,7 +351,7 @@ jobs:
     # Publishes server.json to the official MCP Registry (registry.modelcontextprotocol.io). The
     # registry stores only metadata — it points at the artifacts the sibling jobs above publish —
     # and verifies we own each listed package via a marker that must equal server.json's `name`
-    # (io.github.GavinLucas/docker-mcp-server):
+    # (io.github.L337-org/docker-mcp-server):
     #   - pypi  -> the `<!-- mcp-name: ... -->` comment in README.md (PyPI long-description)
     #   - oci   -> the io.modelcontextprotocol.server.name image label (set in the images job)
     #   - mcpb  -> the .mcpb release-asset URL (must contain "mcp") + a matching fileSha256
@@ -393,9 +403,9 @@ jobs:
             .version = $v
             | (.packages[] | select(.registryType == "pypi") | .version) = $v
             | (.packages[] | select(.registryType == "oci")  | .identifier)
-                = "ghcr.io/gavinlucas/docker-mcp-server:\($v)"
+                = "ghcr.io/l337-org/docker-mcp-server:\($v)"
             | (.packages[] | select(.registryType == "mcpb") | .identifier)
-                = "https://github.com/GavinLucas/docker-mcp/releases/download/\($tag)/docker-mcp-server-\($v).mcpb"
+                = "https://github.com/L337-org/docker-mcp/releases/download/\($tag)/docker-mcp-server-\($v).mcpb"
             | (.packages[] | select(.registryType == "mcpb") | .fileSha256) = $sha
           ' server.json > server.tmp && mv server.tmp server.json
           echo "--- server.json ---"; cat server.json
@@ -481,7 +491,7 @@ jobs:
           for tag in "${VERSION}" "${VERSION}-no-scout"; do
             ok=""
             for i in $(seq 1 5); do
-              if docker buildx imagetools inspect "ghcr.io/gavinlucas/docker-mcp-server:${tag}" >/dev/null 2>&1; then
+              if docker buildx imagetools inspect "ghcr.io/l337-org/docker-mcp-server:${tag}" >/dev/null 2>&1; then
                 echo "GHCR OK: :${tag}"; ok=1; break
               fi
               echo "::notice::GHCR tag :${tag} not readable yet (attempt $i/5); waiting 15s"
@@ -512,7 +522,7 @@ jobs:
       - name: Verify the MCP Registry lists the version
         run: |
           set -euo pipefail
-          url="https://registry.modelcontextprotocol.io/v0/servers?search=io.github.GavinLucas/docker-mcp-server"
+          url="https://registry.modelcontextprotocol.io/v0/servers?search=io.github.L337-org/docker-mcp-server"
           for i in $(seq 1 5); do
             if curl -fsS "$url" | jq -e --arg v "$VERSION" \
                 '.servers[] | select(.server.version == $v)' >/dev/null; then

{docker_mcp_server-2.1.0 → docker_mcp_server-2.1.2}/CLAUDE.md

@@ -11,7 +11,7 @@ This file provides guidance to Claude Code (claude.ai/code) when working with co
 
 ## Project
 
-`docker-mcp` is a Python MCP server (requires Python >=3.14) managed with `uv` that exposes the Docker SDK for Python as MCP tools. The entry point is the `docker_mcp` package, run with `python -m docker_mcp` or via the installed console script. It is **published to PyPI as `docker-mcp-server`** (the `docker-mcp` name was already taken) and as a container image to GHCR (`ghcr.io/gavinlucas/docker-mcp-server`), mirrored to Docker Hub (`gavinlucas/docker-mcp-server`) when the opt-in `DOCKERHUB_*` release secrets are configured; the import package stays `docker_mcp` and the repo stays `…/docker-mcp`. Two console scripts are installed — `docker-mcp` and `docker-mcp-server` — both targeting `docker_mcp:main`. A third channel packages the server as a **Claude Desktop Extension (`.mcpb`)** attached to each GitHub Release — see "Desktop Extension (MCPB bundle)" below. A fourth channel (**Homebrew tap**) exists in `gavinlucas/homebrew-tap` but is currently **paused** — see "Homebrew tap" below.
+`docker-mcp` is a Python MCP server (requires Python >=3.14) managed with `uv` that exposes the Docker SDK for Python as MCP tools. The entry point is the `docker_mcp` package, run with `python -m docker_mcp` or via the installed console script. It is **published to PyPI as `docker-mcp-server`** (the `docker-mcp` name was already taken) and as a container image to GHCR (`ghcr.io/l337-org/docker-mcp-server`), mirrored to Docker Hub (`gavinlucas/docker-mcp-server`) when the opt-in `DOCKERHUB_*` release secrets are configured; the import package stays `docker_mcp` and the repo stays `…/docker-mcp`. Two console scripts are installed — `docker-mcp` and `docker-mcp-server` — both targeting `docker_mcp:main`. A third channel packages the server as a **Claude Desktop Extension (`.mcpb`)** attached to each GitHub Release — see "Desktop Extension (MCPB bundle)" below. A fourth channel (**Homebrew tap**) exists in `gavinlucas/homebrew-tap` but is currently **paused** — see "Homebrew tap" below.
 
 The `docker` dependency is pulled with its `[ssh]` extra (paramiko), so `DOCKER_HOST=ssh://…` works through a pure-Python transport — no system `ssh` binary, identical on the host and in the container images. docker-py auto-selects paramiko for `ssh://` when present, so there is no transport code to maintain (just the `ssh://` branch in `system._connection_help`). CLI-backed tools (Compose, Buildx, Context, Scout) shell out to `docker`, which would otherwise use the *system* `ssh` — instead, `_cli.py:run_docker` detects `DOCKER_HOST=ssh://…` and routes the subprocess through a per-call local TCP proxy (`docker_mcp/tools/_ssh_proxy.py`) that opens its own paramiko connection (mirroring docker-py's `SSHHTTPAdapter` defaults) and runs `docker system dial-stdio` over it, so the CLI authenticates identically to the docker-py-backed tools with no system `ssh` binary involved (the one exception being a `ProxyCommand` in `~/.ssh/config` for bastion/jump-host setups, which paramiko runs as an external command — commonly `ssh -W %h:%p ...` — same as it would for the docker-py-backed tools).
 
@@ -163,11 +163,11 @@ The infrastructure exists (`scripts/docker-mcp-server.rb.tpl`, `.github/workflow
 
 ### MCP Registry (`server.json`)
 
-A discovery listing in the official MCP Registry (`registry.modelcontextprotocol.io`), which stores only **metadata** pointing at the artifacts the other channels already publish — so it's not a fourth artifact, just an index entry covering all of them. `server.json` (repo root, server name `io.github.GavinLucas/docker-mcp-server`) declares three package types in one entry: `pypi` (`docker-mcp-server`), `oci` (the GHCR image), and `mcpb` (the release `.mcpb`). The `registry` job in `.github/workflows/publish.yaml` stamps the tag version and the published `.mcpb`'s `fileSha256` into `server.json`, authenticates via **GitHub OIDC** (`id-token: write`, no stored secret), and runs `mcp-publisher publish`. The registry verifies we own each listed package by matching a marker against `server.json`'s `name`, so three markers must stay equal to it: the `<!-- mcp-name: … -->` comment in `README.md` (PyPI long-description), the `io.modelcontextprotocol.server.name` image label in the `images` job (OCI), and the `.mcpb` URL (must contain "mcp") + its hash (MCPB). The job runs `needs: [pypi, images, mcpb]`, so all three markers are live before it starts — its short retries only absorb registry-side read lag. **If `server.json`'s name/markers or the package set change, update this section.**
+A discovery listing in the official MCP Registry (`registry.modelcontextprotocol.io`), which stores only **metadata** pointing at the artifacts the other channels already publish — so it's not a fourth artifact, just an index entry covering all of them. `server.json` (repo root, server name `io.github.L337-org/docker-mcp-server`) declares three package types in one entry: `pypi` (`docker-mcp-server`), `oci` (the GHCR image), and `mcpb` (the release `.mcpb`). The `registry` job in `.github/workflows/publish.yaml` stamps the tag version and the published `.mcpb`'s `fileSha256` into `server.json`, authenticates via **GitHub OIDC** (`id-token: write`, no stored secret), and runs `mcp-publisher publish`. The registry verifies we own each listed package by matching a marker against `server.json`'s `name`, so three markers must stay equal to it: the `<!-- mcp-name: … -->` comment in `README.md` (PyPI long-description), the `io.modelcontextprotocol.server.name` image label in the `images` job (OCI), and the `.mcpb` URL (must contain "mcp") + its hash (MCPB). The job runs `needs: [pypi, images, mcpb]`, so all three markers are live before it starts — its short retries only absorb registry-side read lag. **If `server.json`'s name/markers or the package set change, update this section.**
 
 ### Release pipeline (`.github/workflows/publish.yaml`)
 
-All publishing runs through one workflow on each **published GitHub Release** (nothing publishes without that human step): `preflight` → `pypi` ∥ `images`(→`dockerhub-description`) ∥ `mcpb` → `registry` → `verify`, with a `notify` job on failure. `preflight` resolves the tag once for every job (each checks out **the tag ref**, not the event SHA) and fails fast if the tag disagrees with the committed `pyproject.toml` / `manifest.json` / `uv.lock` self-entry versions — preventing a split-brain release (PyPI ships the pyproject version; every other channel ships the tag version). `verify` confirms all four channels actually serve the version (PyPI JSON API, both GHCR tags, the `.mcpb` asset + checksum, the registry listing) so a partial release is loud. `notify` files (or comments on) a deduplicated issue labeled `ci-failure` + `wf:release` via the composite action `.github/actions/file-failure-issue` — one open issue per failure stream; a scheduled Claude responder routine polls `ci-failure` issues. Re-run a failed release via `workflow_dispatch` with the tag: every job is idempotent (`skip-existing` on PyPI, re-pushed image tags, `--clobber` on the `.mcpb`, duplicate-tolerant registry publish). **PyPI Trusted Publishing pins the workflow *filename*** — the trusted publisher on PyPI must name `publish.yaml`; if the `pypi` job fails OIDC, that registration is missing. Version-bump checklist for a release: edit `pyproject.toml` + `manifest.json`, run `uv lock`, merge, then publish a GitHub Release whose tag matches (`.github/release.yml` — GitHub's release-*notes* config, a different file — groups the generated notes, Dependabot PRs under "Dependencies"). `publish-homebrew.yaml` (paused, dispatch-only) stays separate. **When the pipeline's job graph, markers, or re-run semantics change, update this section.**
+All publishing runs through one workflow on each **published GitHub Release** (nothing publishes without that human step): `preflight` → `pypi` ∥ `images`(→`dockerhub-description`) ∥ `mcpb` → `registry` → `verify`, with a `notify` job on failure. `preflight` resolves the tag once for every job (each checks out **the tag ref**, not the event SHA) and fails fast if the tag disagrees with the committed `pyproject.toml` / `manifest.json` / `uv.lock` self-entry versions — preventing a split-brain release (PyPI ships the pyproject version; every other channel ships the tag version). It also refuses to run when `github.repository_owner` isn't `L337-org`, so a release published from a fork (or mis-timed around a repo transfer) fails before anything ships rather than half-publishing. `verify` confirms all four channels actually serve the version (PyPI JSON API, both GHCR tags, the `.mcpb` asset + checksum, the registry listing) so a partial release is loud. `notify` files (or comments on) a deduplicated issue labeled `ci-failure` + `wf:release` via the composite action `.github/actions/file-failure-issue` — one open issue per failure stream; a scheduled Claude responder routine polls `ci-failure` issues. Re-run a failed release via `workflow_dispatch` with the tag: every job is idempotent (`skip-existing` on PyPI, re-pushed image tags, `--clobber` on the `.mcpb`, duplicate-tolerant registry publish). **PyPI Trusted Publishing pins the workflow *filename*** — the trusted publisher on PyPI must name `publish.yaml`; if the `pypi` job fails OIDC, that registration is missing. Version-bump checklist for a release: edit `pyproject.toml` + `manifest.json`, run `uv lock`, merge, then publish a GitHub Release whose tag matches (`.github/release.yml` — GitHub's release-*notes* config, a different file — groups the generated notes, Dependabot PRs under "Dependencies"). `publish-homebrew.yaml` (paused, dispatch-only) stays separate. **When the pipeline's job graph, markers, or re-run semantics change, update this section.**
 
 ## Conventions
 

{docker_mcp_server-2.1.0 → docker_mcp_server-2.1.2}/CONTRIBUTING.md

@@ -185,4 +185,4 @@ It reads the version from `pyproject.toml`, creates `dist/` if needed, writes a
 
 ## Reporting issues
 
-Bug reports and feature requests have templates that you can choose when you [`create an issue`](https://github.com/GavinLucas/docker-mcp/issues/new/choose). Please select the correct issue type and follow the template.
+Bug reports and feature requests have templates that you can choose when you [`create an issue`](https://github.com/L337-org/docker-mcp/issues/new/choose). Please select the correct issue type and follow the template.

{docker_mcp_server-2.1.0 → docker_mcp_server-2.1.2}/DOCKERHUB.md

@@ -4,11 +4,11 @@ More than just a fully featured [MCP](https://modelcontextprotocol.io) server th
 
 It can manage multiple Docker daemons, e.g. both your local dev environment and also a remote production environment over TCP, TLS or SSH in a single session. It can also be configured to mark some daemons as read-only, so that you can monitor them without the risk of making accidental changes. It also exposes things like logs and stats as resources so that you can easily monitor and triage your environments with a few prompts.
 
-The server runs entirely on your machine and sends no telemetry. You are entirely in control — see the [Privacy Policy](https://github.com/GavinLucas/docker-mcp#privacy-policy).
+The server runs entirely on your machine and sends no telemetry. You are entirely in control — see the [Privacy Policy](https://github.com/L337-org/docker-mcp#privacy-policy).
 
-This image is the container distribution of the project. **Full documentation, configuration, and source are on GitHub: <https://github.com/GavinLucas/docker-mcp>.**
+This image is the container distribution of the project. **Full documentation, configuration, and source are on GitHub: <https://github.com/L337-org/docker-mcp>.**
 
-> The same images are published to GHCR as [`ghcr.io/gavinlucas/docker-mcp-server`](https://github.com/GavinLucas/docker-mcp/pkgs/container/docker-mcp-server) — identical content, so use whichever registry you prefer.
+> The same images are published to GHCR as [`ghcr.io/l337-org/docker-mcp-server`](https://github.com/L337-org/docker-mcp/pkgs/container/docker-mcp-server) — identical content, so use whichever registry you prefer.
 
 ## Quick start
 
@@ -72,14 +72,14 @@ Set these in the client's `env` block. Three switches restrict which tools are r
 
 `DOCKER_HOST` / `DOCKER_TLS_VERIFY` / `DOCKER_CERT_PATH` retarget the daemon (e.g. `-e DOCKER_HOST=tcp://remote-host:2375`).
 
-See the [full configuration reference](https://github.com/GavinLucas/docker-mcp#configuration) for the complete list and examples.
+See the [full configuration reference](https://github.com/L337-org/docker-mcp#configuration) for the complete list and examples.
 
 ## Security
 
-Connecting this server to an AI agent grants it the same access as a local Docker CLI session against the configured daemon — the daemon's socket is effectively root-equivalent on its host. Prefer pointing it at a daemon dedicated to workloads the agent may touch (a dev VM, a remote sandbox, Docker Desktop, a rootless install) rather than your production socket. See the [Security considerations](https://github.com/GavinLucas/docker-mcp#security-considerations) on GitHub before enabling the server.
+Connecting this server to an AI agent grants it the same access as a local Docker CLI session against the configured daemon — the daemon's socket is effectively root-equivalent on its host. Prefer pointing it at a daemon dedicated to workloads the agent may touch (a dev VM, a remote sandbox, Docker Desktop, a rootless install) rather than your production socket. See the [Security considerations](https://github.com/L337-org/docker-mcp#security-considerations) on GitHub before enabling the server.
 
 ## Links
 
-- **Source, full docs & issues:** <https://github.com/GavinLucas/docker-mcp>
-- **Also on PyPI** (run without a container): `uvx docker-mcp-server` — see the [README](https://github.com/GavinLucas/docker-mcp#using-the-server).
+- **Source, full docs & issues:** <https://github.com/L337-org/docker-mcp>
+- **Also on PyPI** (run without a container): `uvx docker-mcp-server` — see the [README](https://github.com/L337-org/docker-mcp#using-the-server).
 - **License & contributing:** see the GitHub repository.

{docker_mcp_server-2.1.0 → docker_mcp_server-2.1.2}/PKG-INFO

@@ -1,10 +1,10 @@
 Metadata-Version: 2.4
 Name: docker-mcp-server
-Version: 2.1.0
+Version: 2.1.2
 Summary: MCP server for managing Docker resources via the Docker SDK for Python
-Project-URL: Homepage, https://github.com/GavinLucas/docker-mcp
-Project-URL: Repository, https://github.com/GavinLucas/docker-mcp
-Project-URL: Issues, https://github.com/GavinLucas/docker-mcp/issues
+Project-URL: Homepage, https://github.com/L337-org/docker-mcp
+Project-URL: Repository, https://github.com/L337-org/docker-mcp
+Project-URL: Issues, https://github.com/L337-org/docker-mcp/issues
 Author: Gavin Lucas
 License-Expression: MIT
 License-File: LICENSE
@@ -26,13 +26,13 @@ Requires-Dist: mcp>=1.27.1
 Requires-Dist: requests>=2.26.0
 Description-Content-Type: text/markdown
 
-<img src="https://raw.githubusercontent.com/GavinLucas/docker-mcp/main/assets/icon.png" align="left" width="72" height="72" alt="">
+<img src="https://raw.githubusercontent.com/L337-org/docker-mcp/main/assets/icon.png" align="left" width="72" height="72" alt="">
 
 # docker-mcp-server
 
 [![docker-mcp MCP server](https://glama.ai/mcp/servers/GavinLucas/docker-mcp/badges/score.svg)](https://glama.ai/mcp/servers/GavinLucas/docker-mcp)
 
-<!-- mcp-name: io.github.GavinLucas/docker-mcp-server -->
+<!-- mcp-name: io.github.L337-org/docker-mcp-server -->
 
 More than just a fully featured [MCP](https://modelcontextprotocol.io) server that lets AI agents manage Docker — containers, images, networks, volumes, swarm services, secrets, configs, nodes, plugins, etc., it helps you create workflows to easily manage your Docker environments.
 
@@ -79,7 +79,7 @@ To pin a specific version, append `==<version>` to the package name (e.g. `docke
       "command": "uvx",
       "args": [
         "--from",
-        "git+https://github.com/GavinLucas/docker-mcp.git",
+        "git+https://github.com/L337-org/docker-mcp.git",
         "docker-mcp-server"
       ],
       "env": {}
@@ -93,7 +93,7 @@ To pin a specific revision, append `@<tag-or-commit>` to the git URL.
 ### Install as a Desktop Extension (.mcpb)
 
 For [Claude Desktop](https://claude.com/download), a one-click bundle is attached to each
-[GitHub Release](https://github.com/GavinLucas/docker-mcp/releases) as
+[GitHub Release](https://github.com/L337-org/docker-mcp/releases) as
 `docker-mcp-server-<version>.mcpb` (with a matching `.sha256`). Download it and drag it into
 **Settings → Extensions**, or use **Settings → Extensions → Advanced settings → Install extension…**
 and pick the file. The install dialog surfaces a **Docker host(s)** field and the read-only /
@@ -110,7 +110,7 @@ Docker context; set one endpoint (`ssh://user@host`) for a remote daemon, or lis
 Running the server as a container removes the Python / uv / git prerequisites entirely — the only
 thing the host needs is Docker, which you already have. Prebuilt multi-arch images (linux/amd64 +
 linux/arm64) are published on each release to **Docker Hub** (`gavinlucas/docker-mcp-server`) and
-**GHCR** (`ghcr.io/gavinlucas/docker-mcp-server`) — the two are identical. Point your MCP client at
+**GHCR** (`ghcr.io/l337-org/docker-mcp-server`) — the two are identical. Point your MCP client at
 `docker run`:
 
 ```json
@@ -131,14 +131,14 @@ linux/arm64) are published on each release to **Docker Hub** (`gavinlucas/docker
 
 `-i` is required (the server speaks MCP over stdio); `--rm` cleans up when the client disconnects. To
 pin a version, replace `:latest` with a release tag (e.g. `:1.5.1`). To pull from GHCR instead, use
-`ghcr.io/gavinlucas/docker-mcp-server:latest`.
+`ghcr.io/l337-org/docker-mcp-server:latest`.
 
-> **Image renamed.** As of 1.5.0 the image is published to `ghcr.io/gavinlucas/docker-mcp-server`
-> (matching the PyPI name). The old `ghcr.io/gavinlucas/docker-mcp` image is frozen at 1.4.0 and no
-> longer updated — point new pulls at `…/docker-mcp-server`.
+> **Image renamed.** As of 1.5.0 the image is published as `docker-mcp-server` (matching the PyPI
+> name). The old `ghcr.io/gavinlucas/docker-mcp` image is frozen at 1.4.0 and no longer updated —
+> point new pulls at `ghcr.io/l337-org/docker-mcp-server`.
 
 **Image variants.** Two variants are published to both registries (`gavinlucas/docker-mcp-server` on
-Docker Hub and `ghcr.io/gavinlucas/docker-mcp-server` on GHCR), both built from one `Dockerfile`. The
+Docker Hub and `ghcr.io/l337-org/docker-mcp-server` on GHCR), both built from one `Dockerfile`. The
 CLI-backed domains (Compose, Stack, Buildx, Scout, Context) shell out to the `docker` CLI and its
 plugins.
 
@@ -361,7 +361,7 @@ All of these go in the `env` block of the server entry in your MCP client config
       "command": "uvx",
       "args": [
         "--from",
-        "git+https://github.com/GavinLucas/docker-mcp.git",
+        "git+https://github.com/L337-org/docker-mcp.git",
         "docker-mcp-server"
       ],
       "env": {
@@ -379,7 +379,7 @@ Swap `DOCKER_MCP_SERVER_READONLY` for `DOCKER_MCP_SERVER_NO_DESTRUCTIVE` to allo
 ```bash
 claude mcp add docker-mcp-server-readonly \
   --env DOCKER_MCP_SERVER_READONLY=1 \
-  -- uvx --from git+https://github.com/GavinLucas/docker-mcp.git docker-mcp-server
+  -- uvx --from git+https://github.com/L337-org/docker-mcp.git docker-mcp-server
 ```
 
 ## Security considerations
@@ -407,10 +407,10 @@ Connecting this server to an AI agent grants it the same level of access as a lo
 | Channel | Link |
 |---------|------|
 | PyPI | [docker-mcp-server](https://pypi.org/project/docker-mcp-server/) |
-| GHCR (container) | [ghcr.io/gavinlucas/docker-mcp-server](https://github.com/GavinLucas/docker-mcp/pkgs/container/docker-mcp-server) |
+| GHCR (container) | [ghcr.io/l337-org/docker-mcp-server](https://github.com/L337-org/docker-mcp/pkgs/container/docker-mcp-server) |
 | Docker Hub (container) | [gavinlucas/docker-mcp-server](https://hub.docker.com/r/gavinlucas/docker-mcp-server) |
-| Desktop Extension (.mcpb) | [GitHub Releases](https://github.com/GavinLucas/docker-mcp/releases) |
-| Official MCP Registry | [io.github.GavinLucas/docker-mcp-server](https://registry.modelcontextprotocol.io/v0.1/servers/io.github.GavinLucas%2Fdocker-mcp-server/versions) |
+| Desktop Extension (.mcpb) | [GitHub Releases](https://github.com/L337-org/docker-mcp/releases) |
+| Official MCP Registry | [io.github.L337-org/docker-mcp-server](https://registry.modelcontextprotocol.io/v0.1/servers/io.github.L337-org%2Fdocker-mcp-server/versions) |
 | Glama | [docker-mcp-server](https://glama.ai/mcp/servers/GavinLucas/docker-mcp) |
 | mcp.so | [docker-mcp-server](https://mcp.so/server/docker-mcp-server/GavinLucas) |
 | awesome-mcp-servers | [punkpeye/awesome-mcp-servers](https://github.com/punkpeye/awesome-mcp-servers#cloud-platforms) |
@@ -419,8 +419,8 @@ Connecting this server to an AI agent grants it the same level of access as a lo
 
 docker-mcp-server collects no data, sends no telemetry, and has no author-operated backend. It runs
 locally and talks only to the Docker daemon and container registries **you** point it at, as part of
-the operations you request. The full statement is in [PRIVACY.md](https://github.com/GavinLucas/docker-mcp/blob/main/PRIVACY.md).
+the operations you request. The full statement is in [PRIVACY.md](https://github.com/L337-org/docker-mcp/blob/main/PRIVACY.md).
 
 ## Contributing
 
-Contributions are welcome. The project values a tight mapping between the Docker SDK's public surface and the MCP tools we expose. See [CONTRIBUTING.md](https://github.com/GavinLucas/docker-mcp/blob/main/CONTRIBUTING.md) for the project layout, tool conventions, the checklist for adding a new tool module, and local development setup.
+Contributions are welcome. The project values a tight mapping between the Docker SDK's public surface and the MCP tools we expose. See [CONTRIBUTING.md](https://github.com/L337-org/docker-mcp/blob/main/CONTRIBUTING.md) for the project layout, tool conventions, the checklist for adding a new tool module, and local development setup.

{docker_mcp_server-2.1.0 → docker_mcp_server-2.1.2}/PRIVACY.md

@@ -24,4 +24,4 @@ results surfaced to the model. This policy covers only the behaviour of docker-m
 ## Contact
 
 Questions about this policy: open an issue at
-<https://github.com/GavinLucas/docker-mcp/issues>.
+<https://github.com/L337-org/docker-mcp/issues>.

{docker_mcp_server-2.1.0 → docker_mcp_server-2.1.2}/README.md

@@ -1,10 +1,10 @@
-<img src="https://raw.githubusercontent.com/GavinLucas/docker-mcp/main/assets/icon.png" align="left" width="72" height="72" alt="">
+<img src="https://raw.githubusercontent.com/L337-org/docker-mcp/main/assets/icon.png" align="left" width="72" height="72" alt="">
 
 # docker-mcp-server
 
 [![docker-mcp MCP server](https://glama.ai/mcp/servers/GavinLucas/docker-mcp/badges/score.svg)](https://glama.ai/mcp/servers/GavinLucas/docker-mcp)
 
-<!-- mcp-name: io.github.GavinLucas/docker-mcp-server -->
+<!-- mcp-name: io.github.L337-org/docker-mcp-server -->
 
 More than just a fully featured [MCP](https://modelcontextprotocol.io) server that lets AI agents manage Docker — containers, images, networks, volumes, swarm services, secrets, configs, nodes, plugins, etc., it helps you create workflows to easily manage your Docker environments.
 
@@ -51,7 +51,7 @@ To pin a specific version, append `==<version>` to the package name (e.g. `docke
       "command": "uvx",
       "args": [
         "--from",
-        "git+https://github.com/GavinLucas/docker-mcp.git",
+        "git+https://github.com/L337-org/docker-mcp.git",
         "docker-mcp-server"
       ],
       "env": {}
@@ -65,7 +65,7 @@ To pin a specific revision, append `@<tag-or-commit>` to the git URL.
 ### Install as a Desktop Extension (.mcpb)
 
 For [Claude Desktop](https://claude.com/download), a one-click bundle is attached to each
-[GitHub Release](https://github.com/GavinLucas/docker-mcp/releases) as
+[GitHub Release](https://github.com/L337-org/docker-mcp/releases) as
 `docker-mcp-server-<version>.mcpb` (with a matching `.sha256`). Download it and drag it into
 **Settings → Extensions**, or use **Settings → Extensions → Advanced settings → Install extension…**
 and pick the file. The install dialog surfaces a **Docker host(s)** field and the read-only /
@@ -82,7 +82,7 @@ Docker context; set one endpoint (`ssh://user@host`) for a remote daemon, or lis
 Running the server as a container removes the Python / uv / git prerequisites entirely — the only
 thing the host needs is Docker, which you already have. Prebuilt multi-arch images (linux/amd64 +
 linux/arm64) are published on each release to **Docker Hub** (`gavinlucas/docker-mcp-server`) and
-**GHCR** (`ghcr.io/gavinlucas/docker-mcp-server`) — the two are identical. Point your MCP client at
+**GHCR** (`ghcr.io/l337-org/docker-mcp-server`) — the two are identical. Point your MCP client at
 `docker run`:
 
 ```json
@@ -103,14 +103,14 @@ linux/arm64) are published on each release to **Docker Hub** (`gavinlucas/docker
 
 `-i` is required (the server speaks MCP over stdio); `--rm` cleans up when the client disconnects. To
 pin a version, replace `:latest` with a release tag (e.g. `:1.5.1`). To pull from GHCR instead, use
-`ghcr.io/gavinlucas/docker-mcp-server:latest`.
+`ghcr.io/l337-org/docker-mcp-server:latest`.
 
-> **Image renamed.** As of 1.5.0 the image is published to `ghcr.io/gavinlucas/docker-mcp-server`
-> (matching the PyPI name). The old `ghcr.io/gavinlucas/docker-mcp` image is frozen at 1.4.0 and no
-> longer updated — point new pulls at `…/docker-mcp-server`.
+> **Image renamed.** As of 1.5.0 the image is published as `docker-mcp-server` (matching the PyPI
+> name). The old `ghcr.io/gavinlucas/docker-mcp` image is frozen at 1.4.0 and no longer updated —
+> point new pulls at `ghcr.io/l337-org/docker-mcp-server`.
 
 **Image variants.** Two variants are published to both registries (`gavinlucas/docker-mcp-server` on
-Docker Hub and `ghcr.io/gavinlucas/docker-mcp-server` on GHCR), both built from one `Dockerfile`. The
+Docker Hub and `ghcr.io/l337-org/docker-mcp-server` on GHCR), both built from one `Dockerfile`. The
 CLI-backed domains (Compose, Stack, Buildx, Scout, Context) shell out to the `docker` CLI and its
 plugins.
 
@@ -333,7 +333,7 @@ All of these go in the `env` block of the server entry in your MCP client config
       "command": "uvx",
       "args": [
         "--from",
-        "git+https://github.com/GavinLucas/docker-mcp.git",
+        "git+https://github.com/L337-org/docker-mcp.git",
         "docker-mcp-server"
       ],
       "env": {
@@ -351,7 +351,7 @@ Swap `DOCKER_MCP_SERVER_READONLY` for `DOCKER_MCP_SERVER_NO_DESTRUCTIVE` to allo
 ```bash
 claude mcp add docker-mcp-server-readonly \
   --env DOCKER_MCP_SERVER_READONLY=1 \
-  -- uvx --from git+https://github.com/GavinLucas/docker-mcp.git docker-mcp-server
+  -- uvx --from git+https://github.com/L337-org/docker-mcp.git docker-mcp-server
 ```
 
 ## Security considerations
@@ -379,10 +379,10 @@ Connecting this server to an AI agent grants it the same level of access as a lo
 | Channel | Link |
 |---------|------|
 | PyPI | [docker-mcp-server](https://pypi.org/project/docker-mcp-server/) |
-| GHCR (container) | [ghcr.io/gavinlucas/docker-mcp-server](https://github.com/GavinLucas/docker-mcp/pkgs/container/docker-mcp-server) |
+| GHCR (container) | [ghcr.io/l337-org/docker-mcp-server](https://github.com/L337-org/docker-mcp/pkgs/container/docker-mcp-server) |
 | Docker Hub (container) | [gavinlucas/docker-mcp-server](https://hub.docker.com/r/gavinlucas/docker-mcp-server) |
-| Desktop Extension (.mcpb) | [GitHub Releases](https://github.com/GavinLucas/docker-mcp/releases) |
-| Official MCP Registry | [io.github.GavinLucas/docker-mcp-server](https://registry.modelcontextprotocol.io/v0.1/servers/io.github.GavinLucas%2Fdocker-mcp-server/versions) |
+| Desktop Extension (.mcpb) | [GitHub Releases](https://github.com/L337-org/docker-mcp/releases) |
+| Official MCP Registry | [io.github.L337-org/docker-mcp-server](https://registry.modelcontextprotocol.io/v0.1/servers/io.github.L337-org%2Fdocker-mcp-server/versions) |
 | Glama | [docker-mcp-server](https://glama.ai/mcp/servers/GavinLucas/docker-mcp) |
 | mcp.so | [docker-mcp-server](https://mcp.so/server/docker-mcp-server/GavinLucas) |
 | awesome-mcp-servers | [punkpeye/awesome-mcp-servers](https://github.com/punkpeye/awesome-mcp-servers#cloud-platforms) |
@@ -391,8 +391,8 @@ Connecting this server to an AI agent grants it the same level of access as a lo
 
 docker-mcp-server collects no data, sends no telemetry, and has no author-operated backend. It runs
 locally and talks only to the Docker daemon and container registries **you** point it at, as part of
-the operations you request. The full statement is in [PRIVACY.md](https://github.com/GavinLucas/docker-mcp/blob/main/PRIVACY.md).
+the operations you request. The full statement is in [PRIVACY.md](https://github.com/L337-org/docker-mcp/blob/main/PRIVACY.md).
 
 ## Contributing
 
-Contributions are welcome. The project values a tight mapping between the Docker SDK's public surface and the MCP tools we expose. See [CONTRIBUTING.md](https://github.com/GavinLucas/docker-mcp/blob/main/CONTRIBUTING.md) for the project layout, tool conventions, the checklist for adding a new tool module, and local development setup.
+Contributions are welcome. The project values a tight mapping between the Docker SDK's public surface and the MCP tools we expose. See [CONTRIBUTING.md](https://github.com/L337-org/docker-mcp/blob/main/CONTRIBUTING.md) for the project layout, tool conventions, the checklist for adding a new tool module, and local development setup.

{docker_mcp_server-2.1.0 → docker_mcp_server-2.1.2}/SECURITY.md

@@ -4,7 +4,7 @@
 
 If you believe you have found a security issue in `docker-mcp`, please open a
 private vulnerability report via GitHub's
-[security advisory flow](https://github.com/GavinLucas/docker-mcp/security/advisories/new)
+[security advisory flow](https://github.com/L337-org/docker-mcp/security/advisories/new)
 rather than filing a public issue. That keeps the discussion private until a
 fix is available.