io.github.rog0x/docker
NPM · @ROG0X/MCP-DOCKER-TOOLS
Docker container management and Dockerfile analysis
Available components
Last scanned (21 hours ago)
Scores higher than 87% of npm servers
Category Cloud Infrastructure
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
- A known CVE affects @rog0x/mcp-docker-tools, but no fixed version has been published, so there is nothing to upgrade to. View diagnostics → Partial
- No install/post-install scripts declared.Pass
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 226 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 481 tokens (~96/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
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.
- 3 Nov 26 0
- Stability: 0.97 → pass security
- 2 Nov 26 0
- Stability: pass → 0.97 functional
- 31 Oct 26 0
- CVE-2026-106765 affects this package ▼ security
- Known CVEs: pass → partial ▼ security
- 27 Oct 26 0
- Stability: 0.97 → pass security
- 26 Oct 26 0
- Stability: pass → 0.97 functional
- 20 Oct 26 0
- Stability: 0.97 → pass security
- 19 Oct 26 0
- Stability: pass → 0.97 functional
- 17 Oct 26 +2
- Stability: 0.87 → pass security
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 4 Nov 2026 · Analysed npm/@rog0x/mcp-docker-tools@1.0.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-fq6x-j3g6-xx83 | CVE-2026-106765 | high | CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H | no |
Background: What a vulnerability scan can and cannot prove →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
docker_compose_analyze ~50
Analyze docker-compose.yml: list services, ports, volumes, networks, health checks, dependencies. Suggest improvements.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The full content of the docker-compose.yml to analyze. |
No output schema declared.
No examples provided.
docker_container_list ~89
List Docker containers with status, ports, image, created time, and resource usage. Can show only running containers or all containers including stopped ones.
| Name | Type | Req | Description |
|---|---|---|---|
| all | boolean | – | If true, show all containers including stopped ones. Defaults to false (running only). |
| format | string | – | Output format: 'table' for readable text, 'json' for structured data. Defaults to 'json'. |
No output schema declared.
No examples provided.
docker_container_logs ~164
Get logs from a Docker container. Supports retrieving the last N lines, filtering by keyword, and including timestamps.
| Name | Type | Req | Description |
|---|---|---|---|
| container | string | yes | Container name or ID to get logs from. |
| filter | string | – | Filter log lines to only include those containing this keyword (case-insensitive). |
| since | string | – | Show logs since a timestamp (e.g., '2024-01-01T00:00:00') or relative duration (e.g., '1h', '30m'). |
| tail | number | – | Number of lines to retrieve from the end of logs. Defaults to 100. |
| timestamps | boolean | – | Include timestamps in log output. Defaults to true. |
| until | string | – | Show logs until a timestamp or relative duration. |
No output schema declared.
No examples provided.
docker_dockerfile_analyze ~84
Analyze a Dockerfile for best practices including multi-stage builds, non-root user, .dockerignore usage, layer caching order, image size optimization, and security.
| Name | Type | Req | Description |
|---|---|---|---|
| checkDockerignore | boolean | – | If true, also checks for common .dockerignore recommendations. Defaults to true. |
| content | string | yes | The full content of the Dockerfile to analyze. |
No output schema declared.
No examples provided.
docker_image_list ~94
List Docker images with size, tags, created date, and layer count. Optionally filter by repository name.
| Name | Type | Req | Description |
|---|---|---|---|
| filter | string | – | Filter images by repository name (partial match). Leave empty to list all. |
| format | string | – | Output format: 'table' or 'json'. Defaults to 'json'. |
| showDangling | boolean | – | Include dangling (untagged) images. Defaults to false. |
No output schema declared.
No examples provided.
How do I install the io.github.rog0x/docker MCP server?
io.github.rog0x/docker runs locally as an npm package, launched with npx -y @rog0x/mcp-docker-tools. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @rog0x/mcp-docker-tools
claude mcp add rog0x-docker -- npx -y @rog0x/mcp-docker-tools
What is the io.github.rog0x/docker MCP server?
io.github.rog0x/docker is an MCP server listed in the public MCP registry as io.github.rog0x/docker. Docker container management and Dockerfile analysis. This page covers its npm package (@rog0x/mcp-docker-tools).
Is the io.github.rog0x/docker MCP server safe to use?
io.github.rog0x/docker scores 85 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 4 November 2026. It declares no install or post-install scripts. 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.rog0x/docker MCP server expose?
io.github.rog0x/docker exposes 5 tools: docker_container_list, docker_image_list, docker_dockerfile_analyze, docker_compose_analyze, docker_container_logs. Their descriptions and schemas cost roughly 481 tokens of context every time the server is loaded.
Is the io.github.rog0x/docker MCP server still maintained?
io.github.rog0x/docker is still listed as active in the MCP registry. We last reached this channel on 4 November 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.rog0x/docker MCP server under?
io.github.rog0x/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.