Ead Factory Mcp

Created By
g-digital-by-Garrigues9 days ago
EAD Factory MCP exposes EAD Trust's Evidence Manager and Signature Manager APIs to any MCP-compatible client (Claude Code, Claude Desktop, Cursor, etc.). The 9 tools cover full evidence generation — SHA-256 file hashing, S3 upload, Okta OAuth2 client_credentials authentication, and status polling until COMPLETED — and the complete signature-request lifecycle: create draft → add documents → add signatories / validators / observers → activate the request → retrieve status. Built by g-digital by Garrigues (J&A Garrigues, S.L.P.), an eIDAS-qualified trust services provider. Two transports: stdio for local desktop clients, HTTP with Bearer OAuth2 for hosted deployments.
Overview

xEAD Factory MCP bridges any MCP-compatible client (Claude Code, Claude Desktop, Cursor, etc.) to EAD Trust's Evidence Manager and Signature Manager APIs, exposing the full Digital Trust services flow as 9 tools.

What it does

  • Evidence generation: hash a local file (SHA-256), upload to S3, register with EAD Trust's Evidence Manager, and poll until status is COMPLETED or ERROR. One tool, full flow.
  • Signature requests: create a draft, add documents (uploaded to S3), add signatories with optional validators and observers, activate the request to trigger notifications, and retrieve status at any time.

Tools (9)

generate_evidence, get_evidence, create_signature_request, add_document_to_signature_request, add_signatory_to_document, add_validator_to_signatory, add_observer_to_document, activate_signature_request, get_signature_request.

Install

npx -y @g-digital/mcp-ead-factory

Or via Docker:

docker run --rm -it --env-file .env gdigital/ead-factory:1.0.12

Auth

OAuth2 client_credentials grant against an EAD Trust Okta tenant. Required env: OKTA_TOKEN_URL, OKTA_CLIENT_ID, OKTA_CLIENT_SECRET, OKTA_SCOPE=token, API_BASE_URL, SIGNATURE_API_BASE_URL. Credentials available from EAD Trust on request.

Transports

stdio for local desktop clients; http (Bearer OAuth2 inbound) for hosted deployments.

Maintainer

g-digital by Garrigues (J&A Garrigues, S.L.P.) — an eIDAS-qualified trust services provider. MIT licensed. Source repo.

Also published on npm, Docker Hub, the MCP Official Registry, Smithery, and as an n8n community node.

Server Config

{
  "mcpServers": {
    "ead-factory": {
      "command": "npx",
      "args": [
        "-y",
        "@g-digital/mcp-ead-factory"
      ],
      "env": {
        "OKTA_TOKEN_URL": "https://<your-okta-tenant>.okta.com/oauth2/<authServer>/v1/token",
        "OKTA_CLIENT_ID": "<your-okta-client-id>",
        "OKTA_CLIENT_SECRET": "<your-okta-client-secret>",
        "OKTA_SCOPE": "token",
        "API_BASE_URL": "https://api.int.gcloudfactory.com/digital-trust",
        "SIGNATURE_API_BASE_URL": "https://api.int.gcloudfactory.com/signature-manager"
      }
    }
  }
}
Project Info
Created At
9 days ago
Updated At
9 days ago
Author Name
g-digital-by-Garrigues
Star
-
Language
-
License
-
Category

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

21 hours ago