Trust

trust: 17 operations.

Also for this capability: API · CLI · MCP · SDKs

trust: 17 operations. Name one in "op" and pass that operation's own arguments in "input". describe returns an operation's input schema.

Tool	`trust`
Address	`https://api.hanzo.ai/v1/mcp`
Method	`tools/call` (JSON-RPC 2.0)
Arguments	2, 1 required
Operation	`GET /v1/trust/coverage` · `GET /v1/trust/coverage/{framework}` · `GET /v1/trust/evidence` · `GET /v1/trust/faq` · `GET /v1/trust/profile` · `GET /v1/trust/risk`
Product	trust

Arguments

Field	Type	Required	Default	Values	Description
`input`	`object`	—	—	—	arguments for the chosen op
`op`	`string`	yes	—	—	—

tools/list declares a type, a description, which fields are required and an enumerated value set for each field and nothing further, and every column above is MCP's own. This tool takes an operation name and that operation's arguments, so what the document constrains is what goes inside input, field by field, on the operation you name — ask describe for that. A — means MCP does not constrain the field.

Call it

A tools/call carries every argument in one flat object — nothing binds to a path or a query string. This call carries exactly the arguments the operation requires, so it is the smallest one that can run.

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": "trust",
         "arguments": {
           "op": "list_trusts"
         }
       }
     }'

Values are the operation's own defaults and enumerated values where it declares them, and a <placeholder> where neither source declares one. tools/list needs no credential; tools/call does — called without one MCP 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

trust dispatches to 17 operations. 6 of them MCP names exactly as the document ids them, and those are below; for the rest MCP has its own verb, which describe resolves.

Operation	Route	Product	Summary
`get_trust_coverage`	`GET /v1/trust/coverage`	trust	Reads coverage: per framework, how many clauses have an automated control behind them, how many are partial, and how many have none — each carrying the unit it is counted in, because "12 of 20" is not a fact until you know what the 20 are.
`get_trust_coverage_by_framework`	`GET /v1/trust/coverage/{framework}`	trust	Reads one framework clause by clause: every clause the standard publishes, what covers it, and which controls stand behind it — so a coverage number can be checked line by line rather than taken on trust.
`get_trust_evidence`	`GET /v1/trust/evidence`	trust	Reads the audit rows that stand behind one control, over a window.
`get_trust_faq`	`GET /v1/trust/faq`	trust	Lists your knowledge base — the questions a reviewer asks, answered once.
`get_trust_profile`	`GET /v1/trust/profile`	trust	Reads your organization's trust-centre profile — the name, tagline and summary a visitor sees, whether the centre is published, and where to send somebody who wants a gated document.
`get_trust_risk`	`GET /v1/trust/risk`	trust	Reads your risk profile — the label and value pairs describing what your organization handles and how.

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

All 120 tools · MCP · API reference

Generated from tools/list on https://api.hanzo.ai/v1/mcp — 120 tools captured 2026-09-30.

Was this page useful?

PreviousTranslate NextUsage