Identik Firma Electrónica

What Identik Firma Electrónica does

Identik Firma Electrónica connects an MCP-compatible client to Identik's hosted electronic-signature service for Argentina. It covers the document lifecycle from selecting a team template through sending a document for signature, checking signer progress, retrieving completed files, and reviewing audit evidence.

The service is based on electronic signatures under Ley 25.506, article 5. The signer completes authorization in Identik using an email link and the evidence collected by the platform. Optional biometric identity verification can be enabled with a national identity document and liveness check. The agent prepares and manages the workflow, but it does not replace the signer's consent or handle the signer's PIN or OTP.

How it works

The direct production endpoint is https://electronica.identik.me/api/mcp. A separate sandbox endpoint, https://sandbox-electronica.identik.me/api/mcp, uses its own accounts, data, credits, and database. Sandbox documents are explicitly marked as test documents and are not legally valid; PDF validation reports the test environment and rejects them as valid signatures.

Communication uses stateless Streamable HTTP and POST requests. Discovery methods such as initialize and tools/list are public, while document and account operations require an Identik team API token in the Authorization: Bearer ... header. Tokens can be requested from Identik or created in the account under API Tokens.

A typical workflow is to list templates, create a document from one, and then send it. Creation leaves the document in DRAFT and does not consume a document credit. Sending changes it to the signing flow and consumes the credit. By default, Identik emails invitations to signers; disabling the initial email leaves the document active so the caller can distribute each signing URL itself.

Tools and capabilities

The Spanish-named tools provide the following operations:

• List team templates and their signer definitions.
• List documents with DRAFT, PENDING, COMPLETED, or REJECTED status.
• Retrieve document metadata, signers, signing URLs, fields, and envelope information.
• Create documents from existing templates and return signer URLs.
• Send documents for signature, with control over initial and completion emails.
• Resend invitations to pending signers while enforcing signing order.
• Retrieve a signed PDF or a separate, temporary audit certificate PDF.
• Return the complete audit trail, including events, dates, IP addresses, and devices.
• Cryptographically validate Identik or Argentine digital-signature PDFs, including integrity, certificate chain, RFC 3161 timestamp, and test-environment status.
• Check available document credits and applicable biometric, WhatsApp, or SMS verification balances.

The signed PDF includes the audit certificate at the end. The separate certificate download is limited to completed documents and produces a temporary URL valid for one hour. Signed-document downloads can return HTTP 410 after the platform's retention period.

Limitations and notes

Templates are created in Identik's web interface; the MCP uses them but does not build them. Sending is the point at which a document credit is consumed, so an agent should keep drafts separate from documents that are ready for signature.

Invitation resends follow signing order. If any selected signer is still waiting for an earlier signer, the entire resend request is rejected; the caller should explain the reason rather than retry automatically.

The repository describes connection manifests and documentation for Identik's hosted MCP services rather than the product implementation. Identik also offers OAuth connectors for OpenAI and Claude, with separate authorization flows. Claude can use the dedicated connector as a custom connector in Claude web, Desktop, or Cowork, and the related Claude Code plugin is installed through its marketplace commands.