Developer · Local MCP server
Harbor Registry MCP
Harbor Registry MCP - projects, repos, artifacts, storage reports, cleanup (with dry-run).
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.mshegolev/harbor-registry-mcp- Version
- 0.1.0
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- PyPI
- Published
- 2026-04-18
- Updated
- 2026-04-18
- Publisher
- mshegolev (GitHub) · 7 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/mshegolev) · how
- Repository
- github.com/mshegolev/harbor-registry-mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| PyPI | harbor-registry-mcp | 0.1.0 | stdio |
How to connect Harbor Registry MCP
Harbor Registry MCP runs locally from a Python package published to PyPI: harbor-registry-mcp version 0.1.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Python; clients usually start it with uvx (from uv) or after pip install - the usual command is uvx harbor-registry-mcp. It reads these environment variables: HARBOR_URL (required), HARBOR_USERNAME (required), HARBOR_PASSWORD (required, secret) and HARBOR_SSL_VERIFY; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"harbor-registry-mcp": {
"command": "uvx",
"args": [
"harbor-registry-mcp"
],
"env": {
"HARBOR_URL": "<value>",
"HARBOR_USERNAME": "<value>",
"HARBOR_PASSWORD": "<secret>",
"HARBOR_SSL_VERIFY": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from mshegolev (GitHub)
| Server | Runs |
|---|---|
| Allure Testops MCPAllure TestOps MCP - projects, launches, test cases, test results via REST API. | Local · stdio |
| Gitlab Ci MCPGitLab CI/CD MCP - pipelines, jobs, schedules, MRs, files. Any GitLab (SaaS or self-hosted). | Local · stdio |
| Jaeger MCPJaeger MCP - search traces, inspect spans, map service dependencies (read-only). | Local · stdio |
| Kibana MCPKibana/Elasticsearch MCP - log search, aggregations, index discovery, dashboards. | Local · stdio |
| Prometheus MCPPrometheus MCP - query metrics, inspect alerts, and explore scrape targets (read-only). | Local · stdio |
| Sonarqube MCPSonarQube MCP - projects, metrics, quality gate, issues, worst-metric ranking. | Local · stdio |
More developer servers
| Server | Runs |
|---|---|
| GuniWeb SAP MCPSAP S/4HANA and ECC: OData V2/V4, IDoc and RFC/BAPI for n8n and other MCP clients. | Local · stdio |
| H/Ai BrowserLet AI agents drive VS Code's built-in browser alongside you, with click-to-source. | Local · stdio |
| HackerEarth MCPGive any AI assistant a code run button via HackerEarth. 24 languages, zero setup. | Local · stdio |
| HallucC - Hallucination & Safety GuardianFact-check LLM outputs with cited sources. API key: aihcc.cloud/keys. | Remote · HTTPLive check: sign-in required |
| Hardware ProbeHardware probe for performance diagnostics, thermal monitoring, and LLM optimization. | Local · stdio |
| Hares - MCP security scannerMulti-layer security scanner for MCP servers and agent skills (injection, exfiltration) | Local · stdio |
| HarnessScopeTurn-level governance observability for Claude Code transcripts. Local-first, no LLM inside. | Local · stdio |
| HarvestPlain-English training-data scout: 12 experts sweep HuggingFace + GitHub, compose scored packs. | Local · stdio |