| FMRS | 29 / 100 · D | 79 / 100 · B |
|---|
| Reliability | 5 / 20 | 12 / 20 |
|---|
| Security and permissions | 5 / 20 | 16 / 20 |
|---|
| Maintenance | 6 / 20 | 18 / 20 |
|---|
| Documentation | 6 / 20 | 18 / 20 |
|---|
| Setup experience | 7 / 20 | 15 / 20 |
|---|
| Best for | - Users of AI coding tools (Claude, Cursor, etc.) who want to reduce token usage.
- Agents that need reliable, unambiguous Docker output for automated decision-making.
- Developers using Docker as part of their infrastructure and wanting MCP integration in their workflow.
| - Developers auditing NPM dependencies within AI workflows
- Teams performing supply chain security assessments
- Users of Claude Desktop, Cursor, or VS Code
|
|---|
| Not for | - Users requiring interactive terminal control or full Docker CLI features (like attach, exec -it).
- Users unfamiliar with MCP configuration or Node.js environments.
- Users needing raw output from the Docker daemon, not structured data.
| - Projects outside the NPM ecosystem (e.g., pure Python/Go)
- Environments without network access to deps.dev, OSV.dev, and the npm registry
- Scenarios requiring maintenance by an official upstream vendor
|
|---|
| Required permissions | - Permissions to execute Docker commands, such as access to Docker socket or daemon (depending on environment).
- Network access for npx to download npm packages or Docker images (if pulling during builds).
- Filesystem access to read Dockerfiles or build contexts (if applicable).
| - Network access to the NPM registry and external services (deps.dev, OSV.dev, OpenSSF, npms.io, GitHub)
- Read access to workspace lockfiles (pnpm-lock.yaml, package-lock., yarn.lock) for cache invalidation
|
|---|
| Risks and side effects | - Running Docker commands may affect containers, images, or builds, e.g., removing containers or modifying images.
- Misconfiguration or network issues can cause Docker commands to fail, and agents may receive incomplete structured data.
- Using npx may introduce supply-chain risks, as remote code is downloaded and executed on each invocation.
| - Third-party READMEs and changelogs are untrusted external content; they are wrapped in tags with _meta flags but should still be handled cautiously
- Depends on availability and accuracy of external services
- Batch requests are capped at 25 packages to prevent registry enumeration; larger sets require batching
- Third-party open source project, not officially maintained by NPM or Anthropic
|
|---|
| Supported clients | Claude Desktop, Claude Code, Cursor, VS Code, Windsurf, Cline, Roo Code, Codex, Gemini CLI, Zed, Continue | Claude Desktop, VS Code, Cursor |
|---|
| Tools | 5 | 19 |
|---|