MCP MeasureMCP Measure

索引已观测

ZapSign

ZapSign electronic document signing via the official API: create documents for signature (from PDF,

我该使用它吗

质量与安全性

B
描述质量
97%
模式完整度
67%
命名质量
78%
投毒风险
60%
权限匹配度
80%
协议合规性
100%

发现（13）

  • HIGHTool poisoning patterns detected
  • MEDIUMTool 'zapsign_webhooks_write_create' description contains placeholder text在 zapsign_webhooks_write_create 中
  • MEDIUMTool 'zapsign_webhooks_write_delete' description contains placeholder text在 zapsign_webhooks_write_delete 中
  • LOWTool 'connect' description lacks action verb在 connect 中
  • LOWTool 'zapsign_documents_write_create_from_template' name length outside 3-30 range在 zapsign_documents_write_create_from_template 中
  • LOWTool 'zapsign_documents_write_place_signatures' name length outside 3-30 range在 zapsign_documents_write_place_signatures 中
  • LOWTool 'zapsign_documents_write_add_extra_doc' name length outside 3-30 range在 zapsign_documents_write_add_extra_doc 中
  • LOWTool 'zapsign_account_write_create_user' name length outside 3-30 range在 zapsign_account_write_create_user 中
  • LOWTool 'zapsign_account_write_delete_user' name length outside 3-30 range在 zapsign_account_write_delete_user 中
  • LOWTool 'zapsign_webhooks_write_create' suggests web access but openWorldHint=false在 zapsign_webhooks_write_create 中

基于对工具定义和协议合规性的自动分析。

上下文开销

~9,176token 数（工具定义）
~793 B典型响应大小
对注意力有显著影响（占 128k 上下文窗口的 7.17%）

这是每次将服务器的工具加载到模型上下文窗口时所消耗的大致 token 数。数值越高，可用于其他任务的注意力就越少。

安装

一键安装

将以下内容添加到你的 `claude_desktop_config.json` 文件中：

{
  "mcpServers": {
    "zapsign-mcp": {
      "url": "https://api.mcp.ai/p_zapsign"
    }
  }
}

远程端点

https://api.mcp.ai/p_zapsignstreamable-http

它能做什么

工具清单

工具（35）

🟢 只读🟡 写入🔴 删除⚪ 未知
🟢zapsign_list_accounts(account)

Lista contas ZapSign vinculadas a este install — id e apelido.

输入模式

{
  "type": "object",
  "properties": {
    "account": {
      "type": "string"
    }
  },
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢zapsign_documents_list(doc_token, status, folder_path, deleted, signer_email, ...)

Documentos de assinatura no ZapSign (leitura). Ações: list (filtros: page, status pending|signed|refused, folder_path, deleted, signer_email, created_from/created_to YYYY-MM-DD, sort_order asc|desc, include_signers); get (doc_token — detalhe + signatários + extra_docs + URLs de arquivo, que expiram em 60min); signer_log (doc_token — trilha de auditoria; download_pdf=true retorna o PDF do log). [Flattened action: list]

输入模式

{
  "type": "object",
  "properties": {
    "doc_token": {
      "type": "string"
    },
    "status": {
      "type": "string"
    },
    "folder_path": {
      "type": "string"
    },
    "deleted": {
      "type": "boolean"
    },
    "signer_email": {
      "type": "string"
    },
    "created_from": {
      "type": "string"
    },
    "created_to": {
      "type": "string"
    },
    "sort_order": {
      "type": "string",
      "enum": [
        "asc",
        "desc"
      ]
    },
    "include_signers": {
      "type": "boolean"
    },
    "download_pdf": {
      "type": "boolean"
    },
    "page": {
      "type": "number"
    },
    "account": {
      "type": "string"
    }
  },
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢zapsign_documents_get(doc_token, status, folder_path, deleted, signer_email, ...)

Documentos de assinatura no ZapSign (leitura). Ações: list (filtros: page, status pending|signed|refused, folder_path, deleted, signer_email, created_from/created_to YYYY-MM-DD, sort_order asc|desc, include_signers); get (doc_token — detalhe + signatários + extra_docs + URLs de arquivo, que expiram em 60min); signer_log (doc_token — trilha de auditoria; download_pdf=true retorna o PDF do log). [Flattened action: get]

输入模式

{
  "type": "object",
  "properties": {
    "doc_token": {
      "type": "string"
    },
    "status": {
      "type": "string"
    },
    "folder_path": {
      "type": "string"
    },
    "deleted": {
      "type": "boolean"
    },
    "signer_email": {
      "type": "string"
    },
    "created_from": {
      "type": "string"
    },
    "created_to": {
      "type": "string"
    },
    "sort_order": {
      "type": "string",
      "enum": [
        "asc",
        "desc"
      ]
    },
    "include_signers": {
      "type": "boolean"
    },
    "download_pdf": {
      "type": "boolean"
    },
    "page": {
      "type": "number"
    },
    "account": {
      "type": "string"
    }
  },
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢zapsign_documents_signer_log(doc_token, status, folder_path, deleted, signer_email, ...)

Documentos de assinatura no ZapSign (leitura). Ações: list (filtros: page, status pending|signed|refused, folder_path, deleted, signer_email, created_from/created_to YYYY-MM-DD, sort_order asc|desc, include_signers); get (doc_token — detalhe + signatários + extra_docs + URLs de arquivo, que expiram em 60min); signer_log (doc_token — trilha de auditoria; download_pdf=true retorna o PDF do log). [Flattened action: signer_log]

输入模式

{
  "type": "object",
  "properties": {
    "doc_token": {
      "type": "string"
    },
    "status": {
      "type": "string"
    },
    "folder_path": {
      "type": "string"
    },
    "deleted": {
      "type": "boolean"
    },
    "signer_email": {
      "type": "string"
    },
    "created_from": {
      "type": "string"
    },
    "created_to": {
      "type": "string"
    },
    "sort_order": {
      "type": "string",
      "enum": [
        "asc",
        "desc"
      ]
    },
    "include_signers": {
      "type": "boolean"
    },
    "download_pdf": {
      "type": "boolean"
    },
    "page": {
      "type": "number"
    },
    "account": {
      "type": "string"
    }
  },
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🔴zapsign_documents_write_create(doc_token, data, account)

Criar/alterar documentos de assinatura no ZapSign. Ações: - create (data): cria documento. Campos: name*, signers[]* (cada {name, email, phone_country, phone_number, auth_mode}); UMA fonte de arquivo: url_pdf | base64_pdf | url_docx | base64_docx | markdown_text; opc lang, disable_signer_emails, date_limit_to_sign, signature_order_active, folder_path, external_id. - create_from_template (data): cria via template. Campos: template_id*, signer_name*, data[]* (cada {de, para} substituindo {{VAR}}); opc signer_email, send_automatic_email, send_automatic_whatsapp, folder_path, external_id, lang. - update (doc_token, data): só com doc "em andamento". Campos: name, date_limit_to_sign, folder_path, extra_docs[]. - delete (doc_token): soft-delete. - refuse (data): cancela/recusa. Campos: doc_token*, rejected_reason*, notify_signer. - place_signatures (doc_token, data): posiciona assinaturas por coordenadas. Campo: rubricas[] ({signer_token, page 0-based, relative_position_left/bottom, relative_size_x/y, type signature|visto}). - add_extra_doc (doc_token, data): anexa PDF extra. Campos: name*, url_pdf | base64_pdf. [Flattened action: create]

输入模式

{
  "type": "object",
  "properties": {
    "doc_token": {
      "type": "string"
    },
    "data": {
      "type": "object",
      "propertyNames": {
        "type": "string"
      },
      "additionalProperties": {}
    },
    "account": {
      "type": "string"
    }
  },
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🔴zapsign_documents_write_create_from_template(doc_token, data, account)

Criar/alterar documentos de assinatura no ZapSign. Ações: - create (data): cria documento. Campos: name*, signers[]* (cada {name, email, phone_country, phone_number, auth_mode}); UMA fonte de arquivo: url_pdf | base64_pdf | url_docx | base64_docx | markdown_text; opc lang, disable_signer_emails, date_limit_to_sign, signature_order_active, folder_path, external_id. - create_from_template (data): cria via template. Campos: template_id*, signer_name*, data[]* (cada {de, para} substituindo {{VAR}}); opc signer_email, send_automatic_email, send_automatic_whatsapp, folder_path, external_id, lang. - update (doc_token, data): só com doc "em andamento". Campos: name, date_limit_to_sign, folder_path, extra_docs[]. - delete (doc_token): soft-delete. - refuse (data): cancela/recusa. Campos: doc_token*, rejected_reason*, notify_signer. - place_signatures (doc_token, data): posiciona assinaturas por coordenadas. Campo: rubricas[] ({signer_token, page 0-based, relative_position_left/bottom, relative_size_x/y, type signature|visto}). - add_extra_doc (doc_token, data): anexa PDF extra. Campos: name*, url_pdf | base64_pdf. [Flattened action: create_from_template]

输入模式

{
  "type": "object",
  "properties": {
    "doc_token": {
      "type": "string"
    },
    "data": {
      "type": "object",
      "propertyNames": {
        "type": "string"
      },
      "additionalProperties": {}
    },
    "account": {
      "type": "string"
    }
  },
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🔴zapsign_documents_write_update(doc_token, data, account)

Criar/alterar documentos de assinatura no ZapSign. Ações: - create (data): cria documento. Campos: name*, signers[]* (cada {name, email, phone_country, phone_number, auth_mode}); UMA fonte de arquivo: url_pdf | base64_pdf | url_docx | base64_docx | markdown_text; opc lang, disable_signer_emails, date_limit_to_sign, signature_order_active, folder_path, external_id. - create_from_template (data): cria via template. Campos: template_id*, signer_name*, data[]* (cada {de, para} substituindo {{VAR}}); opc signer_email, send_automatic_email, send_automatic_whatsapp, folder_path, external_id, lang. - update (doc_token, data): só com doc "em andamento". Campos: name, date_limit_to_sign, folder_path, extra_docs[]. - delete (doc_token): soft-delete. - refuse (data): cancela/recusa. Campos: doc_token*, rejected_reason*, notify_signer. - place_signatures (doc_token, data): posiciona assinaturas por coordenadas. Campo: rubricas[] ({signer_token, page 0-based, relative_position_left/bottom, relative_size_x/y, type signature|visto}). - add_extra_doc (doc_token, data): anexa PDF extra. Campos: name*, url_pdf | base64_pdf. [Flattened action: update]

输入模式

{
  "type": "object",
  "properties": {
    "doc_token": {
      "type": "string"
    },
    "data": {
      "type": "object",
      "propertyNames": {
        "type": "string"
      },
      "additionalProperties": {}
    },
    "account": {
      "type": "string"
    }
  },
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🔴zapsign_documents_write_delete(doc_token, data, account)

Criar/alterar documentos de assinatura no ZapSign. Ações: - create (data): cria documento. Campos: name*, signers[]* (cada {name, email, phone_country, phone_number, auth_mode}); UMA fonte de arquivo: url_pdf | base64_pdf | url_docx | base64_docx | markdown_text; opc lang, disable_signer_emails, date_limit_to_sign, signature_order_active, folder_path, external_id. - create_from_template (data): cria via template. Campos: template_id*, signer_name*, data[]* (cada {de, para} substituindo {{VAR}}); opc signer_email, send_automatic_email, send_automatic_whatsapp, folder_path, external_id, lang. - update (doc_token, data): só com doc "em andamento". Campos: name, date_limit_to_sign, folder_path, extra_docs[]. - delete (doc_token): soft-delete. - refuse (data): cancela/recusa. Campos: doc_token*, rejected_reason*, notify_signer. - place_signatures (doc_token, data): posiciona assinaturas por coordenadas. Campo: rubricas[] ({signer_token, page 0-based, relative_position_left/bottom, relative_size_x/y, type signature|visto}). - add_extra_doc (doc_token, data): anexa PDF extra. Campos: name*, url_pdf | base64_pdf. [Flattened action: delete]

输入模式

{
  "type": "object",
  "properties": {
    "doc_token": {
      "type": "string"
    },
    "data": {
      "type": "object",
      "propertyNames": {
        "type": "string"
      },
      "additionalProperties": {}
    },
    "account": {
      "type": "string"
    }
  },
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🔴zapsign_documents_write_refuse(doc_token, data, account)

Criar/alterar documentos de assinatura no ZapSign. Ações: - create (data): cria documento. Campos: name*, signers[]* (cada {name, email, phone_country, phone_number, auth_mode}); UMA fonte de arquivo: url_pdf | base64_pdf | url_docx | base64_docx | markdown_text; opc lang, disable_signer_emails, date_limit_to_sign, signature_order_active, folder_path, external_id. - create_from_template (data): cria via template. Campos: template_id*, signer_name*, data[]* (cada {de, para} substituindo {{VAR}}); opc signer_email, send_automatic_email, send_automatic_whatsapp, folder_path, external_id, lang. - update (doc_token, data): só com doc "em andamento". Campos: name, date_limit_to_sign, folder_path, extra_docs[]. - delete (doc_token): soft-delete. - refuse (data): cancela/recusa. Campos: doc_token*, rejected_reason*, notify_signer. - place_signatures (doc_token, data): posiciona assinaturas por coordenadas. Campo: rubricas[] ({signer_token, page 0-based, relative_position_left/bottom, relative_size_x/y, type signature|visto}). - add_extra_doc (doc_token, data): anexa PDF extra. Campos: name*, url_pdf | base64_pdf. [Flattened action: refuse]

输入模式

{
  "type": "object",
  "properties": {
    "doc_token": {
      "type": "string"
    },
    "data": {
      "type": "object",
      "propertyNames": {
        "type": "string"
      },
      "additionalProperties": {}
    },
    "account": {
      "type": "string"
    }
  },
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🔴zapsign_documents_write_place_signatures(doc_token, data, account)

Criar/alterar documentos de assinatura no ZapSign. Ações: - create (data): cria documento. Campos: name*, signers[]* (cada {name, email, phone_country, phone_number, auth_mode}); UMA fonte de arquivo: url_pdf | base64_pdf | url_docx | base64_docx | markdown_text; opc lang, disable_signer_emails, date_limit_to_sign, signature_order_active, folder_path, external_id. - create_from_template (data): cria via template. Campos: template_id*, signer_name*, data[]* (cada {de, para} substituindo {{VAR}}); opc signer_email, send_automatic_email, send_automatic_whatsapp, folder_path, external_id, lang. - update (doc_token, data): só com doc "em andamento". Campos: name, date_limit_to_sign, folder_path, extra_docs[]. - delete (doc_token): soft-delete. - refuse (data): cancela/recusa. Campos: doc_token*, rejected_reason*, notify_signer. - place_signatures (doc_token, data): posiciona assinaturas por coordenadas. Campo: rubricas[] ({signer_token, page 0-based, relative_position_left/bottom, relative_size_x/y, type signature|visto}). - add_extra_doc (doc_token, data): anexa PDF extra. Campos: name*, url_pdf | base64_pdf. [Flattened action: place_signatures]

输入模式

{
  "type": "object",
  "properties": {
    "doc_token": {
      "type": "string"
    },
    "data": {
      "type": "object",
      "propertyNames": {
        "type": "string"
      },
      "additionalProperties": {}
    },
    "account": {
      "type": "string"
    }
  },
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🔴zapsign_documents_write_add_extra_doc(doc_token, data, account)

Criar/alterar documentos de assinatura no ZapSign. Ações: - create (data): cria documento. Campos: name*, signers[]* (cada {name, email, phone_country, phone_number, auth_mode}); UMA fonte de arquivo: url_pdf | base64_pdf | url_docx | base64_docx | markdown_text; opc lang, disable_signer_emails, date_limit_to_sign, signature_order_active, folder_path, external_id. - create_from_template (data): cria via template. Campos: template_id*, signer_name*, data[]* (cada {de, para} substituindo {{VAR}}); opc signer_email, send_automatic_email, send_automatic_whatsapp, folder_path, external_id, lang. - update (doc_token, data): só com doc "em andamento". Campos: name, date_limit_to_sign, folder_path, extra_docs[]. - delete (doc_token): soft-delete. - refuse (data): cancela/recusa. Campos: doc_token*, rejected_reason*, notify_signer. - place_signatures (doc_token, data): posiciona assinaturas por coordenadas. Campo: rubricas[] ({signer_token, page 0-based, relative_position_left/bottom, relative_size_x/y, type signature|visto}). - add_extra_doc (doc_token, data): anexa PDF extra. Campos: name*, url_pdf | base64_pdf. [Flattened action: add_extra_doc]

输入模式

{
  "type": "object",
  "properties": {
    "doc_token": {
      "type": "string"
    },
    "data": {
      "type": "object",
      "propertyNames": {
        "type": "string"
      },
      "additionalProperties": {}
    },
    "account": {
      "type": "string"
    }
  },
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢zapsign_signers_get(signer_token, account)

Signatários no ZapSign (leitura). Ação: get (signer_token — status, sign_url, visualizações, geo, auth_mode etc.). [Flattened action: get]

输入模式

{
  "type": "object",
  "properties": {
    "signer_token": {
      "type": "string"
    },
    "account": {
      "type": "string"
    }
  },
  "required": [
    "signer_token"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🔴zapsign_signers_write_add(doc_token, signer_token, data, account)

Gerenciar signatários no ZapSign. Ações: - add (doc_token, data): adiciona signatário. Campos: name*, email*; opc phone_country, phone_number, auth_mode (assinaturaTela|tokenEmail|tokenSms|tokenWhatsapp), lock_name/email/phone, qualification, send_automatic_email, send_automatic_whatsapp, require_document_photo. - update (signer_token, data): atualiza (só antes de assinar) ou reenvia lembrete. Mesmos campos de add. - remove (signer_token): remove (não pode remover quem já assinou nem o único signatário). - sign (data): assina em lote via API (assíncrono). Campos: signer_tokens[]*; opc selfie_photo, document_photo_url. (user_token é injetado automaticamente.) [Flattened action: add]

输入模式

{
  "type": "object",
  "properties": {
    "doc_token": {
      "type": "string"
    },
    "signer_token": {
      "type": "string"
    },
    "data": {
      "type": "object",
      "propertyNames": {
        "type": "string"
      },
      "additionalProperties": {}
    },
    "account": {
      "type": "string"
    }
  },
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🔴zapsign_signers_write_update(doc_token, signer_token, data, account)

Gerenciar signatários no ZapSign. Ações: - add (doc_token, data): adiciona signatário. Campos: name*, email*; opc phone_country, phone_number, auth_mode (assinaturaTela|tokenEmail|tokenSms|tokenWhatsapp), lock_name/email/phone, qualification, send_automatic_email, send_automatic_whatsapp, require_document_photo. - update (signer_token, data): atualiza (só antes de assinar) ou reenvia lembrete. Mesmos campos de add. - remove (signer_token): remove (não pode remover quem já assinou nem o único signatário). - sign (data): assina em lote via API (assíncrono). Campos: signer_tokens[]*; opc selfie_photo, document_photo_url. (user_token é injetado automaticamente.) [Flattened action: update]

输入模式

{
  "type": "object",
  "properties": {
    "doc_token": {
      "type": "string"
    },
    "signer_token": {
      "type": "string"
    },
    "data": {
      "type": "object",
      "propertyNames": {
        "type": "string"
      },
      "additionalProperties": {}
    },
    "account": {
      "type": "string"
    }
  },
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🔴zapsign_signers_write_remove(doc_token, signer_token, data, account)

Gerenciar signatários no ZapSign. Ações: - add (doc_token, data): adiciona signatário. Campos: name*, email*; opc phone_country, phone_number, auth_mode (assinaturaTela|tokenEmail|tokenSms|tokenWhatsapp), lock_name/email/phone, qualification, send_automatic_email, send_automatic_whatsapp, require_document_photo. - update (signer_token, data): atualiza (só antes de assinar) ou reenvia lembrete. Mesmos campos de add. - remove (signer_token): remove (não pode remover quem já assinou nem o único signatário). - sign (data): assina em lote via API (assíncrono). Campos: signer_tokens[]*; opc selfie_photo, document_photo_url. (user_token é injetado automaticamente.) [Flattened action: remove]

输入模式

{
  "type": "object",
  "properties": {
    "doc_token": {
      "type": "string"
    },
    "signer_token": {
      "type": "string"
    },
    "data": {
      "type": "object",
      "propertyNames": {
        "type": "string"
      },
      "additionalProperties": {}
    },
    "account": {
      "type": "string"
    }
  },
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🔴zapsign_signers_write_sign(doc_token, signer_token, data, account)

Gerenciar signatários no ZapSign. Ações: - add (doc_token, data): adiciona signatário. Campos: name*, email*; opc phone_country, phone_number, auth_mode (assinaturaTela|tokenEmail|tokenSms|tokenWhatsapp), lock_name/email/phone, qualification, send_automatic_email, send_automatic_whatsapp, require_document_photo. - update (signer_token, data): atualiza (só antes de assinar) ou reenvia lembrete. Mesmos campos de add. - remove (signer_token): remove (não pode remover quem já assinou nem o único signatário). - sign (data): assina em lote via API (assíncrono). Campos: signer_tokens[]*; opc selfie_photo, document_photo_url. (user_token é injetado automaticamente.) [Flattened action: sign]

输入模式

{
  "type": "object",
  "properties": {
    "doc_token": {
      "type": "string"
    },
    "signer_token": {
      "type": "string"
    },
    "data": {
      "type": "object",
      "propertyNames": {
        "type": "string"
      },
      "additionalProperties": {}
    },
    "account": {
      "type": "string"
    }
  },
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢zapsign_templates_list(template_token, page, account)

Templates (modelos DOCX) no ZapSign (leitura). Ações: list (page — 20/página); get (template_token — inclui inputs[] das variáveis {{VAR}}). [Flattened action: list]

输入模式

{
  "type": "object",
  "properties": {
    "template_token": {
      "type": "string"
    },
    "page": {
      "type": "number"
    },
    "account": {
      "type": "string"
    }
  },
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢zapsign_templates_get(template_token, page, account)

Templates (modelos DOCX) no ZapSign (leitura). Ações: list (page — 20/página); get (template_token — inclui inputs[] das variáveis {{VAR}}). [Flattened action: get]

输入模式

{
  "type": "object",
  "properties": {
    "template_token": {
      "type": "string"
    },
    "page": {
      "type": "number"
    },
    "account": {
      "type": "string"
    }
  },
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🔴zapsign_templates_write_create(template_token, data, account)

Gerenciar templates no ZapSign. Ações: - create (data): cria template DOCX. Campos: name*, docx_url | base64_docx*; opc first_signer{}, lang, observers[], folder_path/folder_token, redirect_link. - update (template_token, data): metadados (o DOCX em si é imutável). Campos: name, lang, observers[], first_signer, folder_path/token, redirect_link. - delete (template_token): irreversível. [Flattened action: create]

输入模式

{
  "type": "object",
  "properties": {
    "template_token": {
      "type": "string"
    },
    "data": {
      "type": "object",
      "propertyNames": {
        "type": "string"
      },
      "additionalProperties": {}
    },
    "account": {
      "type": "string"
    }
  },
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🔴zapsign_templates_write_update(template_token, data, account)

Gerenciar templates no ZapSign. Ações: - create (data): cria template DOCX. Campos: name*, docx_url | base64_docx*; opc first_signer{}, lang, observers[], folder_path/folder_token, redirect_link. - update (template_token, data): metadados (o DOCX em si é imutável). Campos: name, lang, observers[], first_signer, folder_path/token, redirect_link. - delete (template_token): irreversível. [Flattened action: update]

输入模式

{
  "type": "object",
  "properties": {
    "template_token": {
      "type": "string"
    },
    "data": {
      "type": "object",
      "propertyNames": {
        "type": "string"
      },
      "additionalProperties": {}
    },
    "account": {
      "type": "string"
    }
  },
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🔴zapsign_templates_write_delete(template_token, data, account)

Gerenciar templates no ZapSign. Ações: - create (data): cria template DOCX. Campos: name*, docx_url | base64_docx*; opc first_signer{}, lang, observers[], folder_path/folder_token, redirect_link. - update (template_token, data): metadados (o DOCX em si é imutável). Campos: name, lang, observers[], first_signer, folder_path/token, redirect_link. - delete (template_token): irreversível. [Flattened action: delete]

输入模式

{
  "type": "object",
  "properties": {
    "template_token": {
      "type": "string"
    },
    "data": {
      "type": "object",
      "propertyNames": {
        "type": "string"
      },
      "additionalProperties": {}
    },
    "account": {
      "type": "string"
    }
  },
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🔴zapsign_webhooks_write_create(id, data, account, ids)

Gerenciar webhooks no ZapSign (não há endpoint de listagem na API). Ações: - create (data): cria webhook (1 por conta cobre todos os docs). Campos: url*; opc type ("" = todos | doc_signed | doc_created | doc_deleted | ...), doc_token, headers. Retorna {id}. - delete (id): remove webhook pelo id retornado na criação. [Flattened action: create] Bulk support: accepts ids for batched execution.

输入模式

{
  "type": "object",
  "properties": {
    "id": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "number"
        }
      ]
    },
    "data": {
      "type": "object",
      "propertyNames": {
        "type": "string"
      },
      "additionalProperties": {}
    },
    "account": {
      "type": "string"
    },
    "ids": {
      "type": "array",
      "items": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "number"
          }
        ]
      }
    }
  },
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🔴zapsign_webhooks_write_delete(id, data, account, ids)

Gerenciar webhooks no ZapSign (não há endpoint de listagem na API). Ações: - create (data): cria webhook (1 por conta cobre todos os docs). Campos: url*; opc type ("" = todos | doc_signed | doc_created | doc_deleted | ...), doc_token, headers. Retorna {id}. - delete (id): remove webhook pelo id retornado na criação. [Flattened action: delete] Bulk support: accepts ids for batched execution.

输入模式

{
  "type": "object",
  "properties": {
    "id": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "number"
        }
      ]
    },
    "data": {
      "type": "object",
      "propertyNames": {
        "type": "string"
      },
      "additionalProperties": {}
    },
    "account": {
      "type": "string"
    },
    "ids": {
      "type": "array",
      "items": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "number"
          }
        ]
      }
    }
  },
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢zapsign_checks_get(check_id, account, check_ids)

Verificação de antecedentes no ZapSign (leitura). Ação: get (check_id — status not_started|in_progress|delayed|error|completed + pdf_report). [Flattened action: get] Bulk support: accepts check_ids for batched execution.

输入模式

{
  "type": "object",
  "properties": {
    "check_id": {
      "type": "string"
    },
    "account": {
      "type": "string"
    },
    "check_ids": {
      "type": "array",
      "items": {
        "type": "string"
      }
    }
  },
  "required": [
    "check_id"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟡zapsign_checks_write_create(data, account)

Criar verificação de antecedentes no ZapSign (consome créditos). Ação: create (data). Campos: country* (BR|CO|CL|MX|PE), type* (ex.: person | credit_person_br), user_authorized: true*, e um identificador: national_id | foreign_id. [Flattened action: create]

输入模式

{
  "type": "object",
  "properties": {
    "data": {
      "type": "object",
      "propertyNames": {
        "type": "string"
      },
      "additionalProperties": {}
    },
    "account": {
      "type": "string"
    }
  },
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢zapsign_account_plan(page, account)

Conta ZapSign (leitura). Ações: plan (info do plano: créditos, status, período); users (page — lista usuários da conta, 25/página). [Flattened action: plan]

输入模式

{
  "type": "object",
  "properties": {
    "page": {
      "type": "number"
    },
    "account": {
      "type": "string"
    }
  },
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢zapsign_account_users(page, account)

Conta ZapSign (leitura). Ações: plan (info do plano: créditos, status, período); users (page — lista usuários da conta, 25/página). [Flattened action: users]

输入模式

{
  "type": "object",
  "properties": {
    "page": {
      "type": "number"
    },
    "account": {
      "type": "string"
    }
  },
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🔴zapsign_account_write_create_user(email, data, account)

Gerenciar usuários da conta ZapSign. Ações: - create_user (data): adiciona usuário. Campos: email*; opc role (member|admin|self_docs_limited), first_name, last_name, phone_country, phone_number. - delete_user (email): remove usuário (donos não podem ser removidos). [Flattened action: create_user]

输入模式

{
  "type": "object",
  "properties": {
    "email": {
      "type": "string"
    },
    "data": {
      "type": "object",
      "propertyNames": {
        "type": "string"
      },
      "additionalProperties": {}
    },
    "account": {
      "type": "string"
    }
  },
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🔴zapsign_account_write_delete_user(email, data, account)

Gerenciar usuários da conta ZapSign. Ações: - create_user (data): adiciona usuário. Campos: email*; opc role (member|admin|self_docs_limited), first_name, last_name, phone_country, phone_number. - delete_user (email): remove usuário (donos não podem ser removidos). [Flattened action: delete_user]

输入模式

{
  "type": "object",
  "properties": {
    "email": {
      "type": "string"
    },
    "data": {
      "type": "object",
      "propertyNames": {
        "type": "string"
      },
      "additionalProperties": {}
    },
    "account": {
      "type": "string"
    }
  },
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢show_version

Show the current MCP platform and adapter versions.

输入模式

{
  "type": "object",
  "properties": {},
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟡report_bug(message, context, conversation)

Report a bug, missing feature, or send feedback. Include the conversation array with recent messages for reproduction.

输入模式

{
  "type": "object",
  "properties": {
    "message": {
      "type": "string"
    },
    "context": {
      "default": "",
      "type": "string"
    },
    "conversation": {
      "default": "[]",
      "type": "string"
    }
  },
  "required": [
    "message"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢connect

Returns connection status and URLs. When all providers are connected, returns authenticated:true and empty pending[]. When credentials are missing, returns connect_url for the toolkit and per-install URLs.

输入模式

{
  "type": "object",
  "properties": {},
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢toolkit_info

Returns the current toolkit state: installed MCPs, their connection status, the accounts connected to each one, and how many catalog tools each exposes.

输入模式

{
  "type": "object",
  "properties": {},
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟡marketplace(action, query, mcp_id, limit, tier_slug, ...)

The official mcp.ai marketplace — the in-platform catalog of every MCP/tool, AND the way to run them. Covers capability requests like "find an MCP that does X", "consulta um CPF", "is there a tool for Y". Core flow: action=search discovers MCPs by intent → describe returns one MCP's full profile (every tool with its id + params, pricing, auth) so you pick the right tool_id → invoke RUNS that tool. KEY: invoke works even when the MCP is NOT installed — it runs the tool pontualmente (one-off), without adding the MCP to the toolkit and without bloating the tool list. If the MCP needs a credential/login, invoke returns a connect link; if it is paid and the wallet is empty, invoke returns a checkout/top-up link (the user opens it, then you retry). Use install only to make an MCP PERMANENT in the active toolkit (its tools then show up natively in future sessions); prefer invoke for a single/occasional use. list_tools lists what is callable right now. subscribe/cancel handle per-MCP billing; report_bug sends feedback; request_mcp asks us to build a NEW MCP when nothing fits. Search/describe flag installed_in_toolkit vs installed_in_workspace. Writes (install/uninstall/subscribe/cancel and the one-off install behind invoke) require workspace owner/admin. It also carries the mcp.ai PROMPT LIBRARY, which is about ready-made prompt TEXT rather than MCPs: search_prompts finds one, get_prompt returns its full text with {{variables}} filled, and publish_prompt saves a prompt and returns a shareable mcp.ai/p/<slug> link that opens without login.

输入模式

{
  "type": "object",
  "properties": {
    "action": {
      "default": "search",
      "type": "string",
      "enum": [
        "search",
        "describe",
        "install",
        "uninstall",
        "subscribe",
        "cancel",
        "resume",
        "report_bug",
        "request_mcp",
        "list_tools",
        "invoke",
        "search_prompts",
        "get_prompt",
        "publish_prompt"
      ]
    },
    "query": {
      "default": "",
      "type": "string"
    },
    "mcp_id": {
      "default": "",
      "type": "string"
    },
    "limit": {
      "default": 10,
      "type": "number"
    },
    "tier_slug": {
      "default": "",
      "type": "string"
    },
    "immediate": {
      "default": false,
      "type": "boolean"
    },
    "cancel_reason": {
      "type": "string",
      "enum": [
        "too_expensive",
        "missing_features",
        "switched_service",
        "unused",
        "customer_service",
        "too_complex",
        "low_quality",
        "other"
      ]
    },
    "cancel_comment": {
      "default": "",
      "type": "string"
    },
    "message": {
      "default": "",
      "type": "string"
    },
    "report_context": {
      "default": "",
      "type": "string"
    },
    "conversation": {
      "default": "[]",
      "type": "string"
    },
    "request_name": {
      "default": "",
      "type": "string"
    },
    "request_details": {
      "default": "",
      "type": "string"
    },
    "tool_id": {
      "default": "",
      "type": "string"
    },
    "arguments": {
      "default": "{}",
      "type": "string"
    },
    "prompt_slug": {
      "default": "",
      "type": "string"
    },
    "prompt_vars": {
      "default": "{}",
      "type": "string"
    },
    "prompt_category": {
      "default": "",
      "type": "string"
    },
    "prompt_tool": {
      "default": "",
      "type": "string"
    },
    "prompt_title": {
      "default": "",
      "type": "string"
    },
    "prompt_description": {
      "default": "",
      "type": "string"
    },
    "prompt_body": {
      "default": "",
      "type": "string"
    },
    "prompt_targets": {
      "default": [],
      "type": "array",
      "items": {
        "type": "string",
        "enum": [
          "claude",
          "chatgpt",
          "cursor",
          "lovable"
        ]
      }
    }
  },
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟡authenticate(token)

MCP.AI for IDE agents (Cursor, etc.): log in in the browser, copy the access token. Best: add it to this server's config as a header `Authorization: Bearer <token>` for a permanent, non-expiring connection. Or paste it here for a session-only login: call with { token: "<jwt>" } after the user pastes, or with no args to get the link.

输入模式

{
  "type": "object",
  "properties": {
    "token": {
      "type": "string"
    }
  },
  "$schema": "http://json-schema.org/draft-07/schema#"
}

社区

评价此服务器

证据

最近观测

已验证未记录版本35 个工具
已验证未记录版本35 个工具