Ead Enterprise Suite runs on your own machine — the client starts it, so there is no endpoint to ping. 201 installs a week from npm. Last commit 8 Sep 2026.
MCP server for EAD Enterprise Suite - signatures, evidence, notifications, dossiers via AI agents.
Today is the operative word: we check Ead Enterprise Suite every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add ead-enterprise-suite -e 'MCP_API_BASE_URL=<MCP_API_BASE_URL>' -e 'MCP_AUTH_USER_KEY=<MCP_AUTH_USER_KEY>' -- npx -y @g-digital/mcp-ead-enterprise-suite
{
"mcpServers": {
"ead-enterprise-suite": {
"command": "npx",
"args": [
"-y",
"@g-digital/mcp-ead-enterprise-suite"
],
"env": {
"MCP_API_BASE_URL": "<MCP_API_BASE_URL>",
"MCP_AUTH_USER_KEY": "<MCP_AUTH_USER_KEY>"
}
}
}
}
[mcp_servers.ead-enterprise-suite]
command = "npx"
args = ["-y", "@g-digital/mcp-ead-enterprise-suite"]
env = { MCP_API_BASE_URL = "<MCP_API_BASE_URL>", MCP_AUTH_USER_KEY = "<MCP_AUTH_USER_KEY>" }
{
"mcpServers": {
"ead-enterprise-suite": {
"command": "npx",
"args": [
"-y",
"@g-digital/mcp-ead-enterprise-suite"
],
"env": {
"MCP_API_BASE_URL": "<MCP_API_BASE_URL>",
"MCP_AUTH_USER_KEY": "<MCP_AUTH_USER_KEY>"
}
}
}
}
{
"servers": {
"ead-enterprise-suite": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@g-digital/mcp-ead-enterprise-suite"
],
"env": {
"MCP_API_BASE_URL": "<MCP_API_BASE_URL>",
"MCP_AUTH_USER_KEY": "<MCP_AUTH_USER_KEY>"
}
}
}
}
Put your own values in place of
<MCP_API_BASE_URL> (Upstream API root. Required: your user key is exchanged for a session token against this host, and the server will not start without it), <MCP_AUTH_USER_KEY> (Long-lived EAD Enterprise Suite user key, exchanged automatically for a short-lived session token. Use it for headless or automated access instead of an account password. (See https://www.eadtrust.eu/soluciones-legaltech/enterprise-suite/ for credential acquisition.)).
The author’s registry entry marks them as required.
Optional settings from the registry entry, left out of the block above:
MCP_ALLOW_INSECURE_FILE_URL (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)), MCP_ALLOW_UNVERIFIED_BEARER (Escape hatch for MCP_HTTP_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), MCP_ALLOWED_HOSTS (Comma-separated allowed Host headers. Empty = Host validation disabled (default). When set, requests with a Host outside the list are rejected), MCP_ALLOWED_ORIGINS (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), MCP_HTTP_HOST (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)), MCP_HTTP_MAX_BODY_BYTES (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 MCP_FILE_MAX_BYTES applies), MCP_HTTP_PUBLIC (Set to "true" for public/multi-tenant deployments. Activates Host validation and refuses to start unless (1) MCP_ALLOWED_ORIGINS or MCP_ALLOWED_HOSTS is set AND (2) inbound Bearer introspection is configured (MCP_SVC_INTROSPECT_URL + MCP_SVC_CLIENT_ID/SECRET) or MCP_ALLOW_UNVERIFIED_BEARER=true is set explicitly (fail-closed)), MCP_SVC_CLIENT_ID (Client ID this server presents to the introspection endpoint above (its resource-server credentials). Only needed alongside MCP_SVC_INTROSPECT_URL; it does not authenticate you to EAD Enterprise Suite), MCP_SVC_CLIENT_SECRET (Client secret this server presents to the introspection endpoint above (its resource-server credentials). Only needed alongside MCP_SVC_INTROSPECT_URL; it does not authenticate you to EAD Enterprise Suite. (See https://www.eadtrust.eu/soluciones-legaltech/enterprise-suite/ for credential acquisition.)), MCP_SVC_INTROSPECT_URL (RFC 7662 token introspection URL for inbound Bearer verification in HTTP mode. Opt-in, and required when MCP_HTTP_PUBLIC=true. Leave empty for stdio (local) use), PORT (HTTP port when running in hosted (HTTP) mode; ignored in stdio mode).
MCP server for EAD Factory: qualified evidence, signature, notifications and chat via AI agents.
MCP server for GoCertius: certified evidence, dossiers, notifications and chats via AI agents.
MCP server for GroupDocs.Signature — sign, search and verify document signatures via AI agents.
MCP server for 1C Enterprise — ERP catalogs, documents via REST API (Russia)
An MCP Server that provides identity verification and anti-fraud tools for AI agents via deepidv.
Runtime verification MCP server: fail-closed checks for agent tool calls, signed evidence receipts.
Evidence-gated verification, selection, and measurement MCP for coding agents.
Tamper-evident proof creation and verification for AI agents via MCP, A2A, and REST.
Answers built from our own checks of this server.