get_v1_tools_catalog

ListCatalog lists the MCP servers the public registries publish, as we hold them: our canonical copy of registry.modelcontextprotocol.io, plus what we decided about each entry.

This is the SHELF an org picks from. A listing with a streamable-http endpoint can be enabled as-is — POST /v1/mcp/servers with its id — and its tools then join the org's tool plane and the fleet's MCP door. A listing that only ships a stdio package needs a process to run it, which is why the transports are on every entry rather than implied.

Hidden entries are absent: they are the ones we took off the shelf. A platform SuperAdmin sees them, because the same query answers "what is on the shelf" and "what is in the catalog" and two queries would drift apart.

It is PAGED — 50 by default, 200 at most. The public registry publishes tens of thousands of servers, so an unbounded answer is a twenty-megabyte response and a storefront that renders in a minute. total is the whole match, not the page.


Tool	`get_v1_tools_catalog`
Door	`https://api.hanzo.ai/v1/mcp`
Method	`tools/call` (JSON-RPC 2.0)
Arguments	5
Operation	`GET /v1/tools/catalog`
Product	tools

Arguments

Field	Type	Required	Default	Description
`featured`	`string`	—	—	Featured keeps only the listings we put on the front of the shelf, and only when it is exactly the string "true".
`limit`	`integer`	—	—	Limit bounds the page: default 50, maximum 200. A value that is not a positive integer reads as the default.
`official`	`string`	—	—	Official keeps only the vendors' OWN servers — not third-party copies of them — and only when it is exactly the string "true".
`offset`	`integer`	—	—	Offset skips that many listings.
`q`	`string`	—	—	Q matches the name, title or description, case-insensitively.

This tool's schema does not declare which fields are required, nor any default, nor any enumerated value set. The columns above are empty because the door publishes nothing there, not because the answer is "none" — where a field is constrained, the constraint is stated in that field's own description.

Call it

A tools/call carries every argument in one flat object — nothing binds to a path or a query string. Every declared argument is shown, because the door marks none of them required.

curl -X POST https://api.hanzo.ai/v1/mcp \
  -H "Authorization: Bearer $HANZO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
       "jsonrpc": "2.0",
       "id": 1,
       "method": "tools/call",
       "params": {
         "name": "get_v1_tools_catalog",
         "arguments": {
           "featured": "<featured>",
           "limit": 0,
           "official": "<official>",
           "offset": 0,
           "q": "<q>"
         }
       }
     }'

Values are placeholders derived from each field's declared type. tools/list needs no credential; tools/call does — called without one the door answers HTTP 200 with a JSON-RPC result whose isError is set and whose text says what was missing. How to get a key →

The operation behind it

Operation	Route	Product	Summary
`cloud_get_v1_tools_catalog`	`GET /v1/tools/catalog`	tools	ListCatalog lists the MCP servers the public registries publish, as we hold them: our cano

The same capability over plain HTTP is in the tools API reference, on https://api.hanzo.ai.

All 834 tools · The door · API reference

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).

get_v1_tools_catalog

Arguments

Call it

The operation behind it

On this page