Cloud MCPregistry
registry
6 MCP tools on the Hanzo cloud door that call the registry API.
The 6 tools tools/list names for registry. Each dispatches to an operation in the registry API reference.
| Tool | Route | Arguments | Description |
|---|---|---|---|
get_v1_registry_images | GET /v1/registry/images | 0 | Images lists the org's container repositories, read live from the OCI catalog and filtered server-si |
get_v1_registry_packages | GET /v1/registry/packages | 1 | Packages lists the org's npm packages — <org> and @<org>/… — from the npm registry's search inde |
get_v1_registry_projects | GET /v1/registry/projects | 0 | Projects lists the namespaces the caller can see with what each holds: the org's slug, its repositor |
get_v1_registry_status | GET /v1/registry/status | 0 | Status reports whether the OCI and npm registries are reachable and, when the OCI half is auth-gated |
get_v1_registry_tags | GET /v1/registry/tags | 1 | Tags lists one org-owned repository's tags, read live from the OCI registry. |
post_v1_registry_token | POST /v1/registry/token | 1 | Token mints a short-lived, pull-only registry token for exactly one of the org's images, through the |
Generated from tools/list on https://api.hanzo.ai/v1/mcp — 834 tools captured 2026-08-01 (this build read the vendored copy; the door was unreachable).
How is this guide?