Harbor Registry MCP server
Harbor Registry MCP — projects, repos, artifacts, storage reports, cleanup (with dry-run).
1 stars38 downloads/wk
Reviews
Write oneNobody has reviewed Harbor Registry yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Harbor Registry tools (10, 3 write)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
_parse_boolParse an env-var boolean.
harbor_cleanup_candidatesSuggest which artifacts could be deleted to reclaim space.
harbor_delete_artifactwrite actionDelete a single artifact by tag or digest.
harbor_delete_old_artifactswrite actionKeep the N newest artifacts in a repository, delete the rest.
harbor_delete_untaggedwrite actionDelete all untagged artifacts in a project (or single repository).
harbor_list_artifactsList artifacts (tags) in a repository, newest first.
harbor_list_projectsList Harbor projects, sorted by repository count (descending *within the page*).
harbor_list_reposList repositories in a Harbor project.
harbor_storage_reportFull storage breakdown for a Harbor project.
mainEntry point for the ``harbor-registry-mcp`` console script (stdio).
Public scan report
scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it
- Code scan10 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitystatic API keys via environment variables6/15
- Maintenancelast push 45 days ago12/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Harbor Registry compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 78/100
- higher than 57% of 48,273 servers
- Tools
- 10
- the typical server has 7
- Tools that change things
- 30%
- typical: 0%. Fewer write tools means less an agent can break
- GitHub stars
- 1
- more than 65% of 28,534 servers
- Downloads a week
- 38
- more than 30% of 11,915 servers with a package
What its tools let an agent do: 7 read · 3 change
Install Harbor Registry in Claude Code, Cursor or VS Code
claude mcp add harbor-registry-mcp -- uvx harbor-registry-mcp
What the publisher says
From the Harbor Registry repository's README, as published. We do not edit it. Read it on GitHub
harbor-registry-mcp
<!-- mcp-name: io.github.mshegolev/harbor-registry-mcp -->
MCP server for Harbor Registry. Lets an LLM agent (Claude Code, Cursor, OpenCode, etc.) list projects, repositories and artifacts, run storage reports, find cleanup candidates, and delete untagged or old artifacts — all with safety rails (dry-run by default for bulk delete).
Python, FastMCP, stdio transport.
Works with any Harbor 2.x instance — SaaS or self-hosted / on-prem.
Why another Harbor MCP?
A couple of community Harbor MCPs exist (nomagicln/mcp-harbor, bupd/harbor-mcp-server) but they expose only the basic list/get endpoints. This one adds storage reports, cleanup candidates, delete untagged, and delete old artifacts with dry-run — the operations DevOps engineers actually need to reclaim disk space.
Design highlights
- Tool annotations — read-only tools get readOnlyHint: True; destructive ones (harbordelete) carry destructiveHint: True so MCP clients ask for confirmation.
- Dry-run by default on both bulk cleanups (harbordeleteuntagged, harbordeleteoldartifacts) — the agent must pass dryrun=False to execute.
- Structured output — every tool returns a typed payload (TypedDict) + a markdown summary.
- Structured errors — 401 / 403 / 404 / 429 / 5xx mapped to actionable hints.
- Pydantic input validation for every argument.
- Vulnerability snapshot — harborlistartifacts surfaces scan status and counts if withscanoverview is enabled.
Features (8 tools)
Discovery & inspection
- harborlistprojects — projects with repo counts and visibility
- harborlistrepos — repositories in a project
- harborlistartifacts — artifacts in a repository with tags/size/scan status
- harborstoragereport — full project storage breakdown (all repos × all artifacts)
Cleanup planning
- harborcleanupcandidates — suggest what to delete (untagged, never-pulled, old versions)
Cleanup execution (destructive)
- harbordeleteartifact — delete a single artifact by tag or digest
- harbordeleteuntagged — delete all untagged artifacts in a project/repo (dry-run default)
- harbordeleteold_artifacts — keep N latest per repo, delete the rest (dry-run default)
Installation
Requires Python 3.10+.
# via uvx (recommended)
uvx --from harbor-registry-mcp harbor-registry-mcp
# or via pipx
pipx install harbor-registry-mcpConfiguration
claude mcp add harbor -s project \
--env HARBOR_URL=https://harbor.example.com \
--env HARBOR_USERNAME='robot$your-robot' \
--env HARBOR_PASSWORD=your-robot-token \
--env HARBOR_SSL_VERIFY=true \
-- uvx --from harbor-registry-mcp harbor-registry-mcpOr in .mcp.json:
{
"mcpServers": {
"harbor": {
"type": "stdio",
"command": "uvx",
"args": ["--from", "harbor-registry-mcp", "harbor-registry-mcp"],
"env": {
"HARBOR_URL": "https://harbor.example.com",
"HARBOR_USERNAME": "robot$your-robot",
"HARBOR_PASSWORD": "${HARBOR_PASSWORD}",
"HARBOR_SSL_VERIFY": "true"
}
}
}
}Check:
claude mcp list
# harbor: uvx --from harbor-registry-mcp harbor-registry-mcp - ✓ ConnectedEnvironment variables
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Harbor Registry: common questions
- Is Harbor Registry MCP server safe?
- Mostly: it is graded B (78/100). Read the Harbor Registry safety report
- How do I install Harbor Registry?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Harbor Registry need an API key?
- Yes. The registry entry asks for
HARBOR_PASSWORD. - Is Harbor Registry maintained?
- The last commit was 81 days ago (2026-08-13). The latest release is v0.1.0.
- How does Harbor Registry compare with other MCP servers?
- safety score 78/100 (higher than 57% of 48,273 servers); tools 10 (the typical server has 7); tools that change things 30% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.