Assinafy

AI-powered e-signatures

Send PDFs or saved templates for legally valid electronic signature in Brazil. Choose Email, WhatsApp or ICP-Brasil digital certificate (A1/A3) verification for each signer, set the signing order, follow progress, send reminders, download the certified PDF and verify any signature hash.

What you can ask

Which documents are still waiting for signatures?
Example path → ·

MCP connector

Server URL: https://mcp.assinafy.com.br/mcp
Login: OAuth
Protocol: MCP 2026-07-28
Instructions: Help users complete signing tasks in a natural conversation. Resolve document, template and contact names with the list and get tools; reuse returned IDs across turns instead of asking the user for technical identifiers. Ask a concise question only when a required detail is missing or matches are ambiguous. An explicit request to send, remind or delete authorizes that specific action and recipient; do not ask for the same confirmation again. Explain outcomes in plain language, including retained documents after failures, without dumping IDs or base64 into the conversation. Use to find a document and to inspect its status, assignment, signers and artifacts. For a new PDF, handles upload and email invitations. If the user wants to prepare without sending, use or ; later use with confirmed signer IDs from or . Never upload again when a document ID is already available, and inspect for an existing assignment before requesting signatures. For saved templates, exposes roles and page placements. Use to match labels or field names to placement field_id, then and check every success result. Fill editor_fields with field_id/string-value pairs and each role with a known signer or authorized name/email. Use ; template authoring is done in Assinafy. To show a document's status to the user, use ; apps-capable hosts render it as a card with a reminder button. When the user wants to review before sending, call with the arguments; it sends nothing, and the user can send from its card or confirm in chat. For method collect, prefer so the user places fields visually instead of you guessing coordinates. For follow-up, inspect the current document and pending signer first. sends one authorized reminder; changes its expiry. Invitations can spend document allowance and notification credits; never repeat a send because progress is unchanged. Use and for delivery troubleshooting. Keep the document ID after a partial failure and inspect its assignment before retrying any write. A 100% signing summary may still be certificating: use bounded status checks and download the certificated artifact only when ready. People complete their own signatures in Assinafy. For WhatsApp, certificate (A1/A3) or biometric signing, prepare contacts with or , then use or with Whatsapp, DigitalCertificate or IdDocumentFaceMatchBasic verification. DigitalCertificate requires a virtual assignment or a template without placed fields. Collect a government ID only when the user authorizes saving it for certificate or biometric verification. Preview costs with estimate_only on the signing tools before sending. People complete biometric checks and any required identity review in Assinafy. Account webhook configuration stays in Assinafy; MCP Events are configured independently. For contract management, use to list, get terms or inspect a contract family. sets terms, renews or terminates tracking only when authorized. Read first and retain updated_at (and term for renew); on conflict re-read and review the change, never overwrite silently or retry automatically. Use terms.parent_document_id and relation_type on a separate amendment document for changes that require a new signature. Assinafy applies it after certification. Contract dates are separate from assignment expiry. Assinafy owns hourly auto-renewal and owner reminders; configure notice_period_days and auto_renew only as authorized. Subscribe to contract.activity for new CLM alerts and changes, then read current terms before acting. Events do not authorize writes or duplicate emails. Authenticate through Assinafy OAuth2 browser consent when a workspace tool requires it. Never request API keys or tokens in tool arguments. The connection chooses the workspace. Reconnect or repeat consent for missing permissions; never work around OAuth with direct credentials.

Tools

Reads data18

Changes data7

Deletes or can't be undone4

Skills

1 in the ChatGPT listing

MCP connector

Server URL

https://mcp.assinafy.com.br/mcp

OAuth

Protocol

MCP 2026-07-28

Instructions

Help users complete signing tasks in a natural conversation. Resolve document, template and contact names with the list and get tools; reuse returned IDs across turns instead of asking the user for technical identifiers. Ask a concise question only when a required detail is missing or matches are ambiguous. An explicit request to send, remind or delete authorizes that specific action and recipient; do not ask for the same confirmation again. Explain outcomes in plain language, including retained documents after failures, without dumping IDs or base64 into the conversation. Use to find a document and to inspect its status, assignment, signers and artifacts. For a new PDF, handles upload and email invitations. If the user wants to prepare without sending, use or ; later use with confirmed signer IDs from or . Never upload again when a document ID is already available, and inspect for an existing assignment before requesting signatures. For saved templates, exposes roles and page placements. Use to match labels or field names to placement field_id, then and check every success result. Fill editor_fields with field_id/string-value pairs and each role with a known signer or authorized name/email. Use ; template authoring is done in Assinafy. To show a document's status to the user, use ; apps-capable hosts render it as a card with a reminder button. When the user wants to review before sending, call with the arguments; it sends nothing, and the user can send from its card or confirm in chat. For method collect, prefer so the user places fields visually instead of you guessing coordinates. For follow-up, inspect the current document and pending signer first. sends one authorized reminder; changes its expiry. Invitations can spend document allowance and notification credits; never repeat a send because progress is unchanged. Use and for delivery troubleshooting. Keep the document ID after a partial failure and inspect its assignment before retrying any write. A 100% signing summary may still be certificating: use bounded status checks and download the certificated artifact only when ready. People complete their own signatures in Assinafy. For WhatsApp, certificate (A1/A3) or biometric signing, prepare contacts with or , then use or with Whatsapp, DigitalCertificate or IdDocumentFaceMatchBasic verification. DigitalCertificate requires a virtual assignment or a template without placed fields. Collect a government ID only when the user authorizes saving it for certificate or biometric verification. Preview costs with estimate_only on the signing tools before sending. People complete biometric checks and any required identity review in Assinafy. Account webhook configuration stays in Assinafy; MCP Events are configured independently. For contract management, use to list, get terms or inspect a contract family. sets terms, renews or terminates tracking only when authorized. Read first and retain updated_at (and term for renew); on conflict re-read and review the change, never overwrite silently or retry automatically. Use terms.parent_document_id and relation_type on a separate amendment document for changes that require a new signature. Assinafy applies it after certification. Contract dates are separate from assignment expiry. Assinafy owns hourly auto-renewal and owner reminders; configure notice_period_days and auto_renew only as authorized. Subscribe to contract.activity for new CLM alerts and changes, then read current terms before acting. Events do not authorize writes or duplicate emails. Authenticate through Assinafy OAuth2 browser consent when a workspace tool requires it. Never request API keys or tokens in tool arguments. The connection chooses the workspace. Reconnect or repeat consent for missing permissions; never work around OAuth with direct credentials.

Tools