Skip to main content

Assinafy

io.github.assinafy/mcp-serverVersion 3.2.0

Send documents for legally valid e-signature in Brazil, track signers and download signed files.

Status

Responds477 msAnswered our handshake without sign-in.

Registry data may be out of date

We could not refresh it, so this page shows the last copy.
Last checked
Nov 14, 2026, 14:45 UTC
Latency
477 ms
Remotes responding
1 of 1
Sign-in
No sign-in
Hosting
Hosted outside the EU (detected)
Registry data as of
Nov 14, 2026, 22:14 UTC

Data from the official MCP Registry, checked by run.zero. How we check

Connect

Streamable HTTP
https://mcp.assinafy.com.br/mcpResponds477 ms
No sign-in

Claude Code

claude mcp add --transport http mcp-server https://mcp.assinafy.com.br/mcp

Claude Desktop and claude.ai

Settings > Connectors > Add custom connector
Name: mcp-server
Remote MCP server URL: https://mcp.assinafy.com.br/mcp

Cursor

{
  "mcpServers": {
    "mcp-server": {
      "url": "https://mcp.assinafy.com.br/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"mcp-server","type":"http","url":"https://mcp.assinafy.com.br/mcp"}'

Built your own server? run.zero hosts MCP servers on European infrastructure.

Host your own MCP server on run.zero

Tools

29 tools

Tools of Assinafy
Read-only
Idempotent
Open world
assinafy_browse_contractsFind 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.NoYesYesNo
assinafy_create_assignmentRequest 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. Check with assinafy_get_document that no assignment exists first; this can consume credits.NoNoNoYes
assinafy_create_document_from_templateGenerate 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.NoNoNoYes
assinafy_create_signerCreate a signer in the workspace. Search with assinafy_list_signers first to avoid duplicates. Sends no invitation.NoNoNoNo
assinafy_delete_documentDelete a document only when the user's instruction explicitly authorizes deletion. Inspect its current state first; Assinafy enforces which documents may be deleted.YesNoNoNo
assinafy_download_documentDownload 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.NoYesYesNo
assinafy_download_document_pageDownload the rendered image of a specific document page. Use a page_id returned by assinafy_get_document. Returns base64.NoYesYesNo
assinafy_get_documentInspect 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.NoYesYesNo
assinafy_get_fieldRetrieve a single field definition.NoYesYesNo
assinafy_get_signerRetrieve a signer's information.NoYesYesNo
assinafy_get_templateGet one saved template with its roles and field placements.NoYesYesNo
assinafy_list_document_activitiesList 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.NoYesYesNo
assinafy_list_documentsSearch workspace documents by name or status, with pagination. Use it to find a document the user names before inspecting or following up on it.NoYesYesNo
assinafy_list_fieldsList 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.NoYesYesNo
assinafy_list_signersList the signers of a workspace. Use it to resolve a recipient to a signer ID; ask the user about ambiguous matches before sending.NoYesYesNo
assinafy_list_templatesList saved templates with their signer roles, pages and field placements (field_id). Template authoring is done in Assinafy.NoYesYesNo
assinafy_list_whatsapp_notificationsList 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.NoYesYesNo
assinafy_place_fieldsOpen 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.NoYesYesNo
assinafy_rename_documentUpdate 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.YesNoNoNo
assinafy_resend_notificationSend 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.NoNoNoYes
assinafy_review_signature_requestPreview 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.NoYesYesNo
assinafy_send_pdf_for_signatureUpload 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.NoNoNoYes
assinafy_set_assignment_expirationSet 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.YesNoNoNo
assinafy_show_documentShow 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.NoYesYesNo
assinafy_update_contractManage 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.YesNoNoYes
assinafy_update_signerUpdate 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.YesNoNoNo
assinafy_upload_documentUpload 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.NoNoNoNo
assinafy_validate_fieldsValidate 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.NoYesYesNo
assinafy_verify_documentVerify 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.NoYesYesNo

Details

Registry status
Active
Published
Oct 13, 2026
Updated
Oct 13, 2026
Categories (suggested)
DocumentsSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
GDPR
Not declared

Are you the operator? Claim this listing