io.github.ofershap/docker
NPM · MCP-DOCKER-SERVER · SCANNED SEP 20
MCP server for Docker — manage containers, images, volumes, and compose services from your IDE
Available components
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 Security89
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects uuid 10.0.0, reached via dockerode > uuid. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 58 of 157 dependencies flagged as unhealthy (1 deprecated). 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 193 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability76
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 322 tokens (~32/item across 10 items; 10 tools + 0 resources), lean.Pass
- 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
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "remove_container" implies "remove" 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 10 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
How do I install the io.github.ofershap/docker MCP server?
io.github.ofershap/docker runs locally as an npm package, launched with npx -y mcp-docker-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · mcp-docker-server
claude mcp add ofershap-docker -- npx -y mcp-docker-server
{
"mcpServers": {
"ofershap-docker": {
"command": "npx",
"args": [
"-y",
"mcp-docker-server"
]
}
}
} {
"servers": {
"ofershap-docker": {
"command": "npx",
"args": [
"-y",
"mcp-docker-server"
]
}
}
} codex mcp add ofershap-docker -- npx -y mcp-docker-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ofershap-docker": {
"type": "local",
"command": [
"npx",
"-y",
"mcp-docker-server"
],
"enabled": true
}
}
} openclaw mcp add ofershap-docker --command npx --arg -y --arg mcp-docker-server
mcp_servers:
ofershap-docker:
command: "npx"
args: ["-y", "mcp-docker-server"] {
"McpServers": {
"ofershap-docker": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"mcp-docker-server"
]
}
}
} assistant mcp add ofershap-docker -t stdio -c npx -a -y mcp-docker-server
{
"mcpServers": {
"ofershap-docker": {
"command": "npx",
"args": [
"-y",
"mcp-docker-server"
]
}
}
} 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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −3
- Stability: pass → 0.80 functional
- 15 Sept 26 +1
- Stability: 0.97 → pass security
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 0
- Security disclosure: unverified → fail ▼ functional
- 11 Sept 26 0
- Security disclosure: fail → unverified ▼ functional
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
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/mcp-docker-server@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-w5hq-g745-h8pq | CVE-2026-41907 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 157 packages
| Packages resolved | 157 |
|---|---|
| Deprecated | 1 |
| Stale | 57 |
| 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 →
container_logs ~39
Get logs from a Docker container.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Container ID or name |
| tail | number | – | Number of lines from the end |
No output schema declared.
No examples provided.
container_stats ~33
Get CPU, memory, and network stats for a running Docker container.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Container ID or name |
No output schema declared.
No examples provided.
exec_command ~47
Execute a command inside a running Docker container.
| Name | Type | Req | Description |
|---|---|---|---|
| command | array | yes | Command and arguments, e.g. ['ls', '-la'] |
| id | string | yes | Container ID or name |
No output schema declared.
No examples provided.
list_containers ~31
List Docker containers. Set all=true to include stopped containers.
| Name | Type | Req | Description |
|---|---|---|---|
| all | boolean | – | Include stopped containers |
No output schema declared.
No examples provided.
list_images ~15
List Docker images on the host.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
remove_container ~43
Remove a Docker container. Use force=true to remove running containers.
| Name | Type | Req | Description |
|---|---|---|---|
| force | boolean | – | Force remove running container |
| id | string | yes | Container ID or name |
No output schema declared.
No examples provided.
remove_image ~40
Remove a Docker image. Use force=true to force removal.
| Name | Type | Req | Description |
|---|---|---|---|
| force | boolean | – | Force remove |
| id | string | yes | Image ID or tag |
No output schema declared.
No examples provided.
restart_container ~24
Restart a Docker container.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Container ID or name |
No output schema declared.
No examples provided.
start_container ~25
Start a stopped Docker container.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Container ID or name |
No output schema declared.
No examples provided.
stop_container ~25
Stop a running Docker container.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Container ID or name |
No output schema declared.
No examples provided.
What is the io.github.ofershap/docker MCP server?
io.github.ofershap/docker is an MCP server listed in the public MCP registry as io.github.ofershap/docker. MCP server for Docker, manage containers, images, volumes, and compose services from your IDE. This page covers its npm package (mcp-docker-server).
Is the io.github.ofershap/docker MCP server safe to use?
io.github.ofershap/docker scores 79 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 20 September 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.ofershap/docker MCP server expose?
io.github.ofershap/docker exposes 10 tools: list_containers, container_logs, start_container, stop_container, restart_container, and 5 more. Their descriptions and schemas cost roughly 322 tokens of context every time the server is loaded.
Is the io.github.ofershap/docker MCP server still maintained?
io.github.ofershap/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.ofershap/docker MCP server under?
io.github.ofershap/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.