Assinafy MCP Server
Server Details
Send documents for legally valid e-signature in Brazil, track signers and status, and download signed files with Assinafy, a Brazilian e-signature platform with a free API plan (www.assinafy.com.br).
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 29 tools
Most tools map cleanly to a resource+action, but several pairs genuinely overlap: get_document vs show_document both read one known document, browse_contracts vs list_documents both search documents, and send_pdf_for_signature duplicates upload_document + create_assignment. The descriptions do a good job cross-referencing and steering (review before send, resolve IDs first), which keeps it usable, but an agent must read carefully to pick the right send path among create_assignment, create_document_from_template, place_fields, and send_pdf_for_signature.
Every tool is prefixed with assinafy_ and follows a strict snake_case verb_noun pattern: list_*, get_*, create_*, update_*, delete_*, download_*, validate_*, verify_*. The handful of less-common verbs (browse_contracts, show_document, resend_notification, place_fields) are still verb_noun and unambiguous in form.
29 tools is heavy and includes convenience composites that could be expressed in terms of primitives (send_pdf_for_signature = upload + assign, show_document = get_document presentation, review_signature_request = dry-run of create_assignment). The domain is genuinely broad (documents, signers, templates, fields, assignments, contracts, notifications), so most tools earn a place, but the surface is at the upper edge of what an agent can hold in context.
The lifecycle is well covered end to end: upload → assign → place/collect → remind → expire → download certificated artifacts → verify, plus signers, templates, fields, activities, and a CLM contract layer. Gaps are modest but real: no explicit cancel/void of an in-flight assignment (only document deletion or expiration), no delete/merge for signers, and no document metadata update beyond rename.
Publisher details
- Operator
- Assinafy · Publisher source
- Operator website
- https://www.assinafy.com.br
- Vendor relationship
- First-party · Publisher source
- Documentation
- https://api.assinafy.com.br/v1/docs · Publisher source
- Privacy policy
- Not provided
- Trust center
- Not available
- Restrictions
- Not available
Available Tools
29 toolsassinafy_browse_contractsBrowse contractsARead-onlyIdempotentInspect
Find contracts with action list and filters, read terms or an amendment with get, or read the root and its amendments with related. Resolve names before writes. Apps-capable hosts show a contract browser; other clients receive the same JSON. Contract lifecycle dates are separate from signing deadlines. Reads remain available when the tracking plan lapses.
Inputs: action (required), page, sort, expand, +11 more.
assinafy_create_assignmentCreate assignment (request signatures)AInspect
Request signatures on a document. Use method: virtual to sign without input fields, or method: collect to place input fields on specific pages. DigitalCertificate signers require method: virtual; other methods fail with code digital_certificate_requires_virtual.
For virtual, the document may be in uploaded, metadata_processing or metadata_ready; it is promoted to pending_signature automatically once metadata processing completes. For collect, the document must be in metadata_ready (fields reference specific pages).
step controls signing order: signers sharing a step sign in parallel, and the next step is notified only after the previous step completes. If supplied, every signer must supply it and values must be contiguous starting at 1. Obtain signer IDs from assinafy_list_signers or assinafy_create_signer and page IDs from assinafy_get_document. This sends signing invitations. Verification settings select a method only. This tool does not accept biometric data; never request or submit it in chat or tool arguments. Any biometric verification occurs directly between the signer and Assinafy on its signing page, with the signer's consent. Check with assinafy_get_document that no assignment exists first; this can consume credits.
Inputs: method (required), signers (required), document_id (required), entries, +5 more.
assinafy_create_document_from_templateSend a template for signatureAInspect
Generate a document from a saved template and invite each Signer role, with optional CopyReceiver roles, by signer ID or full name and email. Editor roles use only editor_fields. Find roles with assinafy_list_templates and validate editor_fields values with assinafy_validate_fields first. DigitalCertificate signers require a template without placed signer fields. This sends invitations and can consume credits. Verification settings select a method only. This tool does not accept biometric data; never request or submit it in chat or tool arguments. Any biometric verification occurs directly between the signer and Assinafy on its signing page, with the signer's consent.
Inputs: signers (required), template_id (required), name, tags, +6 more.
assinafy_create_signerCreate signerAInspect
Create a signer in the workspace. Search with assinafy_list_signers first to avoid duplicates. Sends no invitation.
Inputs: full_name (required), email, account_id, whatsapp_phone_number.
assinafy_delete_documentDelete a documentADestructiveInspect
Delete a document only when the user's instruction explicitly authorizes deletion. Inspect its current state first; Assinafy enforces which documents may be deleted.
Inputs: document_id (required).
assinafy_download_documentDownload a documentARead-onlyIdempotentInspect
Download a document artifact as base64: original (default), certificated, certificate-page, pades or bundle. Download the signed PDF only when the document is certificated and the artifact is listed.
Inputs: document_id (required), artifact.
assinafy_download_document_pageDownload document pageARead-onlyIdempotentInspect
Download the rendered image of a specific document page. Use a page_id returned by assinafy_get_document. Returns base64.
Inputs: page_id (required), document_id (required).
assinafy_get_documentGet a documentARead-onlyIdempotentInspect
Inspect one known document: status, assignment, signers with their progress, pages and available artifacts. Read it before retrying a send or following up. 100% signed does not mean certification is finished; the signed PDF is ready at status certificated.
Inputs: document_id (required).
assinafy_get_fieldGet fieldCRead-onlyIdempotentInspect
Retrieve a single field definition.
Inputs: field_id (required), account_id.
assinafy_get_signerGet signerCRead-onlyIdempotentInspect
Retrieve a signer's information.
Inputs: signer_id (required), account_id.
assinafy_get_templateGet a templateBRead-onlyIdempotentInspect
Get one saved template with its roles and field placements.
Inputs: template_id (required), account_id.
assinafy_list_document_activitiesList document activitiesARead-onlyIdempotentInspect
List the activities recorded for a document. Each entry carries an event-specific payload snapshot (keys vary per event) and the request origin (ip, user-agent). Use it to explain what happened to a document and when.
Inputs: document_id (required), page, sort, per_page.
assinafy_list_documentsList documentsARead-onlyIdempotentInspect
Search workspace documents by name or status, with pagination. Use it to find a document the user names before inspecting or following up on it.
Inputs: page, sort, tags, method, +4 more.
assinafy_list_fieldsList fieldsARead-onlyIdempotentInspect
List the field definitions of a workspace.
When include_standard is enabled, records of type signature, initial and signatureDate are also returned. Match definitions to template placement field_id and ask about ambiguous names.
Inputs: account_id, include_inactive, include_standard.
assinafy_list_signersList signersARead-onlyIdempotentInspect
List the signers of a workspace. Use it to resolve a recipient to a signer ID; ask the user about ambiguous matches before sending.
Inputs: page, search, per_page, account_id.
assinafy_list_templatesList templatesARead-onlyIdempotentInspect
List saved templates with their signer roles, pages and field placements (field_id). Template authoring is done in Assinafy.
Inputs: page, search, per_page, account_id.
assinafy_list_whatsapp_notificationsList WhatsApp notificationsARead-onlyIdempotentInspect
List all WhatsApp notification messages sent for an assignment. The response includes the rendered template text split into header, body and buttons — exactly what the signer would see. In sandbox/stage, WhatsApp messages are simulated (no real delivery) and button URLs include access/verification codes you can use to simulate the signing flow. Treat returned signing links and verification codes as sensitive; never use them to sign for another person. Use it to troubleshoot WhatsApp delivery for one assignment.
Inputs: document_id (required), assignment_id (required).
assinafy_place_fieldsPlace signature fieldsARead-onlyIdempotentInspect
Open a visual editor to place signature, initials, date and input fields on a metadata_ready document, then send it with method collect. Takes the assinafy_create_assignment arguments except method and entries. Sends nothing by itself: in apps-capable hosts the user places fields and presses Send; other clients get page sizes and field IDs as text to build entries. Verification settings select a method only. This tool does not accept biometric data; never request or submit it in chat or tool arguments. Any biometric verification occurs directly between the signer and Assinafy on its signing page, with the signer's consent.
Inputs: signers (required), document_id (required), message, expires_at, +2 more.
assinafy_rename_documentRename documentADestructiveInspect
Update a document's name. Only allowed before any assignment is created (i.e. while the document is in uploaded or metadata_ready status and has no signers yet); once the signature process has started or the document is certificated, the name is locked. The name is normalized: diacritics are removed and unsupported characters are replaced with dashes.
Inputs: name (required), document_id (required).
assinafy_resend_notificationRemind a signerAInspect
Send one reminder to a pending signer in the assignment's active step, after confirming with assinafy_get_document that they have not signed. May consume notification credits; never repeat a reminder only because progress is unchanged.
Inputs: signer_id (required), document_id (required), assignment_id (required), estimate_only.
assinafy_review_signature_requestReview a signature requestARead-onlyIdempotentInspect
Preview an assinafy_create_assignment call without sending anything: same arguments, checked against the document and signers. Use it when the user wants to review before sending. Apps-capable hosts render a card whose Send button performs the request; other clients get the summary as text, and the request is sent only after the user confirms. Verification settings select a method only. This tool does not accept biometric data; never request or submit it in chat or tool arguments. Any biometric verification occurs directly between the signer and Assinafy on its signing page, with the signer's consent.
Inputs: method (required), signers (required), document_id (required), entries, +4 more.
assinafy_send_pdf_for_signatureSend a PDF for signatureAInspect
Upload a new PDF, wait for processing and invite signers by full name and email, using Email verification and notification. This sends invitations and uses plan allowance: use only recipients the user authorized. After a partial failure, inspect the retained document ID and continue with assinafy_create_assignment instead of uploading again.
Inputs: signers (required), file_name (required), file_base64 (required), message, +6 more.
assinafy_set_assignment_expirationChange the deadlineADestructiveInspect
Set an existing signature request deadline with an ISO 8601 date or date-time at least one hour in the future, or remove it with expires_at: null. A shorter deadline ends signing when it passes; Assinafy refuses expired or closed requests.
Inputs: expires_at (required), document_id (required), assignment_id (required).
assinafy_show_documentShow document statusARead-onlyIdempotentInspect
Show a status card for one known document: its status, who has signed, who is still pending and when it expires. Apps-capable hosts render it with a reminder button; other clients get the same summary as text. Resolve the document with assinafy_list_documents first.
Inputs: document_id (required).
assinafy_update_contractUpdate contract termsADestructiveInspect
Manage an existing document’s CLM record: set creates/patches terms or links a signed amendment; renew starts the next term; terminate closes tracking. Requires a tracking plan. Read first: include terms.updated_at for existing terms or links; renew requires the current term and updated_at, terminate requires updated_at. A conflict needs a fresh read and user review, never blind retries. Only supplied terms change; external_references replaces the list; null can clear values or unlink a pending amendment. Assinafy owns auto-renewal and owner reminders; changes can trigger lifecycle emails/webhooks. These actions do not sign, send or cancel the document itself. Use only for changes the user authorized.
Inputs: action (required), term, terms, value, +5 more.
assinafy_update_signerUpdate signerADestructiveInspect
Update a signer's information. Only supplied fields change; send null or an empty string to clear email or whatsapp_phone_number.
Verification integrity: email / whatsapp_phone_number cannot be changed while the signer has verified that channel on an in-flight (not yet certificated) document — the response is 400 naming the offending document(s). Already-certificated documents do not block updates. Changing a channel that has unverified in-flight requests rotates their access/verification codes (invalidating previously sent links/OTPs); use the resend endpoint to redeliver. full_name can always be updated.
Inputs: signer_id (required), email, full_name, account_id, +1 more.
assinafy_upload_documentUpload a documentAInspect
Upload a PDF without sending invitations and return its document ID. Use it when the user wants to prepare a document now and send it later with assinafy_create_assignment. Never upload again when a document ID is already known.
Inputs: file_name (required), file_base64 (required), account_id.
assinafy_validate_fieldsValidate multiple field valuesARead-onlyIdempotentInspect
Validate one or more input values against existing field definitions without creating a document or requesting signatures. Supply field/value pairs in values; the server sends the documented JSON array. Check each result's success before requesting signatures.
Inputs: values (required), account_id.
assinafy_verify_documentVerify a signed documentARead-onlyIdempotentInspect
Verify a signed document using its verification_code from assinafy_get_document or the signature hash printed on the signed document. Public lookup; requires no workspace connection and sends no credential upstream.
Inputs: hash (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Send documents for e-signature, track signing status, and download signed PDFs. No API key required.
ZapSign electronic document signing via the official API: create documents for signature (from PDF,
E-signature API: send documents for signature, track envelopes, get signed files.
Assinatura eletrônica no Brasil (ICP-Brasil): envie, assine e verifique com sua conta SignDocs.
Related MCP Servers
AlicenseNot gradedqualityBmaintenanceEnables connecting to a Brazilian digital signature platform to prepare and send documents, track signatures, send reminders, and download signed copies.4MIT- AlicenseAqualityBmaintenanceEnables AI clients to create and manage e-signature sessions, envelopes, documents, and webhooks through the SignDocs Brasil API.2495 npm1MIT
- AlicenseNot gradedqualityDmaintenanceE-signature for AI agents. One unauthenticated call returns a sandbox API key (no account, no browser), then the agent can send documents for signature, check status, and download the sealed PDF plus Certificate of Completion.3 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents and developers to create, send, and follow up on contracts for e-signature, manage signers and templates, retrieve signed PDFs and audit trails, and verify PDF signatures. It keeps signing and declining in the hands of each signer through personal links.1MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.