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.
Available components
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
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
claude mcp add g-digital-by-garrigues-ead-enterprise-suite -- npx -y @g-digital/mcp-ead-enterprise-suite
codex mcp add g-digital-by-garrigues-ead-enterprise-suite -- npx -y @g-digital/mcp-ead-enterprise-suite
{
"$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
}
}
} openclaw mcp add g-digital-by-garrigues-ead-enterprise-suite --command npx --arg -y --arg @g-digital/mcp-ead-enterprise-suite
mcp_servers:
g-digital-by-garrigues-ead-enterprise-suite:
command: "npx"
args: ["-y", "@g-digital/mcp-ead-enterprise-suite"] {
"mcpServers": {
"g-digital-by-garrigues-ead-enterprise-suite": {
"command": "npx",
"args": [
"-y",
"@g-digital/mcp-ead-enterprise-suite"
]
}
}
} 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.
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.
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.
signature_request_get ~70
Retrieves full details of a signature request. Requires: signature_request_create → requestId, case_file_create → caseFileId. Returns status, documents, participants, deadline, and history. Use to check overall process state.
| Name | Type | Req | Description |
|---|---|---|---|
| caseFileId | string | yes | — |
| requestId | string | yes | — |
No output schema declared.
No examples provided.
use_case_list ~54
Lists available use cases for the account. Use cases define the allowed signature workflows and document types. Returns useCaseId values needed for signature_request_create.
| Name | Type | Req | Description |
|---|---|---|---|
| companyId | string | yes | — |
| page | object | — | — |
No output schema declared.
No examples provided.