# io.github.CloudCorpRecords/containerport (oci · ghcr.io/cloudcorprecords/containerport)

Run core Docker container operations: list, run, inspect, logs, images and volumes.

- Trust score: 40/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `@reneturcios/containerport`: 65/100, [markdown](https://verifymcp.io/servers/cloudcorprecords-containerport/reneturcios-containerport.md), [page](https://verifymcp.io/servers/cloudcorprecords-containerport/reneturcios-containerport)
- oci · `ghcr.io/cloudcorprecords/containerport`: 40/100 (this document), [markdown](https://verifymcp.io/servers/cloudcorprecords-containerport/ghcr-io-cloudcorprecords-containerport.md), [page](https://verifymcp.io/servers/cloudcorprecords-containerport/ghcr-io-cloudcorprecords-containerport)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/cloudcorprecords/containerport`
- Version: `0.1.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 0/100
  - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  - Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 3 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 72/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 440 tokens (~44/item across 10 items; 10 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 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.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the io.github.CloudCorpRecords/containerport MCP server?

io.github.CloudCorpRecords/containerport runs locally as a container image, launched with docker run --rm -i ghcr.io/cloudcorprecords/containerport:0.1.0. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add cloudcorprecords-containerport -- docker run --rm -i ghcr.io/cloudcorprecords/containerport:0.1.0
```

### Cursor

```json
{
  "mcpServers": {
    "cloudcorprecords-containerport": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/containerport:0.1.0"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "cloudcorprecords-containerport": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/containerport:0.1.0"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add cloudcorprecords-containerport -- docker run --rm -i ghcr.io/cloudcorprecords/containerport:0.1.0
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cloudcorprecords-containerport": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/containerport:0.1.0"
      ],
      "enabled": true
    }
  }
}
```

### Hermes

```yaml
mcp_servers:
  cloudcorprecords-containerport:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/cloudcorprecords/containerport:0.1.0"]
```

### Netclaw

```json
{
  "McpServers": {
    "cloudcorprecords-containerport": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/containerport:0.1.0"
      ]
    }
  }
}
```

### Other

```json
{
  "mcpServers": {
    "cloudcorprecords-containerport": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/containerport:0.1.0"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 40, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 39, +1)

No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 38)

First indexed and scored.

## MCP tools (10)

### `list_containers` (~36 tokens)

List Docker containers, optionally including stopped ones.

Input parameters:

- `all` (boolean): When true, include stopped containers as well as running ones.

### `inspect_container` (~34 tokens)

Return the full inspect document for one Docker container.

Input parameters:

- `container_id` (string, required): ID or name of the container to inspect.

### `run_container` (~132 tokens)

Run a new Docker container in detached mode from an image.

Input parameters:

- `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, required): 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.

### `start_container` (~31 tokens)

Start a stopped Docker container.

Input parameters:

- `container_id` (string, required): ID or name of the stopped container to start.

### `stop_container` (~31 tokens)

Stop a running Docker container.

Input parameters:

- `container_id` (string, required): ID or name of the running container to stop.

### `remove_container` (~51 tokens)

Remove a Docker container, optionally forcing removal.

Input parameters:

- `container_id` (string, required): ID or name of the container to remove.
- `force` (boolean): When true, force removal even if the container is running.

### `list_images` (~16 tokens)

List Docker images present on the host.

### `pull_image` (~38 tokens)

Pull a Docker image from its registry.

Input parameters:

- `image` (string, required): Image to pull from its registry, such as a name with an optional tag.

### `get_container_logs` (~55 tokens)

Fetch recent log output from a Docker container.

Input parameters:

- `container_id` (string, required): ID or name of the container to fetch logs from.
- `tail` (number): Number of lines to return from the end of the log output.

### `list_volumes` (~16 tokens)

List Docker volumes on the host.

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/cloudcorprecords-containerport/ghcr-io-cloudcorprecords-containerport#diagnostics

## Score history

- 2026-11-05: 40
- 2026-11-04: 40
- 2026-11-03: 39
- 2026-11-02: 39
- 2026-11-01: 38

## Common questions

### 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 container image (ghcr.io/cloudcorprecords/containerport).

### Is the io.github.CloudCorpRecords/containerport MCP server safe to use?

io.github.CloudCorpRecords/containerport scores 40 out of 100 on VerifyMCP. 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.

## Links

- GitHub Container Registry: https://ghcr.io/cloudcorprecords/containerport
- Repository: https://github.com/CloudCorpRecords/containerport
- Changelog RSS feed: https://verifymcp.io/servers/cloudcorprecords-containerport/ghcr-io-cloudcorprecords-containerport.xml
- Changelog JSON feed: https://verifymcp.io/servers/cloudcorprecords-containerport/ghcr-io-cloudcorprecords-containerport.json
- HTML version of this page: https://verifymcp.io/servers/cloudcorprecords-containerport/ghcr-io-cloudcorprecords-containerport