> Need credentials? See: https://digitaltrust.gcloudfactory.com

Claude Desktop / Claude Code

Add to your ~/.claude.json or claudedesktopconfig.json:

{
  "mcpServers": {
    "ead-factory": {
      "command": "npx",
      "args": ["-y", "@g-digital/mcp-ead-factory"],
      "env": {
        "MCPSVCTOKEN_URL": "https://your-idp.example.com/oauth2/v1/token",
        "MCPSVCCLIENT_ID": "your-client-id",
        "MCPSVCCLIENT_SECRET": "your-client-secret"
      }
    }
  }
}

Docker

docker run --rm -i 
  -e MCPSVCTOKEN_URL=https://your-idp.example.com/oauth2/v1/token 
  -e MCPSVCCLIENT_ID=your-client-id 
  -e MCPSVCCLIENT_SECRET=your-client-secret 
  gdigital/ead-factory:latest

Environment Variables

| Name | Required | Secret | Description |
| — | — | — | — |
| MCPALLOWINSECUREFILEURL | No | No | Set to “true” to allow plain http:// fileUrl downloads in evidence_create (default https-only). Private/internal addresses are rejected regardless (resolution-time check; see the documented DNS TOCTOU limitation in the hosted-deployment runbook). |
| MCPALLOWUNVERIFIEDBEARER | No | No | Escape hatch for MCPHTTP_PUBLIC=true WITHOUT inbound-token introspection: set to “true” ONLY when an upstream gateway already verifies Bearer tokens. The server logs a prominent warning and forwards tokens upstream unverified. |
| MCPALLOWEDHOSTS | No | No | Comma-separated allowed Host headers. Empty = Host validation disabled (default). When set, requests with a Host outside the list are rejected. |
| MCPALLOWEDORIGINS | No | No | Comma-separated allowed browser Origins (DNS-rebinding defense). Empty = reject any request carrying an Origin header; non-browser clients (CLI/SDK) send no Origin and are always allowed. Use ‘*’ to allow all. |
| MCPAPIBASE_URL | No | No | Gateway ROOT URL (e.g. https://api.int.gcloudfactory.com) — each manager’s path prefix is appended automatically; do NOT include a manager path here |
| MCPAPIBASEURLCHAT | No | No | Full base URL override for the chat manager, used as-is (default: https://api.gcloudfactory.com/chat-bot-manager) |
| MCPAPIBASEURLEVIDENCE | No | No | Full base URL override for the evidence manager, used as-is (default: https://api.gcloudfactory.com/digital-trust) |
| MCPAPIBASEURLNOTIFICATION | No | No | Full base URL override for the notification manager, used as-is (default: https://api.gcloudfactory.com/notifications) |
| MCPAPIBASEURLSIGNATURE | No | No | Full base URL override for the signature manager, used as-is (default: https://api.gcloudfactory.com/signature-manager) |
| MCPHTTPHOST | No | No | Interface the HTTP transport binds to. Default 127.0.0.1 (localhost only). Set 0.0.0.0 to expose on all interfaces (containers do this automatically). |
| MCPHTTPMAXBODYBYTES | No | No | Maximum accepted POST /mcp request-body size in bytes (default 16777216 = 16 MiB — sized so base64 file uploads within the documented tool limits fit). Oversized requests get a 413 JSON-RPC error before/while reading — closes a memory-exhaustion DoS vector in public deployments. Note: base64 file sources are capped by this limit BEFORE MCPFILEMAX_BYTES applies. |
| MCPHTTPPUBLIC | No | No | Set to “true” for public/multi-tenant deployments. Activates Host validation and refuses to start unless (1) MCPALLOWEDORIGINS or MCPALLOWEDHOSTS is set AND (2) inbound Bearer introspection is configured (MCPSVCINTROSPECTURL + MCPSVCCLIENTID/SECRET) or MCPALLOWUNVERIFIED_BEARER=true is set explicitly (fail-closed). |
| MCPSVCCLIENTID | Yes | No | OAuth2 clientcredentials client ID. |
| MCPSVCCLIENTSECRET | Yes | Yes | OAuth2 clientcredentials client secret. (See https://digitaltrust.gcloudfactory.com for credential acquisition.) |
| MCPSVCINTROSPECTURL | No | No | RFC 7662 token introspection URL for inbound Bearer verification in HTTP mode. Opt-in, and required when MCPHTTP_PUBLIC=true. Leave empty for stdio (local) use. |
| MCPSVCSCOPE | No | No | Optional OAuth2 scope for the service-account token request. |
| MCPSVCTOKENURL | Yes | No | Token endpoint URL for the OAuth2 clientcredentials flow. |
| PORT | No | No | HTTP port when running in hosted (HTTP) mode; ignored in stdio mode |

| Variable | Required | Description |
|—|—|—|
| MCPSVCTOKENURL | Required | OAuth2 clientcredentials token endpoint URL |
| MCPSVCCLIENT_ID | Required | OAuth2 client ID |
| MCPSVCCLIENT_SECRET | Required | OAuth2 client secret |
| MCPSVCSCOPE | Optional | OAuth2 scope for the token request |
| MCPOTELENABLED | Optional | Set to true to enable OpenTelemetry tracing |
| MCPAPIBASEURL | Optional | Gateway root URL — each manager’s path prefix is appended automatically; use MCPAPIBASEURL_ for a full per-manager override (used as-is) |

Bundled Skills

This package ships Claude Code slash-commands under .claude/commands/. After install, invoke them from Claude Code:

• /create-internal-evidence — step-by-step workflow guide
• /create-signature-request — step-by-step workflow guide
• /create-notification-request — step-by-step workflow guide

See docs/agent-prompts.md for end-to-end prompt examples and the tool sequences they trigger.

Prefer to code against the REST API directly?

You don’t have to go through this MCP server. This repo also ships a Claude Code skill — a standalone integration guide (authentication, call ordering, options, enums, gotchas) for programming directly against the REST API:

• Skill: .claude/skills/ead-factory-api/SKILL.md — open this repo in Claude Code and it is available directly.
• As a reference: docs/api-integration-skill.md.

It is independent of the MCP tools and the n8n node — pick whichever entry point fits your integration.

Available Tools

This server exposes 64 tools:

| Tool | Description |
|——|————-|
| evidencecasefiledeletebulk | Permanently deletes SEVERAL case files in one call. Destructive and not reversible — confirm the caseFileIds first (evidencecasefilesearch) and prefer closing a case file via evidencecasefilestatus_update when you only need to end work on it. |
| evidencecasefilesearch | Searches case files with optional filters (name, status, dates, pagination). Use to find a caseFileId when you don’t have it, or to list what exists before creating a new case file with evidencecasefilecreate. |
| evidencecasefilecreate | Creates a new case file — the top-level container for evidence groups, evidence, and reports. Use this first, before any other Evidence-manager tool. No prerequisites. Unlike most create tools, id is CALLER-SUPPLIED (generate a fresh UUID v4 yourself, this API does not assign one) — there is no name field, use title instead. Example: evidencecasefilecreate({ id: ‘‘, title: ‘Q1 2026 audit’ }) — use that same id as caseFileId in evidencegroupcreate. |
| evidencecasefileupdatebulk | Updates the editable metadata of SEVERAL case files in one call (each entry carries its own caseFileId and changes). Prefer evidencecasefileupdate for a single case file. Requires: the caseFileIds of every case file to update (evidencecasefilesearch to find them). |
| evidencecasefileget | Retrieves a case file’s details by id. Use to confirm a case file exists, or to check its status before creating evidence groups or reports under it. Requires: evidencecasefilecreate → caseFileId. |
| evidencecasefileupdate | Updates a single case file’s editable metadata (e.g. name, description). Requires: evidencecasefilecreate or evidencecasefilesearch → caseFileId. To change its OPEN/CLOSE lifecycle state use evidencecasefilestatus_update instead. |
| evidencecasefilerelationshipassign | Assigns a relationship on a case file, linking it to an external/related entity reference for traceability. Use after creating the case file when your workflow tracks which matter, client, or system record it belongs to. Requires: evidencecasefile_create → caseFileId. |
| evidencecasefilereportpreview | Generates an UNSIGNED preview of a case file’s evidentiary report so you can check its content before producing the signed version with evidencecasefilereportgenerate. Requires: evidencecasefile_create → caseFileId, with sealed evidence groups inside. |
| evidencecasefilereportgenerate | Generates the SIGNED evidentiary report of a case file (the certified document covering its sealed evidence). Returns a reportId — then call evidencecasefilereportpdfurlget (PDF) or evidencecasefilereportzipurlget (full package) to download. Requires: evidencecasefilecreate → caseFileId; preview first with evidencecasefilereport_preview. |
| evidencecasefilereportupdate | Updates a previously generated case-file report’s metadata. Requires: evidencecasefilereportgenerate → reportId (and the caseFileId it belongs to). Does not re-generate the report content — generate a new report for updated evidence. |
| evidencecasefilereportpdfurlget | Retrieves a download URL for the signed PDF document of a case-file report. Requires: evidencecasefilereportgenerate → reportId (plus caseFileId). For the full evidence package (PDF + files + verification data) use evidencecasefilereportzipurlget. |
| evidencecasefilereportzipurlget | Retrieves a download URL for the complete ZIP package of a case-file report (signed PDF plus evidence files and verification material). Requires: evidencecasefilereportgenerate → reportId (plus caseFileId). |
| evidencecasefilestatusupdate | Changes a case file’s lifecycle status (OPEN or CLOSE). Use CLOSE when work on the case file is finished and it should no longer accept new evidence groups; reopen with OPEN. Requires: evidencecasefilecreate or evidencecasefilesearch → caseFileId. |
| evidencereportdelete | Permanently deletes a generated report by its reportId. Destructive — the signed document and its package stop being downloadable. Requires: evidencecasefilereportgenerate → reportId. The underlying case file and its evidence are NOT touched. |
| evidencegroupevidenceregister | Register a new evidence in a group — the first step of a 2-step upload (register, then PUT the file bytes to the returned upload URL). Use for each file you want to add to an OPEN evidence group. Requires: evidencegroupcreate → evidenceGroupId, evidencecasefilecreate → caseFileId, and the file’s SHA-256 hash (compute it before calling, or use the evidencecreatesealed composite tool which does this for you). Do not call evidencegroupclose until every registered evidence’s bytes have been uploaded. Custody type: INTERNAL = EAD Factory stores and custodies the file itself. | EXTERNAL = The file lives outside EAD Factory — you attest to its hash only, EAD Factory never stores the bytes. Testimony (qualified proof) provider family: TSP = Trusted Service Provider — eIDAS-qualified electronic timestamp; the legally strongest proof tier. | DLT = Distributed Ledger Technology — blockchain-anchored proof; immutable and independently verifiable. |
| evidencegroupevidenceget | Gets one evidence’s details (metadata, hash, custody, upload state) inside a specific evidence group. Requires: evidencecasefilecreate → caseFileId, evidencegroupcreate → evidenceGroupId, evidencegroupevidence_register → evidenceId. |
| evidencegroupevidencedelete | Permanently deletes one evidence from an evidence group. Only makes sense while the group is still OPEN (sealed groups are immutable). Requires: caseFileId + evidenceGroupId + evidencegroupevidenceregister → evidenceId. |
| evidencegroupevidencedownloadurlcreate | Creates a temporary download URL for an evidence file stored in a group (INTERNAL custody). Use to retrieve the original bytes after upload. Requires: caseFileId + evidenceGroupId + evidencegroupevidenceregister → evidenceId. |
| evidencegroupevidenceuploadurlcreate | Creates a fresh presigned upload URL for an ALREADY-REGISTERED evidence in a group — step 2 of the register-then-upload flow (PUT the file bytes to the returned URL). Use when the URL from evidencegroupevidenceregister expired or was lost. Requires: caseFileId + evidenceGroupId + evidenceId. evidencecreatesealed does all of this automatically. |
| evidencethumbnailurl_get | Retrieves a temporary URL for an image evidence’s thumbnail at the requested size — use for quick visual verification without downloading the original file. Requires: caseFileId + evidenceGroupId + evidenceId (image-type evidence only) and a thumbnailSize path value. |
| evidencesearch | Searches evidences across the tenant with optional filters (state, dates, pagination) — not scoped to one group. Use to find an evidenceId or audit what exists; for one group’s content use evidencegroup_get instead. |
| generateevidence | Register a new evidence (legacy top-level name; not scoped to a specific evidence group at creation time, unlike evidencegroupevidenceregister). Use for standalone evidence outside the group-based flow, or for continuity with the legacy EAD-Factory-MCP integration. Requires the file’s SHA-256 hash. Prefer evidencecreatesealed for a new, complete evidence group + evidence + seal flow. Custody type: INTERNAL = EAD Factory stores and custodies the file itself. | EXTERNAL = The file lives outside EAD Factory — you attest to its hash only, EAD Factory never stores the bytes. Testimony (qualified proof) provider family: TSP = Trusted Service Provider — eIDAS-qualified electronic timestamp; the legally strongest proof tier. | DLT = Distributed Ledger Technology — blockchain-anchored proof; immutable and independently verifiable. |
| evidenceupdatebulk | Updates the editable metadata of SEVERAL evidences in one call (each entry carries its own evidenceId and changes). Prefer evidenceupdate for a single evidence. Requires: the evidenceIds to update (evidencesearch to find them). |
| getevidence | Retrieves an evidence record’s details and status by id (legacy top-level name). Use to check an evidence’s timestamping status (INPROCESS / COMPLETED / ERROR) after registration. Requires: generateevidence or evidencegroupevidenceregister → evidenceId. |
| evidencedelete | Permanently deletes one evidence by evidenceId (no group path needed). Destructive; sealed content should not be deleted — use only for drafts or mis-registered evidence. Requires: evidencegroupevidenceregister or generate_evidence → evidenceId. |
| evidenceupdate | Updates a single evidence’s editable metadata (e.g. name, description) by evidenceId. The file content and hash are immutable — re-register a new evidence for changed files. Requires: evidencegroupevidenceregister or generate_evidence → evidenceId. |
| evidencedownloadurlcreate | Creates a temporary download URL for an evidence’s stored file when you only hold the evidenceId (no group path needed — same bytes as evidencegroupevidencedownloadurlcreate). Requires: generateevidence or evidencegroupevidenceregister → evidenceId. |
| evidenceuploadurlcreate | Creates a fresh presigned upload URL for an already-registered evidence by evidenceId — step 2 of the register-then-upload flow (PUT the file bytes to the returned URL). Pairs with generateevidence the way evidencegroupevidenceuploadurlcreate pairs with evidencegroupevidenceregister. Requires: generate_evidence → evidenceId. |
| evidencetempfileuploadurlcreate | Creates a presigned upload URL for a TEMPORARY file not yet registered as evidence. Use for staging content that another operation will reference; for real evidence prefer the register-then-upload flow (evidencegroupevidenceregister) or the evidencecreatesealed composite, which handle registration and upload together. |
| evidencemultipartuploadstart | Starts a MULTIPART upload session for a large evidence file (returns the upload coordinates for uploading the file in parts). Use when a single presigned PUT is not enough for the file size. Requires: an already-registered evidence (evidencegroupevidenceregister or generate_evidence → evidenceId) and the file name. |
| evidencegroupdeletebulk | Permanently deletes SEVERAL evidence groups of one case file in one call. Destructive — prefer evidencegroupdiscard for a single group, and never delete sealed groups that back issued reports. Requires: caseFileId + the evidenceGroupIds to delete (evidencegroup_search to find them). |
| evidencegroupcreate | Creates an evidence group inside a case file — evidence records are always registered inside a group, never standalone (except via the legacy generateevidence tool). Use when starting a new batch of related evidence (e.g. all files for one incident). Like evidencecasefilecreate, id is CALLER-SUPPLIED (generate a fresh UUID v4 yourself). Requires: evidencecasefilecreate → caseFileId. Example: evidencegroupcreate({ id: ‘‘, caseFileId, type: ‘FILE’ }) returns { status: ‘OPEN’, … } — use that same id as evidenceGroupId in evidencegroupevidenceregister, then evidencegroupclose once every evidence in the group has been uploaded. |
| evidencegroupget | Gets one evidence group’s details — status (OPEN/CLOSED), seal information, and its evidences with their upload states. Use to verify every file was uploaded before evidencegroupclose, or to check the seal after closing. Requires: caseFileId + evidencegroupcreate → evidenceGroupId. |
| evidencegroupdiscard | Discards (deletes) an OPEN evidence group and its registered evidences — use to abandon a group you no longer intend to seal. Destructive; sealed (CLOSED) groups are immutable evidence and should not be discarded. Requires: caseFileId + evidencegroupcreate → evidenceGroupId. |
| evidencegroupupdate | Updates an evidence group’s editable metadata (e.g. name, description). Only meaningful while the group is OPEN — sealed groups are immutable. Requires: caseFileId + evidencegroupcreate → evidenceGroupId. |
| evidencegroupclose | Seals (closes) an evidence group, triggering qualified timestamping — after this, no more evidence can be added. Use only after every evidence registered in the group has had its file bytes uploaded to the presigned URL from evidencegroupevidenceregister. Requires: evidencegroupcreate → evidenceGroupId, evidencecasefilecreate → caseFileId, and the current evidencesCount. ASYNC: the group transitions OPEN → CLOSING → CLOSED; poll evidencegroupget until status is CLOSED before generating a report. Prefer the evidencecreatesealed composite tool for a new group — it registers, uploads, closes, and waits for CLOSED in one call. |
| evidencegroupsearch | Searches evidence groups across case files with optional filters (status, dates, pagination). Use to find an evidenceGroupId or list groups pending sealing; for one group’s full detail use evidencegroupget. |
| evidencegroupupdatebulk | Updates the editable metadata of SEVERAL evidence groups in one call (each entry carries its own evidenceGroupId and changes). Prefer evidencegroupupdate for a single group. Requires: the evidenceGroupIds to update (evidencegroup_search to find them). |
| evidencereportpdfurlget | Retrieves a download URL for a report’s signed PDF when you only hold the reportId (no caseFileId path needed — same document evidencecasefilereportpdfurlget returns). Requires: evidencecasefilereportgenerate → reportId. |
| evidencereportzipurlget | Retrieves a download URL for a report’s complete ZIP package when you only hold the reportId (same package evidencecasefilereportzipurlget returns). Requires: evidencecasefilereportgenerate → reportId. |
| createsignaturerequest | Creates a new signature request — the top-level container for documents and signatories in a signing flow. Use this first, before adddocumenttosignaturerequest. No prerequisites. Example: createsignaturerequest({ name: ‘NDA — Acme Corp’, createdBy: ‘jane@company.com’ }) returns { id, … } — use the returned id as signatureRequestId in subsequent calls. |
| adddocumenttosignaturerequest | Adds a document to a signature request — the first step of a 2-step upload (add, then PUT the file bytes to the returned upload URL). Use once per document that needs signing. Requires: createsignaturerequest → signatureRequestId, and the document’s SHA-256 hash (compute it before calling, or use the signaturerequestfull composite tool). Add signatories with addsignatoryto_document before activating. Signature type: INTERPOSITION = EAD Factory mediates the signing act on the signatory’s behalf (e.g. an OTP sent via WhatsApp/SMS) — the signatory needs no software or certificate. | ADVANCED = Advanced electronic signature — the signatory signs directly (signing pad or certificate); a stronger legal tier than INTERPOSITION. | OTHER = A signature type not covered by INTERPOSITION or ADVANCED. |
| addsignatorytodocument | Adds a signatory (by name + email) to a document within a signature request. Use once per person who needs to sign that specific document. Requires: createsignaturerequest → signatureRequestId, adddocumenttosignaturerequest → documentId. Add all signatories before calling activatesignature_request — signatories cannot be added after activation. |
| addvalidatortosignatory | Adds a validator to a document’s signatory: a person who must approve (validate) that signatory’s identity or the document before the signature can proceed. Add validators BEFORE activatesignaturerequest. Requires: adddocumenttosignaturerequest → documentId, addsignatorytodocument → signatoryId. The signaturerequestfull composite accepts validators inline. |
| addobservertodocument | Adds an observer to a signature request’s document: a person who receives read-only visibility of the process and the signed result without signing. Add observers BEFORE activatesignaturerequest. Requires: createsignaturerequest → signatureRequestId, adddocumenttosignature_request → documentId. |
| activatesignaturerequest | Activates a signature request, sending signing notifications to every added signatory — after this, no more documents or signatories can be added (use addvalidatortosignatory / addobservertodocument before activating if you need those roles). Requires: createsignaturerequest → signatureRequestId, at least one document (adddocumenttosignaturerequest) with its bytes uploaded, and at least one signatory per document (addsignatorytodocument). Prefer signaturerequest_full for a new request — it creates, adds documents+signatories, and activates in one call. |
| getsignaturerequest | Retrieves a signature request’s details and status by id (legacy top-level name). Use to check signing progress after activation. Requires: createsignaturerequest → signatureRequestId. |
| signaturerequestlist | List signature requests, optionally filtered by close condition among other criteria. Use to find a request when you don’t have its id (e.g. by name or status). Signature-request close condition: ALLREQUIRED = The request only closes once EVERY signatory has signed. | PARTIALALLOWED = The request can close once the minimum required signatories have signed, even if others haven’t yet. |
| signaturerequestcancel | Cancels an active signature request — no further signing can occur. Use when a request was activated in error or is no longer needed. Requires: createsignaturerequest → signatureRequestId. Cannot be undone. |
| signaturecertificategenerate | Generates the well-signed appearance certificate document for a signature request. Use once every signatory has signed (check with getsignaturerequest). Requires: createsignaturerequest → signatureRequestId. Unlike EAD Enterprise’s equivalent tool (a GET that polls an already-generated URL), this triggers generation and returns the result in the same call. |
| signaturecoordinateset | Sets the on-page (x, y, page) coordinates where a signatory’s signature appears on a document. Use after addsignatorytodocument if the signature placement needs to be explicit rather than auto-positioned. Requires: createsignaturerequest → signatureRequestId, adddocumenttosignaturerequest → documentId, addsignatorytodocument → signatoryId. |
| signaturedocumentdownloadurlget | Retrieves the download link for the FINAL, well-signed version of a document — the actual signed file, once every signatory has signed. Requires: createsignaturerequest → signatureRequestId, adddocumenttosignaturerequest → documentId. Use getsignaturerequest first to confirm signing is complete before calling this. Not to be confused with signaturecertificategenerate, which produces a separate appearance certificate document, not the signed document itself. |
| notificationrequestcreate | Creates a new notification request (draft) — the top-level container for receivers and attachments in a certified-notification flow. Use this first, before any other Notification-manager tool. No prerequisites. Set autosend: true to also send immediately on activation of the first receiver batch, or leave it false to add receivers/documents over several calls before calling notificationrequestsend yourself. Returns requestId and one notificationId per receiver already on the request (if any were included inline). |
| notificationrequestsend | Activates a notification request, triggering delivery to every added receiver across their configured channels. Runs as an MCP Task (bounded-polling until every receiver’s notification leaves its in-flight state — EAD Factory’s upstream emits no events for this transition). Requires: notificationrequestcreate → requestId, at least one receiver (notificationreceiveradd). Use notificationrequeststatus to check progress without waiting for the Task to complete. |
| notificationrequeststatus | Searches notifications, optionally filtered by requestId and/or delivery state — the closest equivalent to “checking a request’s status”: a request fans out into one notification per receiver, each with its own state history, so this returns every notification matching the filter with its current state. Omit requestId to search across every request. Requires: notificationrequestcreate → requestId (if filtering to one request). |
| notificationreceiveradd | Adds one or more receivers to a draft notification request — each receiver becomes its own per-channel notification under the shared requestId (there is no separate receiverId; track receivers by the notificationIds this call returns). Use once per batch of receivers before calling notificationrequestsend. Requires: notificationrequestcreate → requestId. Each receiver’s shape depends on its provider (SMTP/SMS/NOTICEMAN/WFB) — see the schema for the fields each variant needs. Notification delivery provider: SMTP = Email delivery. | SMS = SMS text message delivery. | NOTICEMAN = EAD Factory’s own certified notification channel (qualified electronic delivery). | NOTICEMANANDWHATSAPP = Certified channel plus a WhatsApp copy. | NOTICEMANANDWHATSAPPANDRCS = Certified channel plus WhatsApp and RCS copies. | NOTICEMANANDRCS = Certified channel plus an RCS (Rich Communication Services) copy. | WFB = WhatsApp Business messaging, uncertified (no Noticeman qualified channel). | RCS = RCS (Rich Communication Services) messaging only, uncertified. |
| notificationdocumentadd | Registers one or more document attachments (metadata only — fileName + SHA-256 hash) on a draft notification request. Use once per batch of documents before activating. Requires: notificationrequestcreate → requestId. This only registers metadata; call notificationdocumentuploadurlcreate for each registered attachment to get a URL to PUT the actual file bytes to. |
| notificationdocumentuploadurlcreate | Creates a presigned upload URL for a document attachment already registered via notificationdocumentadd — PUT the file bytes to the returned URL. Requires: notificationrequestcreate → requestId, notificationdocumentadd → attachmentId. |
| notificationdocumentdownloadurlcreate | Creates a presigned download URL for a document attachment on a notification request. Requires: notificationrequestcreate → requestId, notificationdocumentadd → attachmentId. |
| notificationcertificategenerate | Generates a delivery-certificate report for one or more notifications on a request. Use once notificationrequeststatus shows the relevant notifications have left their in-flight state. Requires: notificationrequestcreate → requestId, notificationrequeststatus → notificationIds. Returns a reportId — call notificationcertificatepdfurlget with it to get the actual download URL (2-step, same shape as Evidence’s report tools). |
| notificationcertificatepdfurlget | Retrieves the download URL for a previously generated notification delivery certificate. Requires: notificationcertificategenerate → reportId. |
| evidencecreatesealed | Creates (or reuses) an evidence group, registers and uploads one or more files as evidence, then seals (closes) the group — the full flagship evidence flow in one call instead of evidencegroupcreate + N x (evidencegroupevidenceregister + upload) + evidencegroupclose. Bounded-polls until the group reaches CLOSED (EAD Factory’s upstream emits no events for this transition): task-aware MCP clients get an asynchronous Task; any other client simply receives the final result synchronously. Requires: casefilecreate -> caseFileId. Provide evidenceGroupId to add to an existing OPEN group instead of creating one. Each evidence’s file uses the shared FileInput contract (local path, base64, https URL, or n8n binary item) — never a bespoke file field. On success returns the group id, its final CLOSED status, and each evidence’s id + sha256. Use the atomic evidencegroupcreate / evidencegroupevidenceregister / evidencegroupclose tools instead when you need to inspect or react to each intermediate step. |
| signaturerequestfull | Creates a signature request, adds one or more documents (each with its own signatories), and activates it — the full flagship signature flow in one call instead of createsignaturerequest + N x (adddocumenttosignaturerequest + addsignatorytodocument) + activatesignaturerequest. Each document’s file uses the shared FileInput contract (local path, base64, https URL, or n8n binary item) — never a bespoke file field. Set activate: false to leave the request in draft so you can add validators/observers (addvalidatortosignatory, addobserverto_document) before activating it yourself. On success returns the request id, each document’s id, and each signatory’s id. Use the atomic tools instead when you need to inspect or react to each intermediate step, or need validators/observers before activation. |
| eadfactoryhelp | Returns an overview of EAD Factory’s managers (Evidence, Signature, Notification, Chat), their key tools and starting points, and guidance on when to use a composite workflow tool (e.g. evidencecreatesealed) versus the atomic tools. Call this first if you’re unsure which tool to use — no credentials needed. |

MCP Tasks support

notificationrequestsend runs as an MCP Task and requires a client with MCP Tasks support — from other clients the call fails; instead, create the request with autosend: true (notificationrequestcreate) and poll notificationrequeststatus yourself.

evidencecreatesealed works from any client: task-aware clients get an asynchronous Task; all others simply receive the final result synchronously.

Coexistence

This MCP server is the current, actively maintained interface for the EAD Factory (Digital Trust) platform.

It coexists safely with any other MCP servers in your setup — it exposes only EAD-Factory-namespaced tools and shares no local state with other servers.

License

MIT — see LICENSE.