# Identik Firma Electrónica [Health: Active]

**Category:** 🤝 Agreements & Coordination  
**Repository:** https://github.com/pbullian/identik-mcp  
**GitHub Stars:** 1  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/identik-firma-electr-nica

## Description
Firma electrónica argentina (Ley 25.506): enviar documentos a firmar, seguir estado y validar.

## Tools
Capabilities this server exposes over MCP:

- **listar_plantillas** — Lista las plantillas del equipo con sus `id` y firmantes. Las plantillas se arman en la interfaz web; desde acá se usan para generar documentos.
- **listar_documentos** — Lista los documentos del equipo con su estado (DRAFT, PENDING, COMPLETED, REJECTED).
- **obtener_documento** — Devuelve un documento por su `id` numérico: estado, `meta` (`requireBiometricId`, `requireWhatsappOtp`, idioma), firmantes (con `signingStatus`, `signingUrl` y la identidad esperada para la biometría: `idDocumentNumber`, `firstName`, `lastName`), campos y `envelopeId`.
- **crear_documento_desde_plantilla** — Genera un documento de firma electrónica a partir de una plantilla. Flujo: listar_plantillas → esta herramienta → enviar_documento. Devuelve el `documentId` y el `signingUrl` de cada firmante. IMPORTANTE: el documento queda en borrador (no consume crédito) hasta que lo envíes con enviar_documento.
- **enviar_documento** — Pone el documento en firma. ACÁ se consume el crédito del documento; sin este paso queda en borrador. Por defecto manda el email de invitación a cada firmante. Con `enviar_email: false` no manda las invitaciones iniciales por email ni los avisos iniciales por WhatsApp/SMS. El documento igual queda en firma y vos distribuís los signingUrl obtenidos con obtener_documento. Los emails de finalización conservan su configuración salvo que indiques enviar_email_finalizacion. Esa opción controla el envío del PDF y la constancia al completar, según la plataforma; no cambia otros emails de avance o recordatorios.
- **reenviar_invitacion** — Reenvía el email a firmantes pendientes respetando el orden de firma. Si alguno de los elegidos todavía espera su turno, se rechaza todo el pedido sin enviar correos. Explicá el motivo y no reintentes automáticamente.
- **descargar_documento_firmado** — Devuelve una URL firmada de descarga del PDF firmado (con la constancia integrada al final). Pasado el plazo de resguardo responde 410.
- **descargar_constancia** — Devuelve una URL temporal (1 hora, sin token) para bajar la constancia de firma como PDF aparte: firmantes, fechas, IP, dispositivo y hash SHA-256 del PDF firmado. En esta plataforma la constancia ya va dentro del PDF firmado; esto es para tenerla como archivo separado. Sólo documentos COMPLETED.
- **traza_auditoria** — Devuelve la traza de auditoría completa del documento en JSON (creación, envío, apertura, firmas, con fecha/IP/dispositivo). Resuelve el envelopeId automáticamente a partir del id numérico.
- **validar_pdf** — Verifica criptográficamente las firmas de un PDF (de Identik o firma digital argentina): integridad, cadena, sello de tiempo RFC-3161, y si es un documento de PRUEBA. Equivalente autenticado del validador público /validar.
- **estado_cuenta** — Saldos de la cuenta: créditos de documentos y, si la plataforma los usa, verificación de identidad biométrica, WhatsApp y SMS.

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: high). Install path detected from listing signals. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "identik-firma-electr-nica": {
    "url": "https://electronica.identik.me/api/mcp"
  }
}
```

## Documentation

## 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.

_Full upstream README: https://allmcps.com/mcp/identik-firma-electr-nica/readme_