Hanzo
OpenapiTools

Pulls the public MCP registry into our canonical copy and reports what changed.

Pulls the public MCP registry into our canonical copy and reports what changed. SuperAdmin only; every other caller is refused.

POST /v1/tools/catalog/sync

Addresshttps://api.hanzo.ai/v1/tools/catalog/sync
MethodPOST
Operationpost_tools_catalog_sync
AuthAuthorization: Bearer $HANZO_API_KEY

Pulls the public MCP registry into our canonical copy and reports what changed. SuperAdmin only; every other caller is refused.

It is IDEMPOTENT: a listing is keyed by the publisher's own reverse-DNS name, so a second pass over an unchanged registry rewrites the same rows and reports added=0, updated=0. It never deletes — a listing that vanishes upstream may be one an org has already enabled, and dropping its description would not drop its server. And it never touches CURATION: hidden, featured, an admin-set official and a logo survive every sync, because the write does not name those columns.

Request

The document declares no body for POST /v1/tools/catalog/sync. The handler is typed in cloud but its shape is not yet emitted, so the fields are not listed here — ask the MCP door's describe for post_tools_catalog_sync, which answers from the running route.

Response

StatusBodyMeaning
200mcpCatalogSyncok

200 body — 4 fields.

FieldInTypeAlwaysDescription
addedbodyintegerAdded is how many listings the catalog did not have before.
registrybodystringRegistry is the upstream this pass read.
totalbodyintegerTotal is how many listings the catalog holds now.
updatedbodyintegerUpdated is how many the publisher has changed since we last looked.

Failure carries the platform error shape — see Errors.

Examples

hanzo tools catalog sync

Tools API · All Hanzo APIs · Interactive reference

How is this guide?

On this page