io.github.CloudCorpRecords/containerport
NPM · @RENETURCIOS/CONTAINERPORT · 2 COMPONENTS
Run core Docker container operations: list, run, inspect, logs, images and volumes.
Available components
Last scanned (10 hours ago)
Scores higher than 32% 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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 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 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability72
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 440 tokens (~44/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 Management13
- Stability observed for 4 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 1 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
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 63
First indexed and scored.
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 5 Nov 2026 · Analysed npm/@reneturcios/containerport@0.1.0
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-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| 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 →
get_container_logs ~55
Fetch recent log output from a Docker container.
| Name | Type | Req | Description |
|---|---|---|---|
| container_id | string | yes | ID or name of the container to fetch logs from. |
| tail | number | – | Number of lines to return from the end of the log output. |
No output schema declared.
No examples provided.
inspect_container ~34
Return the full inspect document for one Docker container.
| Name | Type | Req | Description |
|---|---|---|---|
| container_id | string | yes | ID or name of the container to inspect. |
No output schema declared.
No examples provided.
list_containers ~36
List Docker containers, optionally including stopped ones.
| Name | Type | Req | Description |
|---|---|---|---|
| all | boolean | – | When true, include stopped containers as well as running ones. |
No output schema declared.
No examples provided.
list_images ~16
List Docker images present on the host.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_volumes ~16
List Docker volumes on the host.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
pull_image ~38
Pull a Docker image from its registry.
| Name | Type | Req | Description |
|---|---|---|---|
| image | string | yes | Image to pull from its registry, such as a name with an optional tag. |
No output schema declared.
No examples provided.
remove_container ~51
Remove a Docker container, optionally forcing removal.
| Name | Type | Req | Description |
|---|---|---|---|
| container_id | string | yes | ID or name of the container to remove. |
| force | boolean | – | When true, force removal even if the container is running. |
No output schema declared.
No examples provided.
run_container ~132
Run a new Docker container in detached mode from an image.
| Name | Type | Req | Description |
|---|---|---|---|
| command | string | – | Command to run inside the container, executed via the container's sh -c. |
| env | array | – | Environment variables to set in the container, each in KEY=VALUE form, passed to docker run -e. |
| image | string | yes | Image to run the new container from, such as a name with an optional tag. |
| name | string | – | Name to assign to the new container. |
| ports | array | – | Port mappings to publish, each in host:container form, passed to docker run -p. |
No output schema declared.
No examples provided.
start_container ~31
Start a stopped Docker container.
| Name | Type | Req | Description |
|---|---|---|---|
| container_id | string | yes | ID or name of the stopped container to start. |
No output schema declared.
No examples provided.
stop_container ~31
Stop a running Docker container.
| Name | Type | Req | Description |
|---|---|---|---|
| container_id | string | yes | ID or name of the running container to stop. |
No output schema declared.
No examples provided.
How do I install the io.github.CloudCorpRecords/containerport MCP server?
io.github.CloudCorpRecords/containerport runs locally as an npm package, launched with npx -y @reneturcios/containerport. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @reneturcios/containerport
claude mcp add cloudcorprecords-containerport -- npx -y @reneturcios/containerport
What is the io.github.CloudCorpRecords/containerport MCP server?
io.github.CloudCorpRecords/containerport is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/containerport. Run core Docker container operations: list, run, inspect, logs, images and volumes. This page covers its npm package (@reneturcios/containerport).
Is the io.github.CloudCorpRecords/containerport MCP server safe to use?
io.github.CloudCorpRecords/containerport scores 65 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 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.CloudCorpRecords/containerport MCP server expose?
io.github.CloudCorpRecords/containerport exposes 10 tools: list_containers, inspect_container, run_container, start_container, stop_container, and 5 more. Their descriptions and schemas cost roughly 440 tokens of context every time the server is loaded.
Is the io.github.CloudCorpRecords/containerport MCP server still maintained?
io.github.CloudCorpRecords/containerport is still listed as active in the MCP registry. We last reached this channel on 5 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.CloudCorpRecords/containerport MCP server under?
io.github.CloudCorpRecords/containerport declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.