get_v1_sites
ListSites returns the org's deployed sites at the pretty URLs they serve at.
ListSites returns the org's deployed sites at the pretty URLs they serve at.
It reads the SAME org-scoped store as /v1/projects and keeps only the projects
that are actually live, so a draft or a failed build is not advertised as a
site.
Scope: a validated principal is required (403 without one) and the list is keyed by that principal's org.
| Tool | get_v1_sites |
| Door | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 0 |
| Operation | GET /v1/sites |
| Product | sites |
Arguments
This tool declares no arguments. Call it with an empty arguments object.
Call it
A tools/call carries its arguments in one flat object. This tool declares none, so the object is empty.
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_sites",
"arguments": {}
}
}'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_sites | GET /v1/sites | sites | ListSites returns the org's deployed sites at the pretty URLs they serve at. |
The same capability over plain HTTP is in the sites API reference, on https://api.hanzo.ai.
All 833 tools · The door · API reference
Generated from tools/list on https://api.hanzo.ai/v1/mcp — 833 tools captured 2026-08-01 (this build read the vendored copy; the door was unreachable).
How is this guide?