Verfy

MCP servers / mcp-server-docker

MCP tool changes

mcp-server-docker

1 of its last 1 updates changed what the agent reads: 0 tool descriptions rewritten, up to 0.3.0.

PyPI package · last recorded on 13 November 2026 on a clean machine with placeholder settings; only tools/list was sent. A changed description is not a vulnerability. PyPI page · Method and limits · this data as JSON.

Release by release

0.2.1 → 0.3.0

minor release, 7 August 2026

build_image: input schema changed

create_container: input schema changed

create_network: input schema changed

create_volume: input schema changed

fetch_container_logs: input schema changed

list_containers: input schema changed

list_images: input schema changed

list_networks: input schema changed

list_volumes: input schema changed

prompt:docker_compose: input schema changed

pull_image: input schema changed

push_image: input schema changed

recreate_container: input schema changed

remove_container: input schema changed

remove_image: input schema changed

remove_network: input schema changed

remove_volume: input schema changed

run_container: input schema changed

start_container: input schema changed

stop_container: input schema changed

Releases tried: 0.1.0 (2025-04-05), did not start; 0.2.0 (2025-05-11), did not start; 0.2.1 (2025-06-05); 0.3.0 (2026-08-07).

Tools in 0.3.0

The pin is the SHA-256 of the tool's name, description and input schema, as verfy.lock records it. The same pin in your lock means your agent reads this exact definition. Verfy 0.16.0 and later also pin a tool's title, annotations and output schema when the server sends them, so such a tool shows a different pin in your lock.

Tools in 0.3.0
ToolDescriptionPin
list_containersList all Docker containers6d601c73e858
create_containerCreate a new Docker container0a476b440182
run_containerRun an image in a new Docker container (preferred over `create_container` + `start_container`)d989746ac503
recreate_containerStop and remove a container, then run a new container. Fails if the container does not exist.c62238b3dbd7
start_containerStart a Docker containerb1010e27f289
fetch_container_logsFetch logs for a Docker containerac7522fa5ff6
stop_containerStop a Docker container3bc13aace157
remove_containerRemove a Docker container85c2e541e546
list_imagesList Docker imagesfed3c456704e
pull_imagePull a Docker image451df0e1656f
push_imagePush a Docker image8445f2c07034
build_imageBuild a Docker image from a Dockerfilebff02136e915
remove_imageRemove a Docker image14b08bf575b8
list_networksList Docker networks296f3287cbb2
create_networkCreate a Docker network49e24c153fb3
remove_networkRemove a Docker network85fe15b27d9c
list_volumesList Docker volumesc288955e7146
create_volumeCreate a Docker volume531cfcd50221
remove_volumeRemove a Docker volumeedbcc91760ce
prompt:docker_composeTreat the LLM like a Docker Compose manager9100424f7fa9

Lock these tools

Pin what mcp-server-docker serves you today, commit the lock, and a pull request fails when a tool changes, with the text before and after. Pin the package version in your MCP config as well.

$ pip install verfy
$ verfy lock check --update   # shows each tool, then writes verfy.lock
$ git add verfy.lock
# .github/workflows/verfy.yml, after actions/checkout
- uses: verfy-dev/verfy-action@v1

Maintain this server? Run the same check on your releases and add the Locked by Verfy badge to your README.