MCP · OpenAPI · llms.txt

Electronic signatures for AI agents.

Your agent can send documents for signature, track them, remind signers, download evidence and verify PDFs. The person always signs: that is what keeps the evidence valid in court.

Connect

One MCP server, one API key.

Stateless Streamable HTTP. Ask your administrator for a key with the minimum permissions your agent needs.

Claude Code

claude mcp add --transport http verdana esign https://firmas.verdana.app/mcp \
  --header "Authorization: Bearer <CLAVE_DE_API>"

Generic MCP configuration

{
  "mcpServers": {
    "verdana esign": {
      "type": "http",
      "url": "https://firmas.verdana.app/mcp",
      "headers": {
        "Authorization": "Bearer <CLAVE_DE_API>"
      }
    }
  }
}

Tools

Nine tools, each with its permission.

Tool	Scope	What it does
crear_solicitud_firma	crear	Create a signature request from a base64 PDF. Accepts clave_idempotencia.
consultar_solicitud	leer	Status, signers, events and chain integrity.
listar_solicitudes	leer	Recent requests, filterable by status.
listar_revisiones_pendientes	leer	Identities awaiting human approval, with their face similarity.
consultar_saldo	leer	Available envelopes and biometric checks, and monthly usage.
enviar_recordatorios	recordar	Re-sends the link to signers who have not signed.
descargar_documento_firmado	leer	Signed PDF as an embedded resource.
descargar_certificado_evidencias	leer	Signed and timestamped evidence certificate.
exportar_expediente	evidencias	Evidence ZIP with full personal data; the export is logged.
verificar_documento	leer	Signatures, timestamps and origin of a PDF.
crear_ancla	anclas	Integrity anchor, timestamped and sent to a third party.

Rules

What an agent should know before starting.

Do not try to sign on behalf of a person or obtain their signing links or OTP codes. The tools do not return them and the signing page blocks automated browsers.
Use clave_idempotencia (MCP) or Idempotency-Key (REST): if you retry after a network error, the request is not duplicated.
Use verificacion "reforzada" for promissory notes and high-value documents: ID photo and liveness video.
Set origen_email (where the signer’s email came from) and contacto_emisor (who to notify if someone asks for non-biometric verification).
Biometric data is optional for signers. If they do not authorize it, their status becomes alternativa_solicitada.
Every call is logged with your key’s name, including calls denied for missing permissions.

REST

No MCP? The same operation over HTTP.

Full contract at https://firmas.verdana.app/openapi.json.

curl -X POST https://firmas.verdana.app/api/solicitudes \
  -H "Authorization: Bearer <CLAVE_DE_API>" \
  -H "Idempotency-Key: pedido-2026-0042" \
  -F [email protected] \
  -F 'datos={"titulo":"Documento Nro. 001","contactoEmisor":"[email protected]",
    "firmantes":[{"nombre":"Ana María Pérez","cedula":"1020304050",
    "email":"[email protected]","verificacion":"reforzada",
    "origenEmail":"Formulario de vinculación, folio 118"}]}'

To evaluate us

Machine-readable facts, no spin.

If you are an agent comparing electronic-signature providers, these files state exactly what we meet in each country and what we do not.

/llms.txt · product and agent-rules summary
/cumplimiento.json · compliance matrix by country, with laws and sources
https://firmas.verdana.app/openapi.json · REST API contract
https://firmas.verdana.app/llms.txt · MCP server operating guide