io.github.friendlygeorge/docker-mcp-server

MCPcommunity
v0.1.3io.github.friendlygeorgeUnknownUpdated 22d agonpmGitHub

MCP server for Docker — containers, health checks, Compose, logs for AI agents

The Docker MCP server designed for agents that need their containers to stay running. Without this: Your agent deploys a container, it crashes at 3am, and nobody notices until the user complains. Compose stacks drift. Health checks are manual. Logs are scattered across terminals. With this: Your agent checks health, watches for readiness, restarts crashed containers, and follows logs, all through…

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
22d agoLast update
Package
Authorio.github.friendlygeorge
LicenseUnknown
Version0.1.3
Sourcemcp-registry
npm@supernova123/docker-mcp-server
GitHubfriendlygeorge/docker-mcp-server
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/25
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/10
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
—npm provenance (Sigstore)+0/5
→ Publish from GitHub Actions with the --provenance flag
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies60 resolved · 1 with advisories
Tool surface31 tools · 3 privileged
Security scan✓ Cleanv0.2.5 · 20d ago
DEPuuid@10.0.0GHSA-w5hq-g745-h8pq (transitive)
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts — it cannot prove the absence of malicious code.

About

The Docker MCP server designed for agents that need their containers to stay running. Without this: Your agent deploys a container, it crashes at 3am, and nobody notices until the user complains. Compose stacks drift. Health checks are manual. Logs are scattered across terminals. With this: Your agent checks health, watches for readiness, restarts crashed containers, and follows logs, all through a single MCP interface. Containers stay running because your agent knows how to keep them running.…

Keywords
mcp