Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

io.github.g-digital-by-Garrigues/ead-enterprise-suite

NPM · @G-DIGITAL/MCP-EAD-ENTERPRISE-SUITE · SCANNED AUG 3

MCP server for EAD Enterprise Suite - signatures, evidence, notifications, dossiers via AI agents.

+39 this week 63 Trust /100
Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →

Supply Chain Security87
  • No malware found by supply-chain analysis.Pass
  • Only part of the dependency tree could be resolved (110 of 114), so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • Only part of the dependency tree could be resolved (110 of 114), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Build provenance is cryptographically sound, but it attests a different repository to the one declared in the registry. Most often the declared URL is simply stale. View diagnostics → Unverified
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 11 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability59
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 6344 tokens (~122/item across 52 items; 52 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage70
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 10% of tool parameters carry a description.Partial
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · @g-digital/mcp-ead-enterprise-suite

# add to Claude Code
claude mcp add g-digital-by-garrigues-ead-enterprise-suite -- npx -y @g-digital/mcp-ead-enterprise-suite
# add to Codex CLI
codex mcp add g-digital-by-garrigues-ead-enterprise-suite -- npx -y @g-digital/mcp-ead-enterprise-suite
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "g-digital-by-garrigues-ead-enterprise-suite": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@g-digital/mcp-ead-enterprise-suite"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add g-digital-by-garrigues-ead-enterprise-suite --command npx --arg -y --arg @g-digital/mcp-ead-enterprise-suite
# ~/.hermes/config.yaml
mcp_servers:
  g-digital-by-garrigues-ead-enterprise-suite:
    command: "npx"
    args: ["-y", "@g-digital/mcp-ead-enterprise-suite"]
// mcp.json
{
  "mcpServers": {
    "g-digital-by-garrigues-ead-enterprise-suite": {
      "command": "npx",
      "args": [
        "-y",
        "@g-digital/mcp-ead-enterprise-suite"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 3 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Aug 26 +57
    • Install scripts: unverified → pass security
    • Known CVEs: unverified → partial security
    • Malware scan: unverified → pass security
    • Provenance: Build provenance is cryptographically sound, but it attests a different repository to the one declared in the registry. Most often the declared URL is simply stale. security
    • Security disclosure: fail → unverified functional
    • Schema quality: unverified → good functional
    • Stability: unverified → 0.23 functional
    • MCP protocol: unverified → pass functional
    • Maintenance: unverified → pass functional
    • License: unverified → pass functional
    • Tool coverage: unverified → 100 functional
    • Dependency health: unverified → partial functional
    • Licence: MIT functional
  • 1 Aug 26 −12
    • Tool coverage: 100 → unverified functional
  • 31 Jul 26 −6
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 −18
    • Malware scan: pass → unverified security
  • 28 Jul 26 +17
    • Security disclosure: unverified → fail functional
    • Tool coverage: unverified → 100 functional
    • First check of Schema quality: fail functional
    • First check of Schema quality: unverified functional
    • First check of Schema quality: fail functional
    • First check of Tool coverage: 10 functional
  • 27 Jul 26 24

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Analysed npm/@g-digital/[email protected]

Provenance metadata_mismatch

Ecosystem: npm · Outcome: metadata_mismatch

Reason: repo_metadata_mismatch

Certificate issuer:
https://token.actions.githubusercontent.com
Certificate SAN:
https://github.com/g-digital-by-Garrigues/MCP_Market_Distribution/.github/workflows/publish.yml@refs/heads/main
Rekor log index:
2218221557
Predicate type:
https://slsa.dev/provenance/v1
Subject digest:
sha512:69270b5a2f5a01dd87b1a60432583bd5bf1a14c9275d6924255dfc05a18a75f44f2888cd0ed6bd31383797b5bcf45a0444ec84126ce48055121515bc1
Discovery method:
attestation_endpoint
Dependencies 110 packages

110 packages in the resolved dependency tree · 110 deprecated · 33 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 52 exposed · ~6,344 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens
activate_signature_request ~216

Activates a signature request, transitioning from DRAFT to ACTIVE and sending signing invitations to all signatories. Do NOT call this immediately after uploading files. Activation preconditions: request is DRAFT; at least one SIGNATORY exists; every document has been uploaded to its presigned URL; backend processing has had time to complete for every uploaded document (use processed/READY_TO_SIGN from signature_request_get when exposed; otherwise wait after the successful PUT); and PDF documents have signature coordinates set for every required signatory. INTERPOSITION may send a simple signing link, including WhatsApp when available/configured; ADVANCED uses phonePrefix/phoneNumber for OTP and currently does not support WhatsApp delivery. IRREVERSIBLE: cannot add documents or participants after activation. ASYNC: after activation, poll signature_request_get until status is ACTIVE, then use signature_document_list with documentId to monitor signing; call signature_certificate_get only after the document is SIGNED.

NameTypeReqDescription
caseFileIdstringyes
requestIdstringyes

No output schema declared.

No examples provided.

assign_validator_to_signatory ~117

Assigns one or more validators to a specific signatory in a signature request. The validator must approve before the signatory can sign. Requires: signature_participant_create (validator) → validatorId in validatorIds array, signature_participant_create (signatory) → signatoryId, signature_request_create → requestId, case_file_create → caseFileId.

NameTypeReqDescription
caseFileIdstringyes
requestIdstringyes
signatoryIdstringyes
validatorIdsarrayyes

No output schema declared.

No examples provided.

case_file_create ~97

Creates a new case file — the top-level container for all related operations (evidence, notifications, signatures, dossiers). Call this first before any other operation. Generate a UUID v4 for `id`. Returns caseFileId needed for all subsequent calls.

NameTypeReqDescription
descriptionstring
idstringyes
namestringyes
referencestring
useCaseIdstringyes

No output schema declared.

No examples provided.

case_file_get ~50

Retrieves details of a specific case file. Requires: caseFileId. Use to verify a case file exists before creating evidence groups, dossiers, or signature requests.

NameTypeReqDescription
caseFileIdstringyes

No output schema declared.

No examples provided.

case_file_list ~80

Lists all case files in your EAD Enterprise Suite account. Pass userId (from session_login or session_info) to scope results to your account. Returns paginated list with IDs, names, and status.

NameTypeReqDescription
filterobject
orderobject
pageobject
userIdstringyes

No output schema declared.

No examples provided.

dossier_certify ~95

Certifies a dossier, generating a tamper-evident PDF and locking all linked evidence. Requires: dossier_create → dossierId, dossier_evidence_link (evidence linked), case_file_create → caseFileId. ASYNC: transitions DRAFT → CERTIFYING → CERTIFIED. Poll dossier_list until dossierId status === CERTIFIED.

NameTypeReqDescription
caseFileIdstringyes
dossierIdstringyes

No output schema declared.

No examples provided.

dossier_create ~164

Creates a dossier to aggregate certified evidence groups into a single tamper-evident PDF. Requires: case_file_create → caseFileId. Evidence groups must be in CLOSED status before linking. Generate a UUID v4 string for `id`. Returns dossierId. After creation, link evidence with dossier_evidence_link, then certify with dossier_certify.

NameTypeReqDescription
accessTokenstring
caseFileIdstringyes
dossierTemplateIdstring
filledFieldsobject
idstringyes
languagestringyes
modelIdstring
namestringyes
purposestring
validityFromstringyes
validityTostringyes

No output schema declared.

No examples provided.

dossier_delete ~66

Deletes a dossier. Available in DRAFT status (to discard before certification) or in CERTIFIED status (to permanently remove the certified dossier). Irreversible. Requires: caseFileId and dossierId.

NameTypeReqDescription
caseFileIdstringyes
dossierIdstringyes

No output schema declared.

No examples provided.

dossier_document_url ~53

Returns the download URL for the certified dossier PDF. Requires: dossier_certify (CERTIFIED status), caseFileId, dossierId.

NameTypeReqDescription
caseFileIdstringyes
dossierIdstringyes

No output schema declared.

No examples provided.

dossier_evidence_delete ~76

Removes an evidence item from a dossier. Only available while dossier is in DRAFT status. Requires: caseFileId, dossierId, evidenceId.

NameTypeReqDescription
caseFileIdstringyes
dossierEvidenceGroupIdstringyes
dossierEvidenceIdstringyes
dossierIdstringyes

No output schema declared.

No examples provided.

dossier_evidence_get ~70

Retrieves details of a specific evidence item linked to a dossier. Requires: caseFileId, dossierId, evidenceId.

NameTypeReqDescription
caseFileIdstringyes
dossierEvidenceGroupIdstringyes
dossierEvidenceIdstringyes
dossierIdstringyes

No output schema declared.

No examples provided.

dossier_evidence_link ~100

Links evidence items from a sealed group to a dossier. Requires: dossier_create → dossierId, evidence_seal (CLOSED), case_file_create → caseFileId. Pass the ids array of evidence UUIDs. Can be called multiple times for evidence from different case files.

NameTypeReqDescription
caseFileIdstringyes
caseFileToLinkIdstringyes
dossierIdstringyes
idsarrayyes

No output schema declared.

No examples provided.

dossier_evidence_list ~76

Lists all evidence items linked to a dossier. Requires: caseFileId and dossierId.

NameTypeReqDescription
caseFileIdstringyes
dossierEvidenceGroupIdstringyes
dossierIdstringyes
filterobject
orderobject
pageobject

No output schema declared.

No examples provided.

dossier_evidence_list_to_link ~88

Lists evidence items available to be linked to a dossier (CLOSED groups not yet linked). Requires: caseFileId and dossierId.

NameTypeReqDescription
caseFileIdstringyes
caseFileToLinkIdstringyes
dossierIdstringyes
filterobject
orderobject
pageobject

No output schema declared.

No examples provided.

dossier_get ~51

Retrieves full details of a specific dossier including status, linked evidence, and download URLs. Requires: caseFileId and dossierId.

NameTypeReqDescription
caseFileIdstringyes
dossierIdstringyes

No output schema declared.

No examples provided.

dossier_group_certify ~133

Creates AND certifies a dossier from a single sealed evidence group in one call (express path). Requires: evidence_seal (CLOSED), case_file_create → caseFileId, evidence_group_create → evidenceGroupId. Generate a UUID v4 string for `id`. Returns dossierId with CERTIFYING status → poll until CERTIFIED.

NameTypeReqDescription
caseFileIdstringyes
evidenceGroupIdstringyes
evidenceIdsarray
idstringyes
languagestringyes
modelIdstring
namestringyes

No output schema declared.

No examples provided.

dossier_list ~80

Lists all dossiers in a case file. Requires: caseFileId. Returns paginated list with IDs, names, status, and creation dates. Use to monitor certification progress — poll until status: CERTIFIED.

NameTypeReqDescription
caseFileIdstringyes
filterobject
orderobject
pageobject

No output schema declared.

No examples provided.

dossier_package_url ~58

Returns the download URL for the full dossier package (PDF + evidence files). Requires: dossier_certify (CERTIFIED status), caseFileId, dossierId.

NameTypeReqDescription
caseFileIdstringyes
dossierIdstringyes

No output schema declared.

No examples provided.

dossier_preview ~45

Returns an HTML preview URL of a dossier before certification. Requires: caseFileId and dossierId.

NameTypeReqDescription
caseFileIdstringyes
dossierIdstringyes

No output schema declared.

No examples provided.

dossier_template_list ~45

Lists available dossier templates. No prerequisites. Returns template IDs and their translations per language. Use the returned id as dossierTemplateId in dossier_create.

NameTypeReqDescription
pageobject

No output schema declared.

No examples provided.

dossier_update ~125

Updates the metadata of an existing dossier. Requires: dossier_create → dossierId, caseFileId. Only available while dossier is in DRAFT status.

NameTypeReqDescription
accessTokenstring
caseFileIdstringyes
dossierIdstringyes
dossierTemplateIdstring
filledFieldsobject
languagestring
modelIdstring
namestring
purposestring
validityFromstring
validityTostring

No output schema declared.

No examples provided.

dossier_visibility ~61

Updates the visibility (public/private) of a certified dossier. Requires: dossier_certify (CERTIFIED status), caseFileId, dossierId.

NameTypeReqDescription
caseFileIdstringyes
dossierIdstringyes
visibilitystringyes

No output schema declared.

No examples provided.

evidence_create ~420

Registers a NEW evidence record inside an evidence group. Requires: evidence_group_create → evidenceGroupId, case_file_create → caseFileId. Generate a UUID v4 for `id`. Compute the SHA-256 hex hash of the file BEFORE calling. Normal INTERNAL flow: call evidence_create with custodyType INTERNAL and NO fileUrl; the API returns uploadFileUrl, a presigned S3 URL. You MUST PUT the exact file bytes to uploadFileUrl, then verify with evidence_get/evidence_list, and ONLY THEN call evidence_seal. Do not seal an evidence group until every INTERNAL evidence file has been uploaded. Convenience flow: if you pass `fileUrl` (public HTTPS, no redirects, under 1 GiB), this tool downloads that URL and PUTs the bytes to uploadFileUrl for you. EXTERNAL flow: use custodyType EXTERNAL only when you intentionally register hash-only evidence; still generate a fresh UUID for each evidence. If an INTERNAL evidence creation/upload failed and you want to retry as EXTERNAL, create a NEW evidence id; do not reuse an id whose outcome is unknown. WARNING: the API sometimes returns {code:'EvidenceCreateError'} even when the evidence was successfully persisted — always verify with evidence_list before retrying.

NameTypeReqDescription
caseFileIdstringyesUUID of the case file
custodyTypestringINTERNAL = EAD stores the file; EXTERNAL = only hash registered
evidenceGroupIdstringyesUUID of the evidence group
fileNamestringyesOriginal file name including extension
fileUrlstringOptional public HTTPS URL to download and auto-upload to the returned uploadFileUrl (custodyType INTERNAL only). Omit this when you want the manual presigned-URL flow.
hashstringyesSHA-256 hex digest of the file content (64 hex chars)
idstringyesUUID v4 for the new evidence record (idempotency key)
titlestringyesHuman-readable title for the evidence

No output schema declared.

No examples provided.

evidence_get ~83

Retrieves a specific evidence record. Requires: evidence_create → evidenceId, evidence_group_create → evidenceGroupId, case_file_create → caseFileId. Returns status (COMPLETED|IN_PROCESS|ERROR), hash, and tspTimestamp when certified.

NameTypeReqDescription
caseFileIdstringyes
evidenceGroupIdstringyes
idstringyes

No output schema declared.

No examples provided.

evidence_group_create ~110

Creates an evidence group inside a case file. Requires: case_file_create → caseFileId. Generate a UUID v4 for `id`. Set evidenceType to FILE, PHOTO, VIDEO, or WEB_PLUGIN. Returns evidenceGroupId. One group can contain multiple evidence records.

NameTypeReqDescription
attestationobject
caseFileIdstringyes
descriptionstring
evidenceTypestringyes
idstringyes
namestringyes

No output schema declared.

No examples provided.

evidence_group_list ~81

Lists all evidence groups in a case file with their current status (OPEN, CLOSING, CLOSED). Use to find an existing group or check which groups are ready for sealing. Requires: caseFileId.

NameTypeReqDescription
caseFileIdstringyes
filterobject
orderobject
pageobject

No output schema declared.

No examples provided.

evidence_list ~81

Lists all evidence records in a specific evidence group. Requires: caseFileId and evidenceGroupId. Returns paginated list with IDs, titles, status, and timestamps.

NameTypeReqDescription
caseFileIdstringyes
evidenceGroupIdstringyes
filterobject
orderobject
pageobject

No output schema declared.

No examples provided.

evidence_seal ~162

Seal and certify an evidence group. Closes the group to new additions and triggers async timestamping. Returns immediately — the group transitions OPEN → CLOSING → CLOSED. Poll evidence_group_list until status is CLOSED before linking to a dossier.

NameTypeReqDescription
altitudeLocationstring
attestationobject
caseFileIdstringyes
deviceManufacturerstring
deviceModelstring
deviceOSstring
evidencesCountnumberyes
idstringyes
latitudeLocationstring
locationAccuracystring
longitudeLocationstring
userAgentstring
webUrlstring

No output schema declared.

No examples provided.

evidence_upload ~375

Uploads a local file as evidence in one step: computes its SHA-256, registers the evidence record (custodyType INTERNAL = EAD stores the file), and uploads the bytes to S3 — no manual hashing or PUT needed. Internally this follows the required EAD sequence: create INTERNAL evidence → receive uploadFileUrl (presigned S3 URL) → PUT file bytes → return uploaded:true. Requires: case_file_create → caseFileId, evidence_group_create → evidenceGroupId. Provide EXACTLY ONE of `filePath` (absolute local path, stdio/local mode only) or `contentBase64` (base64-encoded file content, ~10 MB max). Use evidence_upload when the file is on the local machine; use evidence_create when you already have the SHA-256 hash, need to inspect/use uploadFileUrl manually, or have a public fileUrl. After this tool succeeds, verify with evidence_get/evidence_list and only then call evidence_seal. If this tool fails before returning an evidence id, check evidence_list before retrying; if retrying manually, use evidence_create with a fresh UUID. Local files must be under 1 GiB.

NameTypeReqDescription
caseFileIdstringyesUUID of the case file
contentBase64stringBase64-encoded file content (~10 MB max). The tool will create evidence, receive uploadFileUrl, and PUT these bytes to it.
evidenceGroupIdstringyesUUID of the evidence group
fileNamestringyesFile name including extension
filePathstringAbsolute local path to the file (stdio/local mode only). The tool will create evidence, receive uploadFileUrl, and PUT this file to it.
titlestringyesHuman-readable title for the evidence

No output schema declared.

No examples provided.

large_evidence_upload_complete ~82

Finalize a multipart evidence upload and register the evidence in the group. Returns immediately — the evidence transitions asynchronously to COMPLETED. Poll evidence_list until status is COMPLETED before sealing the group.

NameTypeReqDescription
caseFileIdstringyes
evidenceGroupIdstringyes
idstringyes
userAgentstring

No output schema declared.

No examples provided.

large_evidence_upload_initiate ~104

Performs the large_evidence_upload_initiate operation against the GoCertius API. Review the API documentation for full field details.

NameTypeReqDescription
capturedAtstringyes
caseFileIdstringyes
evidenceGroupIdstringyes
evidenceIdstringyes
fileNamestringyes
idstringyes
titlestringyes
totalSizeMBnumberyes

No output schema declared.

No examples provided.

notification_certificate_get ~153

Creates or retrieves a PDF certificate for a specific notification receiver. Requires notification_request_send and notification_receiver_add. Generate a UUID v4 for `id` the first time and reuse that id when polling. This tool is idempotent: it first lists existing certificates for the receiver and, if `id` already exists, returns it instead of creating it again. If the certificate status is CERTIFIED, the response includes documentUrl when available. If it is CERTIFYING, poll this same tool with the same id.

NameTypeReqDescription
caseFileIdstringyes
idstringyes
languagestring
notificationRequestIdstringyes
receiverIdstringyes

No output schema declared.

No examples provided.

notification_document_add ~73

Performs the notification_document_add operation. Review the API documentation for full field details.

NameTypeReqDescription
caseFileIdstringyes
fileNamestringyes
fileSizenumber
hashstringyes
idstringyes
notificationRequestIdstringyes

No output schema declared.

No examples provided.

notification_receiver_add ~141

Adds a recipient to a notification request. Requires: notification_request_create → notificationRequestId, case_file_create → caseFileId. The `id` can be a UUID v4 or custom string. Returns receiverId — save it for notification_certificate_get.

NameTypeReqDescription
caseFileIdstringyes
emailstringyes
firstNamestringyes
idstringyes
lastNamestringyes
notificationRequestIdstringyes
otpRequiredboolean
phoneNumberstring
phonePrefixstring
sendWaUrlboolean

No output schema declared.

No examples provided.

notification_request_create ~228

Creates a certified notification request. Requires: case_file_create → caseFileId. Generate a UUID v4 for `id`. Set language to en_GB or es_ES. Returns notificationRequestId. Add at least one receiver with notification_receiver_add before sending. IMPORTANT: The `content` field must be valid HTML — plain text without HTML tags will not render on the recipient landing page. Only the following HTML formats are supported: paragraphs (<p>), bold (<strong>), italic (<em>), unordered lists (<ul><li>), ordered lists (<ol><li>). Do not use other HTML tags or CSS. Avoid special typographic characters (em dashes, smart quotes) in `subject`; use standard ASCII equivalents (hyphen, straight quotes) instead.

NameTypeReqDescription
caseFileIdstringyes
contentstringyes
idstringyes
languagestringyes
otpByDefaultboolean
sendWaUrlByDefaultboolean
subjectstringyes
typestring

No output schema declared.

No examples provided.

notification_request_send ~59

Trigger delivery of a certified notification to all added recipients. Returns immediately — delivery is async. Poll notification_request_status until status is DELIVERED before retrieving certificates.

NameTypeReqDescription
caseFileIdstringyes
notificationRequestIdstringyes

No output schema declared.

No examples provided.

notification_request_status ~111

Checks the delivery status of a certified notification. Requires: notificationRequestId, caseFileId. Returns status (CREATING|DRAFT|IN_PROCESS|SENT|PARTIALLY_READ|FULLY_READ|PARTIALLY_ANSWERED|FULLY_ANSWERED). Poll until status is SENT or beyond. Do not call notification_certificate_get while status is CREATING, DRAFT, or IN_PROCESS.

NameTypeReqDescription
caseFileIdstringyes
notificationRequestIdstringyes

No output schema declared.

No examples provided.

profile_get ~134

Returns the authenticated user's own profile. Works on EVERY auth flow (user key or email/password) because it identifies the caller from the session token alone — no email needed. Its `id` field IS your userId (UUID): the value required by case_file_list and every /users/{userId}/... operation. Prefer this over session_info when you need the userId, and it is the ONLY way to obtain it on a user-key deployment (MCP_AUTH_USER_KEY), where no email is configured. Also returns companyId (needed to subscribe to the notifications SSE stream) and defaultCaseFileId. No parameters.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

session_info ~154

Returns the authenticated user's session info including userId and session type (Password or UserKey). Use this to retrieve the userId (UUID) required by case_file_list and other user-scoped operations. Works on both auth flows: with a user key (MCP_AUTH_USER_KEY) it resolves identity via profile_get (GET /profile → `id`), since no email is configured; with MCP_AUTH_EMAIL it queries /session-info. profile_get is the canonical way to obtain the userId and returns more (companyId, defaultCaseFileId). Prerequisites: a valid session (call session_login first if needed). Example: session_info() → { userId: '...uuid...', type: 'Password' }

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

session_login ~69

Authenticate with EAD Enterprise Suite. Credentials are read from the server environment: if MCP_AUTH_USER_KEY is set it is exchanged for a session token; otherwise MCP_AUTH_EMAIL + MCP_AUTH_PASSWORD are used. The server manages authentication automatically — call this only to force a re-login or after a 401.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

signature_certificate_get ~93

Retrieves the signed document certificate PDF. Requires: activate_signature_request (document fully SIGNED), signature_request_add_document → documentId, signature_request_create → requestId, case_file_create → caseFileId. Returns documentUrl (signed PDF certificate). ASYNC: poll until documentUrl is available.

NameTypeReqDescription
caseFileIdstringyes
documentIdstringyes
requestIdstringyes

No output schema declared.

No examples provided.

signature_coordinate_set ~152

Sets the visual position of the signature field on a PDF document page. Required for PDF documents before activation, for both INTERPOSITION and ADVANCED signatures. Requires: signature_participant_create → signatoryId, signature_request_add_document → documentId, signature_request_create → requestId, case_file_create → caseFileId. Provide coordinates as array of {page (1-based), x (points from left), y (points from bottom)}. Set coordinates after the document has been uploaded and before activate_signature_request.

NameTypeReqDescription
caseFileIdstringyes
coordinatesarrayyes
documentIdstringyes
requestIdstringyes
signatoryIdstringyes

No output schema declared.

No examples provided.

signature_document_list ~134

Lists documents in a signature request with their signing status per document. Requires: signature_request_create → requestId, case_file_create → caseFileId. IMPORTANT: when called with documentId it returns participant signing status (PENDING = not yet signed), NOT document processing status. To check if documents reached READY_TO_SIGN (required before activate_signature_request), use signature_request_get instead. Post-activation: poll until document status === SIGNED before calling signature_certificate_get.

NameTypeReqDescription
caseFileIdstringyes
documentIdstringyes
pageobject
requestIdstringyes

No output schema declared.

No examples provided.

signature_group_create ~260

Creates a signing order group for a CONFIGURABLE signature request. Types: 'Document' (groups documents into signing rounds — use its id as groupId in signature_request_add_document), 'Signatory' (groups signatories into signing rounds — use its id as groupId in signature_participant_create), 'DocumentSignatory' (links a specific document to a signing round, requires documentId). IMPORTANT — avoid empty groups: when a CONFIGURABLE request is created, the API automatically pre-creates one Document group and one Signatory group both at index:1. Always use these pre-existing index:1 groups for your first document and first signatory (retrieve their IDs with signature_group_list immediately after creating the request). Only call signature_group_create for the ADDITIONAL groups (index:2, 3…). Add participants with linkToAllDocuments:true so DocumentSignatory groups are auto-generated at the correct index. Adding participants without linkToAllDocuments leaves them unlinked to documents and signature_coordinate_set will fail with 'Signatory not found'.

NameTypeReqDescription
caseFileIdstringyes
documentIdstring
idstringyes
requestIdstringyes
typestringyes

No output schema declared.

No examples provided.

signature_group_list ~105

Lists all signing order groups of a CONFIGURABLE signature request. Returns id, type (Document/Signatory/DocumentSignatory), index, and documentId for each group. Call immediately after signature_request_create to retrieve the pre-created index:1 group IDs before adding documents or participants.

NameTypeReqDescription
caseFileIdstringyes
filterobject
orderobject
pageobject
requestIdstringyes

No output schema declared.

No examples provided.

signature_participant_create ~284

Adds a participant (signatory, observer, or validator) to a DRAFT signature request. Requires: signature_request_add_document → documentId + file uploaded to S3, signature_request_create → requestId, case_file_create → caseFileId. Use role SIGNATORY for required signers, OBSERVER for read-only, VALIDATOR for approvers. For ADVANCED signatures, phonePrefix and phoneNumber are mandatory because the signer receives the OTP there; WhatsApp delivery is NOT currently supported for ADVANCED. For INTERPOSITION signatures, phone is optional, and WhatsApp sending is currently available only for this simple/interposition flow when the platform is configured to send a WhatsApp signing link. Returns signatoryId. Add at least one SIGNATORY before activating. For VALIDATOR role: do NOT include groupId or linkToAllDocuments — use assign_validator_to_signatory to link the validator to a specific signatory after creation.

NameTypeReqDescription
caseFileIdstringyes
emailstringyes
firstNamestringyes
groupIdstring
idstringyes
lastNamestringyes
linkToAllDocumentsboolean
phoneNumberstring
phonePrefixstring
requestIdstringyes
rolestringyes

No output schema declared.

No examples provided.

signature_participant_list ~77

Lists all participants of a signature request. Requires: signature_request_create → requestId, case_file_create → caseFileId. Returns roles, contact details, and signing status.

NameTypeReqDescription
caseFileIdstringyes
documentIdstringyes
pageobject
requestIdstringyes

No output schema declared.

No examples provided.

signature_request_add_document ~340

Adds a document to a DRAFT signature request. Requires: signature_request_create → requestId, case_file_create → caseFileId. Provide a string `id` for the document. Compute SHA-256 hex hash of the PDF before calling. Optional: pass `fileUrl` (a publicly accessible URL) to have the tool download and upload the file to S3 automatically — no separate PUT needed. If fileUrl is omitted, returns url (presigned S3 upload URL) for manual PUT. Cannot add documents after activate_signature_request is called. For CONFIGURABLE sequence: `groupId` must reference a Document type group (not Signatory or DocumentSignatory) — passing a wrong group type returns 'Signature group not found'.

NameTypeReqDescription
caseFileIdstringyesUUID of the case file
convertToPdfbooleanConvert non-PDF to PDF before processing
fileNamestringyesFile name including extension (e.g. contract.pdf)
fileSizenumberFile size in bytes (optional)
fileUrlstringOptional public URL to download and auto-upload the PDF to S3. Eliminates the manual PUT step.
groupIdstringFor CONFIGURABLE sequence: ID of a Document type group
hashstringyesSHA-256 hex digest of the PDF content (64 hex chars)
idstringyesUUID for the document — becomes documentId for coordinate_set and certificate_get
requestIdstringyesUUID of the signature request (DRAFT)
titlestringyesDocument title shown to signatories

No output schema declared.

No examples provided.

signature_request_cancel ~59

Cancels an active signature request. Requires: activate_signature_request (ACTIVE status), requestId, caseFileId. Transitions to CANCELLED. Cannot be undone.

NameTypeReqDescription
caseFileIdstringyes
requestIdstringyes

No output schema declared.

No examples provided.

signature_request_create ~150

Creates a new signature request in DRAFT status. Requires: case_file_create → caseFileId. Generate a UUID v4 for `id`. Set deadline as ISO 8601 datetime (max ~30 days ahead). Returns requestId. Add documents with signature_request_add_document and participants with signature_participant_create before activating.

NameTypeReqDescription
caseFileIdstringyes
closeConditionstring
dashboardUrlstring
deadlinestringyes
idstringyes
languagestringyes
namestringyes
objectiveIdstring
sequencestring
signatureTypestring

No output schema declared.

No examples provided.