Skip to main content
Glama
g-digital-by-Garrigues

EAD Enterprise Suite MCP Server

by g-digital-by-Garrigues
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to EAD Enterprise Suite MCP Server

No user-submitted related servers found.

    Related Servers

    • addsign-mcp

      rmindgh
      A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to send documents for e-signature, track signing status, remind pending signers, and download signed PDFs with audit-trail hashes via the AddSign API.
      6
      30 npm
      MIT

    • zyta-sign-mcp

      blanck1945
      A
      license
      C
      quality
      D
      maintenance
      Enables AI agents to manage Zyta Sign documents, signatures, and studies with secure authentication and permission-respecting operations.
      49
      5 npm
      MIT
    • Formify MCP by formify-e-sign

      Formify MCPofficial

      formify-e-sign
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to create fillable PDFs, send contracts for e-signature, verify signers via BankID or ID scans, and track post-send document workflows.
      5
      MIT
    • layerone-mcp by GOLayerone

      layerone-mcpofficial

      GOLayerone
      A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to generate documents (PDF/DOCX/Factur-X) and manage electronic signatures (eIDAS/PAdES) via natural language using LayerOne's DocX and Sign APIs.
      20
      20 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.1/5.0

    Scored across 52 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes (e.g., evidence_create vs evidence_upload, dossier_certify vs dossier_group_certify), but some overlap exists, like between notification_document_add (vague description) and other notification tools, and between large_evidence_upload_initiate and evidence_upload. The large number of tools may cause selection difficulty.

    Naming Consistency4/5

    Pattern is mostly verb_noun (e.g., evidence_create, dossier_certify, signature_request_create), with a few deviations like notification_document_add (noun_noun_verb) and assign_validator_to_signatory (verb_noun_prep_noun). Overall consistent, but minor inconsistencies reduce the score.

    Tool Count3/5

    52 tools is high for most MCP servers, but the suite covers multiple domains (evidence, dossiers, notifications, signatures, sessions). Some tools could be consolidated (e.g., large_evidence_upload_initiate and evidence_upload). Feels slightly over-scoped but justified for enterprise use.

    Completeness4/5

    Covers full lifecycle for evidence, dossiers, notifications, and signatures, including advanced features like coordinate setting and validator assignment. Missing updates for evidence groups and a global notification list, but main workflows are well-supported.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources