Hanzo
Cloud MCPcompany

post_v1_company_fundraise_safe

RequestSafe raises an e-signature request over documents already in the org's data room — a SAFE, a convertible note, or any other fundraising paper.

RequestSafe raises an e-signature request over documents already in the org's data room — a SAFE, a convertible note, or any other fundraising paper. Available only after incorporation (stage company).

Toolpost_v1_company_fundraise_safe
Doorhttps://api.hanzo.ai/v1/mcp
Methodtools/call (JSON-RPC 2.0)
Arguments2
OperationPOST /v1/company/fundraise/safe
Productcompany

Arguments

FieldTypeRequiredDefaultValuesDescription
documentIdsstring[]DocumentIDs are data room document ids to raise a signature request over. Required.
signersSigner[]Signers are the recipients, each a name and an email. Required.

tools/list declares a type and a description for each field and nothing further. A means neither the door nor that operation constrains the field.

Object types

Signer is an object this tool's fields are made of, declared inside the tool's own schema and enumerated in full below.

Signer

FieldTypeRequiredDefaultValuesDescription
emailstringEmail is the address the signature request is sent to.
namestringName is the recipient's name, as it appears on the signature request.

Call it

A tools/call carries every argument in one flat object — nothing binds to a path or a query string. Nothing above is required, so every declared argument is shown rather than a guess at which matter.

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": "post_v1_company_fundraise_safe",
         "arguments": {
           "documentIds": [
             "<documentIds>"
           ],
           "signers": [
             {
               "email": "<email>",
               "name": "<name>"
             }
           ]
         }
       }
     }'

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 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
post_v1_company_fundraise_safePOST /v1/company/fundraise/safecompanyRaises an e-signature request over documents already in the org's data room — a SAFE, a…

The same capability over plain HTTP is in the company 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