Cloud MCPtools
tools
8 MCP tools on the Hanzo cloud door that call the tools API.
| Tool | Route | Arguments | Description |
|---|---|---|---|
get_v1_tools | GET /v1/tools | 2 | ListTools lists every tool the caller's org and project can reach, from every source, each flagged w |
get_v1_tools_activation | GET /v1/tools/activation | 0 | GetActivation reports which tools are switched on for the caller's org and project. |
get_v1_tools_catalog | GET /v1/tools/catalog | 5 | ListCatalog lists the MCP servers the public registries publish, as we hold them: our canonical copy |
get_v1_tools_catalog_id | GET /v1/tools/catalog/{id} | 1 | GetListing returns one catalog entry in full: the publisher's description, its repository and site, |
patch_v1_tools_catalog_id | PATCH /v1/tools/catalog/{id} | 5 | CurateListing sets what WE say about one catalog entry — hidden, featured, official, logo — and answ |
post_v1_tools_call | POST /v1/tools/call | 2 | CallTool runs one of the caller's activated tools and answers with its output. |
post_v1_tools_catalog_sync | POST /v1/tools/catalog/sync | 0 | SyncCatalog pulls the public MCP registry into our canonical copy and reports what changed. |
put_v1_tools_activation | PUT /v1/tools/activation | 2 | PutActivation switches tools on and off for the caller's org and project, and answers with the resul |
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?