# Harbor (oci · ghcr.io/oreondev/harbor-mcp)

Read-only access to a Harbor registry: projects, artifacts, vulnerabilities, robots and replication.

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

## Components

- oci · `ghcr.io/oreondev/harbor-mcp`: 10/100 (this document), [markdown](https://verifymcp.io/servers/oreondev-harbor-mcp/ghcr-io-oreondev-harbor-mcp.md), [page](https://verifymcp.io/servers/oreondev-harbor-mcp/ghcr-io-oreondev-harbor-mcp)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/oreondev/harbor-mcp`
- Version: `0.1.1`
- 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 image's dependency list comes from an SBOM its publisher attached, which nothing verifies, so we will not report it as a clean result.
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: this image's dependency list comes from an SBOM its publisher attached. It names packages and versions but not whether each is deprecated, still maintained or linked to its source, so there is nothing we can fairly grade.
- **Provenance & Transparency**: 48/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 0 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 0/100
  - Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to assess.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to compare.
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool definitions to assess.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool text to scan.
- **Capabilities**: 0/100
  - Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we never saw its MCP handshake.

**Unverified: 6 categories.** Categories scored 0 because we could not verify them: 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 Harbor MCP server?

Harbor runs locally as a container image, launched with docker run --rm -i -e HARBOR_URL -e HARBOR_USERNAME -e HARBOR_PASSWORD -e HARBOR_INSECURE_SKIP_VERIFY -e HARBOR_MCP_RATE ghcr.io/oreondev/harbor-mcp:0.1.1. 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 oreondev-harbor-mcp -- docker run --rm -i -e HARBOR_URL -e HARBOR_USERNAME -e HARBOR_PASSWORD -e HARBOR_INSECURE_SKIP_VERIFY -e HARBOR_MCP_RATE ghcr.io/oreondev/harbor-mcp:0.1.1
```

This image reads HARBOR_URL, HARBOR_USERNAME, HARBOR_PASSWORD, HARBOR_INSECURE_SKIP_VERIFY and HARBOR_MCP_RATE. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### Cursor

```json
{
  "mcpServers": {
    "oreondev-harbor-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "HARBOR_URL",
        "-e",
        "HARBOR_USERNAME",
        "-e",
        "HARBOR_PASSWORD",
        "-e",
        "HARBOR_INSECURE_SKIP_VERIFY",
        "-e",
        "HARBOR_MCP_RATE",
        "ghcr.io/oreondev/harbor-mcp:0.1.1"
      ]
    }
  }
}
```

This image reads HARBOR_URL, HARBOR_USERNAME, HARBOR_PASSWORD, HARBOR_INSECURE_SKIP_VERIFY and HARBOR_MCP_RATE. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### VS Code

```json
{
  "servers": {
    "oreondev-harbor-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "HARBOR_URL",
        "-e",
        "HARBOR_USERNAME",
        "-e",
        "HARBOR_PASSWORD",
        "-e",
        "HARBOR_INSECURE_SKIP_VERIFY",
        "-e",
        "HARBOR_MCP_RATE",
        "ghcr.io/oreondev/harbor-mcp:0.1.1"
      ]
    }
  }
}
```

This image reads HARBOR_URL, HARBOR_USERNAME, HARBOR_PASSWORD, HARBOR_INSECURE_SKIP_VERIFY and HARBOR_MCP_RATE. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### Codex

```bash
codex mcp add oreondev-harbor-mcp -- docker run --rm -i -e HARBOR_URL -e HARBOR_USERNAME -e HARBOR_PASSWORD -e HARBOR_INSECURE_SKIP_VERIFY -e HARBOR_MCP_RATE ghcr.io/oreondev/harbor-mcp:0.1.1
```

This image reads HARBOR_URL, HARBOR_USERNAME, HARBOR_PASSWORD, HARBOR_INSECURE_SKIP_VERIFY and HARBOR_MCP_RATE. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "oreondev-harbor-mcp": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "-e",
        "HARBOR_URL",
        "-e",
        "HARBOR_USERNAME",
        "-e",
        "HARBOR_PASSWORD",
        "-e",
        "HARBOR_INSECURE_SKIP_VERIFY",
        "-e",
        "HARBOR_MCP_RATE",
        "ghcr.io/oreondev/harbor-mcp:0.1.1"
      ],
      "enabled": true
    }
  }
}
```

This image reads HARBOR_URL, HARBOR_USERNAME, HARBOR_PASSWORD, HARBOR_INSECURE_SKIP_VERIFY and HARBOR_MCP_RATE. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### Hermes

```yaml
mcp_servers:
  oreondev-harbor-mcp:
    command: "docker"
    args: ["run", "--rm", "-i", "-e", "HARBOR_URL", "-e", "HARBOR_USERNAME", "-e", "HARBOR_PASSWORD", "-e", "HARBOR_INSECURE_SKIP_VERIFY", "-e", "HARBOR_MCP_RATE", "ghcr.io/oreondev/harbor-mcp:0.1.1"]
```

This image reads HARBOR_URL, HARBOR_USERNAME, HARBOR_PASSWORD, HARBOR_INSECURE_SKIP_VERIFY and HARBOR_MCP_RATE. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### Netclaw

```json
{
  "McpServers": {
    "oreondev-harbor-mcp": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "-e",
        "HARBOR_URL",
        "-e",
        "HARBOR_USERNAME",
        "-e",
        "HARBOR_PASSWORD",
        "-e",
        "HARBOR_INSECURE_SKIP_VERIFY",
        "-e",
        "HARBOR_MCP_RATE",
        "ghcr.io/oreondev/harbor-mcp:0.1.1"
      ]
    }
  }
}
```

This image reads HARBOR_URL, HARBOR_USERNAME, HARBOR_PASSWORD, HARBOR_INSECURE_SKIP_VERIFY and HARBOR_MCP_RATE. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### Other

```json
{
  "mcpServers": {
    "oreondev-harbor-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "HARBOR_URL",
        "-e",
        "HARBOR_USERNAME",
        "-e",
        "HARBOR_PASSWORD",
        "-e",
        "HARBOR_INSECURE_SKIP_VERIFY",
        "-e",
        "HARBOR_MCP_RATE",
        "ghcr.io/oreondev/harbor-mcp:0.1.1"
      ]
    }
  }
}
```

This image reads HARBOR_URL, HARBOR_USERNAME, HARBOR_PASSWORD, HARBOR_INSECURE_SKIP_VERIFY and HARBOR_MCP_RATE. Set them in your client's env block for this server; docker run -e passes each one through to the container.

## 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-05 (score 10, 0)

- [functional] Package version: 0.1.0 → 0.1.1

### 2026-11-04 (score 10)

First indexed and scored.

## MCP tools (0)

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.

## Diagnostics

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

## Score history

- 2026-11-05: 10
- 2026-11-04: 10

## Common questions

### What is the Harbor MCP server?

Harbor is an MCP server listed in the public MCP registry as io.github.oreondev/harbor-mcp. Read-only access to a Harbor registry: projects, artifacts, vulnerabilities, robots and replication. This page covers its container image (ghcr.io/oreondev/harbor-mcp).

### Is the Harbor MCP server safe to use?

Harbor scores 10 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.

### Is the Harbor MCP server still maintained?

Harbor 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 Harbor MCP server under?

Harbor declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the Harbor MCP server?

VerifyMCP ran 5 checks on Harbor, covering Source repository, Provenance, License, Maintenance and 1 more. 9 items could not be completed, a gap on our side rather than a finding about Harbor: Malware scan, Known CVEs, Install scripts, Dependency health and 5 more. 6 categories score 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a container image, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- GitHub Container Registry: https://ghcr.io/oreondev/harbor-mcp
- Repository: https://github.com/oreondev/harbor-mcp
- Website: https://www.oreonit.com/harbor-mcp/
- Changelog RSS feed: https://verifymcp.io/servers/oreondev-harbor-mcp/ghcr-io-oreondev-harbor-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/oreondev-harbor-mcp/ghcr-io-oreondev-harbor-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/oreondev-harbor-mcp/ghcr-io-oreondev-harbor-mcp.json
- HTML version of this page: https://verifymcp.io/servers/oreondev-harbor-mcp/ghcr-io-oreondev-harbor-mcp