Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.Dave-London/docker

NPM · @PARETOOLS/DOCKER · SCANNED SEP 20

Structured Docker operations (ps, images, logs, build) as typed JSON.

Available components

0 this week 92 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to Dave-London/Pare). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 31 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability75
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1485 tokens (~114/item across 13 items; 13 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
  • Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "exec" implies "exec" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the io.github.Dave-London/docker MCP server?

io.github.Dave-London/docker runs locally as an npm package, launched with npx -y @paretools/docker. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @paretools/docker

# add to Claude Code
claude mcp add dave-london-docker -- npx -y @paretools/docker
// .cursor/mcp.json
{
  "mcpServers": {
    "dave-london-docker": {
      "command": "npx",
      "args": [
        "-y",
        "@paretools/docker"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "dave-london-docker": {
      "command": "npx",
      "args": [
        "-y",
        "@paretools/docker"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add dave-london-docker -- npx -y @paretools/docker
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dave-london-docker": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@paretools/docker"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add dave-london-docker --command npx --arg -y --arg @paretools/docker
# ~/.hermes/config.yaml
mcp_servers:
  dave-london-docker:
    command: "npx"
    args: ["-y", "@paretools/docker"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "dave-london-docker": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@paretools/docker"
      ]
    }
  }
}
# add to Vellum
assistant mcp add dave-london-docker -t stdio -c npx -a -y @paretools/docker
// mcp.json
{
  "mcpServers": {
    "dave-london-docker": {
      "command": "npx",
      "args": [
        "-y",
        "@paretools/docker"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 18 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Sept 26 −2
    • Stability: pass → 0.80 functional
  • 15 Sept 26 0
    • Stability: 0.97 → pass security
  • 14 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Sept 26 −2
    • Stability: pass → 0.80 functional
  • 8 Sept 26 0
    • Stability: 0.97 → pass security
  • 7 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Analysed npm/@paretools/docker@0.8.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo Dave-London/Pare
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/Dave-London/Pare/.github/workflows/release.yml@refs/heads/main
Rekor log index 949168475
Predicate type https://slsa.dev/provenance/v1
Subject digest sha512:2e1efa4e0a07a66bb1ae0d62375ed5e4b7d0e18e20819596d2d39d9661936eeef75a1d7f493e8141af89cdf940c0466700d646fc2b938e8df89b80fce

Background: How many MCP packages publish verified provenance →

Dependencies 96 packages
Packages resolved 96
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 13 exposed · ~1,436 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
build ~118

Builds a Docker image and returns structured build results including image ID, duration, and errors. Use instead of running `docker build` in the terminal.

NameTypeReqDescription
argsarrayAdditional build arguments
compactbooleanAuto-compact when structured output exceeds raw CLI tokens. Set false to always get full schema.
filestringDockerfile path (default: Dockerfile)
pathstringBuild context path (default: cwd)
tagstringImage tag (e.g., myapp:latest)
NameTypeReqDescription
durationnumberyes
errorsarrayyes
imageIdstring
stepsnumber
successbooleanyes

No examples provided.

compose-down ~114

Stops Docker Compose services and returns structured status. Use instead of running `docker compose down` in the terminal.

NameTypeReqDescription
compactbooleanAuto-compact when structured output exceeds raw CLI tokens. Set false to always get full schema.
filestringCompose file path (default: docker-compose.yml)
pathstringyesDirectory containing docker-compose.yml
removeOrphansbooleanRemove orphan containers (default: false)
volumesbooleanAlso remove named volumes (default: false)
NameTypeReqDescription
removednumberyes
stoppednumberyes
successbooleanyes

No examples provided.

compose-ps ~74

Lists Docker Compose services with structured state and status information. Use instead of running `docker compose ps` in the terminal.

NameTypeReqDescription
compactbooleanAuto-compact when structured output exceeds raw CLI tokens. Set false to always get full schema.
pathstringDirectory containing docker-compose.yml (default: cwd)
NameTypeReqDescription
servicesarrayyes
totalnumberyes

No examples provided.

compose-up ~127

Starts Docker Compose services and returns structured status. Use instead of running `docker compose up` in the terminal.

NameTypeReqDescription
buildbooleanBuild images before starting (default: false)
compactbooleanAuto-compact when structured output exceeds raw CLI tokens. Set false to always get full schema.
detachbooleanRun in background (default: true)
filestringCompose file path (default: docker-compose.yml)
pathstringyesDirectory containing docker-compose.yml
servicesarraySpecific services to start (default: all)
NameTypeReqDescription
servicesarrayyes
startednumberyes
successbooleanyes

No examples provided.

exec ~147

Executes arbitrary commands inside a running Docker container and returns structured output. Use instead of running `docker exec` in the terminal. WARNING: This runs arbitrary commands inside the container. Only use on trusted containers.

NameTypeReqDescription
commandarrayyesCommand to execute (e.g., ["ls", "-la"])
compactbooleanAuto-compact when structured output exceeds raw CLI tokens. Set false to always get full schema.
containerstringyesContainer name or ID
envarrayEnvironment variables (e.g., ["KEY=VALUE"])
pathstringHost working directory (default: cwd)
workdirstringWorking directory inside the container
NameTypeReqDescription
exitCodenumberyes
stderrstringyes
stdoutstringyes
successbooleanyes

No examples provided.

images ~94

Lists Docker images with structured repository, tag, size, and creation info. Use instead of running `docker images` in the terminal.

NameTypeReqDescription
allbooleanShow all images including intermediates
compactbooleanAuto-compact when structured output exceeds raw CLI tokens. Set false to always get full schema.
filterstringFilter by reference (e.g., 'myapp', 'nginx:*')
NameTypeReqDescription
imagesarrayyes
totalnumberyes

No examples provided.

inspect ~88

Shows detailed container or image information with structured state, image, and platform data. Use instead of running `docker inspect` in the terminal.

NameTypeReqDescription
compactbooleanAuto-compact when structured output exceeds raw CLI tokens. Set false to always get full schema.
pathstringWorking directory (default: cwd)
targetstringyesContainer or image name/ID to inspect
NameTypeReqDescription
createdstringyes
idstringyes
imagestringyes
namestringyes
platformstring
stateobjectyes

No examples provided.

logs ~134

Retrieves container logs as structured line arrays. Use instead of running `docker logs` in the terminal.

NameTypeReqDescription
compactbooleanAuto-compact when structured output exceeds raw CLI tokens. Set false to always get full schema.
containerstringyesContainer name or ID
limitnumberMax lines in structured output (default: 100). Lines beyond this are truncated with isTruncated flag.
sincestringShow logs since timestamp (e.g., '10m', '2024-01-01')
tailnumberNumber of lines to return (default: 100)
NameTypeReqDescription
containerstringyes
isTruncatedboolean
linesarrayyes
totalnumberyes
totalLinesnumber

No examples provided.

network-ls ~70

Lists Docker networks with structured driver and scope information. Use instead of running `docker network ls` in the terminal.

NameTypeReqDescription
compactbooleanAuto-compact when structured output exceeds raw CLI tokens. Set false to always get full schema.
pathstringWorking directory (default: cwd)
NameTypeReqDescription
networksarrayyes
totalnumberyes

No examples provided.

ps ~74

Lists Docker containers with structured status, ports, and state information. Use instead of running `docker ps` in the terminal.

NameTypeReqDescription
allbooleanShow all containers (default: true, includes stopped)
compactbooleanAuto-compact when structured output exceeds raw CLI tokens. Set false to always get full schema.
NameTypeReqDescription
containersarrayyes
runningnumberyes
stoppednumberyes
totalnumberyes

No examples provided.

pull ~120

Pulls a Docker image from a registry and returns structured result with digest info. Use instead of running `docker pull` in the terminal.

NameTypeReqDescription
compactbooleanAuto-compact when structured output exceeds raw CLI tokens. Set false to always get full schema.
imagestringyesImage to pull (e.g., nginx:latest, ubuntu:22.04)
pathstringWorking directory (default: cwd)
platformstringTarget platform (e.g., "linux/amd64", "linux/arm64")
NameTypeReqDescription
digeststring
imagestringyes
successbooleanyes
tagstringyes

No examples provided.

run ~202

Runs a Docker container from an image and returns structured container ID and status. Use instead of running `docker run` in the terminal.

NameTypeReqDescription
commandarrayCommand to run in the container
compactbooleanAuto-compact when structured output exceeds raw CLI tokens. Set false to always get full schema.
detachbooleanRun container in background (default: true)
envarrayEnvironment variables (e.g., ["KEY=VALUE"])
imagestringyesDocker image to run (e.g., nginx:latest)
namestringContainer name
pathstringWorking directory (default: cwd)
portsarrayPort mappings (e.g., ["8080:80", "443:443"])
rmbooleanRemove container after exit (default: false)
volumesarrayVolume mounts (e.g., ["/host/path:/container/path"])
NameTypeReqDescription
containerIdstringyes
detachedbooleanyes
imagestringyes
namestring

No examples provided.

volume-ls ~74

Lists Docker volumes with structured driver, mountpoint, and scope information. Use instead of running `docker volume ls` in the terminal.

NameTypeReqDescription
compactbooleanAuto-compact when structured output exceeds raw CLI tokens. Set false to always get full schema.
pathstringWorking directory (default: cwd)
NameTypeReqDescription
totalnumberyes
volumesarrayyes

No examples provided.

Common questions

What is the io.github.Dave-London/docker MCP server?

io.github.Dave-London/docker is an MCP server listed in the public MCP registry as io.github.Dave-London/docker. Structured Docker operations (ps, images, logs, build) as typed JSON. This page covers its npm package (@paretools/docker).

Is the io.github.Dave-London/docker MCP server safe to use?

io.github.Dave-London/docker scores 92 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.Dave-London/docker MCP server expose?

io.github.Dave-London/docker exposes 13 tools: ps, build, logs, images, run, and 8 more. Their descriptions and schemas cost roughly 1,436 tokens of context every time the server is loaded.

Is the io.github.Dave-London/docker MCP server still maintained?

io.github.Dave-London/docker is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.Dave-London/docker MCP server under?

io.github.Dave-London/docker declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.