Hanzo
Cloud MCPmcp

get_v1_mcp_servers

ListServers lists the external MCP servers the caller's org has registered.

ListServers lists the external MCP servers the caller's org has registered. Each record carries the URL and the name of the header its credential is injected into; the credential VALUE lives only in KMS and is never returned, so hasSecret is the whole of what this surface says about it.

Toolget_v1_mcp_servers
Doorhttps://api.hanzo.ai/v1/mcp
Methodtools/call (JSON-RPC 2.0)
Arguments0
OperationGET /v1/mcp/servers
Productmcp

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_mcp_servers",
         "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

OperationRouteProductSummary
get_v1_mcp_serversGET /v1/mcp/serversmcpLists the external MCP servers the caller's org has registered.

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


All 755 tools · The door · API reference

Generated from tools/list on https://api.hanzo.ai/v1/mcp — 833 tools captured 2026-08-01, of which 755 are documented here (the operator surface is not published) (this build read the vendored copy; the door was unreachable).

How is this guide?

On this page