Ead Factory MCP server

Read from the package source without running it. The installed server may list more.

• activate_signature_request

  Activates a signature request, sending signing notifications to every added signatory \u2014 after this, no more documents or signatories can be added (use add_validator_to_signatory / add_observer_to_document before activating if you need those roles). Requires: create_signature_request \u2192 signatureRequestId, at least one document (add_document_to_signature_request) with its bytes uploaded, a

• add_document_to_signature_request

  Adds a document to a signature request \u2014 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: create_signature_request \u2192 signatureRequestId, and the document's SHA-256 hash (compute it before calling, or use the signature_request_full composite tool). Add signatories with add_signatory_to_document

• add_observer_to_document

  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 activate_signature_request. Requires: create_signature_request \u2192 signatureRequestId, add_document_to_signature_request \u2192 documentId.

• add_signatory_to_document

  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: create_signature_request \u2192 signatureRequestId, add_document_to_signature_request \u2192 documentId. Add all signatories before calling activate_signature_request \u2014 signatories cannot be added after activation.

• add_validator_to_signatory

  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 activate_signature_request. Requires: add_document_to_signature_request \u2192 documentId, add_signatory_to_document \u2192 signatoryId. The signature_request_full composite accepts validators inline.

• create_signature_requestwrite action

  Creates a new signature request \u2014 the top-level container for documents and signatories in a signing flow. Use this first, before add_document_to_signature_request. No prerequisites. Example: create_signature_request({ name: 'NDA \u2014 Acme Corp', createdBy: 'jane@company.com' }) returns { id, ... } \u2014 use the returned id as signatureRequestId in subsequent calls.

• ead_factory_help

  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. evidence_create_sealed) versus the atomic tools. Call this first if you're unsure which tool to use \u2014 no credentials needed.

• evidence_case_file_createwrite action

  Creates a new case file \u2014 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) \u2014 there is no `name` field, use `title` instead. Example: evidence_case_file_create({ id: '<generate a UUI

• evidence_case_file_delete_bulkwrite action

  Permanently deletes SEVERAL case files in one call. Destructive and not reversible \u2014 confirm the caseFileIds first (evidence_case_file_search) and prefer closing a case file via evidence_case_file_status_update when you only need to end work on it.

• evidence_case_file_get

  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: evidence_case_file_create \u2192 caseFileId.

• evidence_case_file_relationship_assign

  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: evidence_case_file_create \u2192 caseFileId.

• evidence_case_file_report_generate

  Generates the SIGNED evidentiary report of a case file (the certified document covering its sealed evidence). Returns a reportId \u2014 then call evidence_case_file_report_pdf_url_get (PDF) or evidence_case_file_report_zip_url_get (full package) to download. Requires: evidence_case_file_create \u2192 caseFileId; preview first with evidence_case_file_report_preview.

• evidence_case_file_report_pdf_url_get

  Retrieves a download URL for the signed PDF document of a case-file report. Requires: evidence_case_file_report_generate \u2192 reportId (plus caseFileId). For the full evidence package (PDF + files + verification data) use evidence_case_file_report_zip_url_get.

• evidence_case_file_report_preview

  Generates an UNSIGNED preview of a case file's evidentiary report so you can check its content before producing the signed version with evidence_case_file_report_generate. Requires: evidence_case_file_create \u2192 caseFileId, with sealed evidence groups inside.

• evidence_case_file_report_updatewrite action

  Updates a previously generated case-file report's metadata. Requires: evidence_case_file_report_generate \u2192 reportId (and the caseFileId it belongs to). Does not re-generate the report content \u2014 generate a new report for updated evidence.

• evidence_case_file_report_zip_url_get

  Retrieves a download URL for the complete ZIP package of a case-file report (signed PDF plus evidence files and verification material). Requires: evidence_case_file_report_generate \u2192 reportId (plus caseFileId).

• evidence_case_file_search

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

• evidence_case_file_status_updatewrite action

  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: evidence_case_file_create or evidence_case_file_search \u2192 caseFileId.

• evidence_case_file_updatewrite action

  Updates a single case file's editable metadata (e.g. name, description). Requires: evidence_case_file_create or evidence_case_file_search \u2192 caseFileId. To change its OPEN/CLOSE lifecycle state use evidence_case_file_status_update instead.

• evidence_case_file_update_bulkwrite action

  Updates the editable metadata of SEVERAL case files in one call (each entry carries its own caseFileId and changes). Prefer evidence_case_file_update for a single case file. Requires: the caseFileIds of every case file to update (evidence_case_file_search to find them).

• evidence_deletewrite action

  Permanently deletes one evidence by evidenceId (no group path needed). Destructive; sealed content should not be deleted \u2014 use only for drafts or mis-registered evidence. Requires: evidence_group_evidence_register or generate_evidence \u2192 evidenceId.

• evidence_download_url_createwrite action

  Creates a temporary download URL for an evidence's stored file when you only hold the evidenceId (no group path needed \u2014 same bytes as evidence_group_evidence_download_url_create). Requires: generate_evidence or evidence_group_evidence_register \u2192 evidenceId.

• evidence_group_close

  Seals (closes) an evidence group, triggering qualified timestamping \u2014 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 evidence_group_evidence_register. Requires: evidence_group_create \u2192 evidenceGroupId, evidence_case_file_create \u2192 caseFileId, and the current evidencesCount. ASY

• evidence_group_createwrite action

  Creates an evidence group inside a case file \u2014 evidence records are always registered inside a group, never standalone (except via the legacy generate_evidence tool). Use when starting a new batch of related evidence (e.g. all files for one incident). Like evidence_case_file_create, `id` is CALLER-SUPPLIED (generate a fresh UUID v4 yourself). Requires: evidence_case_file_create \u2192 caseFil

• evidence_group_delete_bulkwrite action

  Permanently deletes SEVERAL evidence groups of one case file in one call. Destructive \u2014 prefer evidence_group_discard for a single group, and never delete sealed groups that back issued reports. Requires: caseFileId + the evidenceGroupIds to delete (evidence_group_search to find them).

• evidence_group_discard

  Discards (deletes) an OPEN evidence group and its registered evidences \u2014 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 + evidence_group_create \u2192 evidenceGroupId.

• evidence_group_evidence_deletewrite action

  Permanently deletes one evidence from an evidence group. Only makes sense while the group is still OPEN (sealed groups are immutable). Requires: caseFileId + evidenceGroupId + evidence_group_evidence_register \u2192 evidenceId.

• evidence_group_evidence_download_url_createwrite action

  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 + evidence_group_evidence_register \u2192 evidenceId.

• evidence_group_evidence_get

  Gets one evidence's details (metadata, hash, custody, upload state) inside a specific evidence group. Requires: evidence_case_file_create \u2192 caseFileId, evidence_group_create \u2192 evidenceGroupId, evidence_group_evidence_register \u2192 evidenceId.

• evidence_group_evidence_register

  Register a new evidence in a group \u2014 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: evidence_group_create \u2192 evidenceGroupId, evidence_case_file_create \u2192 caseFileId, and the file's SHA-256 hash (compute it before calling, or use the evidence_create_sealed composit

• evidence_group_evidence_upload_url_createwrite action

  Creates a fresh presigned upload URL for an ALREADY-REGISTERED evidence in a group \u2014 step 2 of the register-then-upload flow (PUT the file bytes to the returned URL). Use when the URL from evidence_group_evidence_register expired or was lost. Requires: caseFileId + evidenceGroupId + evidenceId. evidence_create_sealed does all of this automatically.

• evidence_group_get

  Gets one evidence group's details \u2014 status (OPEN/CLOSED), seal information, and its evidences with their upload states. Use to verify every file was uploaded before evidence_group_close, or to check the seal after closing. Requires: caseFileId + evidence_group_create \u2192 evidenceGroupId.

• evidence_group_search

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

• evidence_group_updatewrite action

  Updates an evidence group's editable metadata (e.g. name, description). Only meaningful while the group is OPEN \u2014 sealed groups are immutable. Requires: caseFileId + evidence_group_create \u2192 evidenceGroupId.

• evidence_group_update_bulkwrite action

  Updates the editable metadata of SEVERAL evidence groups in one call (each entry carries its own evidenceGroupId and changes). Prefer evidence_group_update for a single group. Requires: the evidenceGroupIds to update (evidence_group_search to find them).

• evidence_multipart_upload_startwrite action

  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 (evidence_group_evidence_register or generate_evidence \u2192 evidenceId) and the file name.

• evidence_report_deletewrite action

  Permanently deletes a generated report by its reportId. Destructive \u2014 the signed document and its package stop being downloadable. Requires: evidence_case_file_report_generate \u2192 reportId. The underlying case file and its evidence are NOT touched.

• evidence_report_pdf_url_get

  Retrieves a download URL for a report's signed PDF when you only hold the reportId (no caseFileId path needed \u2014 same document evidence_case_file_report_pdf_url_get returns). Requires: evidence_case_file_report_generate \u2192 reportId.

• evidence_report_zip_url_get

  Retrieves a download URL for a report's complete ZIP package when you only hold the reportId (same package evidence_case_file_report_zip_url_get returns). Requires: evidence_case_file_report_generate \u2192 reportId.

• evidence_search

  Searches evidences across the tenant with optional filters (state, dates, pagination) \u2014 not scoped to one group. Use to find an evidenceId or audit what exists; for one group's content use evidence_group_get instead.

• evidence_temp_file_upload_url_createwrite action

  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 (evidence_group_evidence_register) or the evidence_create_sealed composite, which handle registration and upload together.

• evidence_thumbnail_url_get

  Retrieves a temporary URL for an image evidence's thumbnail at the requested size \u2014 use for quick visual verification without downloading the original file. Requires: caseFileId + evidenceGroupId + evidenceId (image-type evidence only) and a thumbnailSize path value.

• evidence_updatewrite action

  Updates a single evidence's editable metadata (e.g. name, description) by evidenceId. The file content and hash are immutable \u2014 re-register a new evidence for changed files. Requires: evidence_group_evidence_register or generate_evidence \u2192 evidenceId.

• evidence_update_bulkwrite action

  Updates the editable metadata of SEVERAL evidences in one call (each entry carries its own evidenceId and changes). Prefer evidence_update for a single evidence. Requires: the evidenceIds to update (evidence_search to find them).

• evidence_upload_url_createwrite action

  Creates a fresh presigned upload URL for an already-registered evidence by evidenceId \u2014 step 2 of the register-then-upload flow (PUT the file bytes to the returned URL). Pairs with generate_evidence the way evidence_group_evidence_upload_url_create pairs with evidence_group_evidence_register. Requires: generate_evidence \u2192 evidenceId.

• generate_evidence

  Register a new evidence (legacy top-level name; not scoped to a specific evidence group at creation time, unlike evidence_group_evidence_register). 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 evidence_create_sealed for a new, complete evidence group + evidence + seal flow. Custody

• get_evidence

  Retrieves an evidence record's details and status by id (legacy top-level name). Use to check an evidence's timestamping status (IN_PROCESS / COMPLETED / ERROR) after registration. Requires: generate_evidence or evidence_group_evidence_register \u2192 evidenceId.

• get_signature_request

  Retrieves a signature request's details and status by id (legacy top-level name). Use to check signing progress after activation. Requires: create_signature_request \u2192 signatureRequestId.

• notification_certificate_generate

  Generates a delivery-certificate report for one or more notifications on a request. Use once notification_request_status shows the relevant notifications have left their in-flight state. Requires: notification_request_create \u2192 requestId, notification_request_status \u2192 notificationIds. Returns a reportId \u2014 call notification_certificate_pdf_url_get with it to get the actual download UR

• notification_certificate_pdf_url_get

  Retrieves the download URL for a previously generated notification delivery certificate. Requires: notification_certificate_generate \u2192 reportId.

• notification_document_add

  Registers one or more document attachments (metadata only \u2014 fileName + SHA-256 hash) on a draft notification request. Use once per batch of documents before activating. Requires: notification_request_create \u2192 requestId. This only registers metadata; call notification_document_upload_url_create for each registered attachment to get a URL to PUT the actual file bytes to.

• notification_document_download_url_createwrite action

  Creates a presigned download URL for a document attachment on a notification request. Requires: notification_request_create \u2192 requestId, notification_document_add \u2192 attachmentId.

• notification_document_upload_url_createwrite action

  Creates a presigned upload URL for a document attachment already registered via notification_document_add \u2014 PUT the file bytes to the returned URL. Requires: notification_request_create \u2192 requestId, notification_document_add \u2192 attachmentId.

• notification_receiver_add

  Adds one or more receivers to a draft notification request \u2014 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 notification_request_send. Requires: notification_request_create \u2192 requestId. Each receiver's shape depends

• notification_request_createwrite action

  Creates a new notification request (draft) \u2014 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 notification_req

• notification_request_sendwrite action

  Activates a notification request, triggering delivery to every added receiver across their configured channels (email/SMS/Noticeman/WhatsApp/RCS). Runs as an MCP Task (bounded-polling until every receiver's notification leaves its in-flight state \u2014 EAD Factory's upstream emits no events for this transition). Requires: notification_request_create -> requestId, at least one receiver added via n

• notification_request_status

  Searches notifications, optionally filtered by requestId and/or delivery state \u2014 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: notification_request_create \u219

• signature_certificate_generate

  Generates the well-signed appearance certificate document for a signature request. Use once every signatory has signed (check with get_signature_request). Requires: create_signature_request \u2192 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.

• signature_coordinate_set

  Sets the on-page (x, y, page) coordinates where a signatory's signature appears on a document. Use after add_signatory_to_document if the signature placement needs to be explicit rather than auto-positioned. Requires: create_signature_request \u2192 signatureRequestId, add_document_to_signature_request \u2192 documentId, add_signatory_to_document \u2192 signatoryId.

• signature_document_download_url_get

  Retrieves the download link for the FINAL, well-signed version of a document \u2014 the actual signed file, once every signatory has signed. Requires: create_signature_request \u2192 signatureRequestId, add_document_to_signature_request \u2192 documentId. Use get_signature_request first to confirm signing is complete before calling this. Not to be confused with signature_certificate_generate, whic

• signature_request_cancelwrite action

  Cancels an active signature request \u2014 no further signing can occur. Use when a request was activated in error or is no longer needed. Requires: create_signature_request \u2192 signatureRequestId. Cannot be undone.

• signature_request_list

  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: ALL_REQUIRED = The request only closes once EVERY signatory has signed. | PARTIAL_ALLOWED = The request can close once the minimum required signatories have signed, even if others haven't yet.

• Code scan3 source files scanned20/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitystatic API keys via environment variables6/15
• Maintenancelast push 10 days ago15/15
• Maintainer identityregistry namespace matches repository owner7/10

Ead Factory: common questions

Is Ead Factory MCP server safe?

Mostly: it is graded B (74/100). Read the Ead Factory safety report

How do I install Ead Factory?

It runs on your machine. Copy the Claude Code, Claude Desktop or Cursor config from the install section.

Does Ead Factory need an API key?

Yes. The registry entry asks for MCP_SVC_CLIENT_SECRET.

Is Ead Factory maintained?

The last commit was 12 days ago (2026-09-09). The latest release is v1.4.0.