io.github.g-digital-by-Garrigues/gocertius
NPM · @G-DIGITAL/MCP-GOCERTIUS · SCANNED AUG 3
MCP server for GoCertius: certified evidence, dossiers, notifications and chats 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 Usability61
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 4966 tokens (~121/item across 41 items; 41 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 Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 13% 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-gocertius
claude mcp add g-digital-by-garrigues-gocertius -- npx -y @g-digital/mcp-gocertius
codex mcp add g-digital-by-garrigues-gocertius -- npx -y @g-digital/mcp-gocertius
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"g-digital-by-garrigues-gocertius": {
"type": "local",
"command": [
"npx",
"-y",
"@g-digital/mcp-gocertius"
],
"enabled": true
}
}
} openclaw mcp add g-digital-by-garrigues-gocertius --command npx --arg -y --arg @g-digital/mcp-gocertius
mcp_servers:
g-digital-by-garrigues-gocertius:
command: "npx"
args: ["-y", "@g-digital/mcp-gocertius"] {
"mcpServers": {
"g-digital-by-garrigues-gocertius": {
"command": "npx",
"args": [
"-y",
"@g-digital/mcp-gocertius"
]
}
}
} 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 +4
- Stability: unverified → 0.27 ▲ functional
- 2 Aug 26 +29
- Known CVEs: unverified → partial ▲ security
- Install scripts: unverified → pass ▲ 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
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Security disclosure: fail → unverified ▼ functional
- Dependency health: unverified → partial ▲ functional
- License: unverified → pass ▲ functional
- Maintenance: unverified → pass ▲ functional
- Licence: MIT functional
- 31 Jul 26 +24
- 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 −66
- Known CVEs: partial → unverified ▼ security
- Malware scan: pass → unverified ▼ security
- Install scripts: pass → unverified ▼ security
- Provenance: Build provenance not yet verified. security
- Dependency health: partial → unverified ▼ functional
- License: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Maintenance: pass → unverified ▼ functional
- Licence: MIT functional
- 28 Jul 26 +46
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ 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: unverified → fail ▼ functional
- Maintenance: unverified → pass ▲ functional
- License: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: good functional
- First check of Tool coverage: 13 functional
- First check of Schema quality: fail functional
- First check of Schema quality: fail functional
- Licence: MIT functional
- 27 Jul 26 26
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:
- 2218221499
- Predicate type:
- https://slsa.dev/provenance/v1
- Subject digest:
- sha512:57cd12274d5de8b03b0db1e4db51a0bdd143894488ac19808ded13e68c5676d1feb5948626431fb6608ce70b8a4324d0878a1542694af43b22f743351
- 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.
case_file_create ~147
Creates a new case file — the top-level container for all related operations (evidence, notifications, dossiers, chats). Call this first before any other operation. Generate a UUID v4 for `id`. For `useCaseId`, use the general GoCertius use case: `063a016a-1d62-4b7b-a24f-7cf4d1d289bf` unless a specific use case is required. Returns caseFileId needed for all subsequent calls.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | — | — |
| id | string | yes | — |
| name | string | yes | — |
| reference | string | — | — |
| useCaseId | string | yes | — |
No output schema declared.
No examples provided.
case_file_get ~49
Retrieves details of a specific case file. Requires: caseFileId. Use to verify a case file exists before creating evidence groups, dossiers, or notifications.
| Name | Type | Req | Description |
|---|---|---|---|
| caseFileId | string | yes | — |
No output schema declared.
No examples provided.
case_file_list ~79
Lists all case files in your GoCertius account. Pass userId (from session_login or session_info) to scope results to your account. Returns paginated list with IDs, names, and status.
| Name | Type | Req | Description |
|---|---|---|---|
| filter | object | — | — |
| order | object | — | — |
| page | object | — | — |
| userId | string | yes | — |
No output schema declared.
No examples provided.
chat_certificate_create ~175
Creates a certificate of a range of messages from a certified chat. Requires: chat_create → chatId, personal caseFileId, chat_get → registeredAt, and messages already present in the Telegram channel. Generate a UUID v4 for `id`. Do not use createdAt as a substitute for registeredAt; if registeredAt is missing, the chat is not ready to certify. Specify chatMessagesFrom and chatMessagesTo as ISO timestamps (chatMessagesFrom must be AFTER registeredAt). ASYNC: poll chat_certificate_get until status === CERTIFIED.
| Name | Type | Req | Description |
|---|---|---|---|
| caseFileId | string | yes | — |
| chatId | string | yes | — |
| chatMessagesFrom | string | yes | — |
| chatMessagesTo | string | yes | — |
| id | string | yes | — |
| language | string | yes | — |
| name | string | yes | — |
No output schema declared.
No examples provided.
chat_certificate_get ~115
Retrieves a certified chat certificate including its status, message range, and PDF download URL. Prerequisites: the certificate must have been created with chat_certificate_create. Returns documentUrl when status is CERTIFIED. Example: chat_certificate_get({ caseFileId: '...', chatId: '...', id: '...' })
| Name | Type | Req | Description |
|---|---|---|---|
| caseFileId | string | yes | UUID of the case file that owns the chat |
| chatId | string | yes | UUID of the chat |
| id | string | yes | UUID of the certificate to retrieve |
No output schema declared.
No examples provided.
chat_create ~172
Creates a certified chat channel (Telegram). IMPORTANT: Chats can only be created in the user's personal case file (created automatically when the GoCertius account was opened). Do not use a manually created case file — use session_info → case_file_list to find the personal case file (oldest createdAt, owned by the user). Generate a UUID v4 for `id`. Set service to Telegram. Returns immediately and the chat may start in status `creating`; call chat_get and wait until it is registered/active before requesting the invitation URL or certificates.
| Name | Type | Req | Description |
|---|---|---|---|
| caseFileId | string | yes | — |
| id | string | yes | — |
| language | string | yes | — |
| service | string | yes | — |
| serviceDescription | string | — | — |
| serviceTitle | string | — | — |
| title | string | yes | — |
No output schema declared.
No examples provided.
chat_get ~83
Retrieves details of a certified chat. Requires: personal caseFileId and chat_create → chatId. Returns status, participants, and registeredAt timestamp. After chat_create, poll chat_get until status is active/registered and registeredAt is present; createdAt is not enough for certificate creation.
| Name | Type | Req | Description |
|---|---|---|---|
| caseFileId | string | yes | — |
| chatId | string | yes | — |
No output schema declared.
No examples provided.
chat_invitation_url ~96
Returns the Telegram invitation URL for a certified chat. Requires: chat_create → chatId and the personal caseFileId. Do not call while chat_get still shows status `creating`; wait until the chat is registered/active, otherwise the API can answer Chat not found. Share the returned invitationUrl with participants so they can join the certified channel.
| Name | Type | Req | Description |
|---|---|---|---|
| caseFileId | string | yes | — |
| chatId | string | yes | — |
No output schema declared.
No examples provided.
dossier_certify ~149
Certifies a DRAFT dossier, locking in all its associated evidence groups. The dossier must be in DRAFT status. After certification it transitions to CERTIFIED and a tamper-evident PDF is generated. Prerequisites: the dossier must exist (dossier_create) and have evidence groups linked. Use dossier_group_certify instead if you want to create + certify in one step from a single evidence group. Example: dossier_certify({ caseFileId: '...', dossierId: '...' })
| Name | Type | Req | Description |
|---|---|---|---|
| caseFileId | string | yes | UUID of the case file that owns this dossier |
| dossierId | string | yes | UUID of the dossier to certify (must be in DRAFT status) |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| accessToken | string | — | — |
| caseFileId | string | yes | — |
| dossierTemplateId | string | — | — |
| filledFields | object | — | — |
| id | string | yes | — |
| language | string | yes | — |
| modelId | string | — | — |
| name | string | yes | — |
| purpose | string | — | — |
| validityFrom | string | yes | — |
| validityTo | string | yes | — |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| caseFileId | string | yes | — |
| dossierId | string | yes | — |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| caseFileId | string | yes | — |
| dossierId | string | yes | — |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| caseFileId | string | yes | — |
| dossierEvidenceGroupId | string | yes | — |
| dossierEvidenceId | string | yes | — |
| dossierId | string | yes | — |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| caseFileId | string | yes | — |
| dossierEvidenceGroupId | string | yes | — |
| dossierEvidenceId | string | yes | — |
| dossierId | string | yes | — |
No output schema declared.
No examples provided.
dossier_evidence_link ~182
Links specific evidence items to a DRAFT dossier. Call once per case file containing evidences to link. After linking all evidences, call dossier_certify to finalize. For a single-group dossier, use dossier_group_certify instead (one step). Example: dossier_evidence_link({ caseFileId: '...', dossierId: '...', caseFileToLinkId: '...', ids: ['ev-uuid-1', 'ev-uuid-2'] })
| Name | Type | Req | Description |
|---|---|---|---|
| caseFileId | string | yes | UUID of the case file that owns the dossier |
| caseFileToLinkId | string | yes | UUID of the case file containing the evidences (often same as caseFileId) |
| dossierId | string | yes | UUID of the DRAFT dossier to link evidences to |
| ids | array | yes | UUIDs of the evidence items to link |
No output schema declared.
No examples provided.
dossier_evidence_list ~76
Lists all evidence items linked to a dossier. Requires: caseFileId and dossierId.
| Name | Type | Req | Description |
|---|---|---|---|
| caseFileId | string | yes | — |
| dossierEvidenceGroupId | string | yes | — |
| dossierId | string | yes | — |
| filter | object | — | — |
| order | object | — | — |
| page | object | — | — |
No output schema declared.
No examples provided.
dossier_evidence_list_to_link ~90
Lists evidence items that are available to be linked to a dossier (CLOSED groups not yet linked). Requires: caseFileId and dossierId.
| Name | Type | Req | Description |
|---|---|---|---|
| caseFileId | string | yes | — |
| caseFileToLinkId | string | yes | — |
| dossierId | string | yes | — |
| filter | object | — | — |
| order | object | — | — |
| page | object | — | — |
No output schema declared.
No examples provided.
dossier_get ~66
Retrieves the full details of a specific dossier including status, linked evidence, and download URLs. Use to check current state or get certificate download URLs after CERTIFIED. Requires: caseFileId and dossierId.
| Name | Type | Req | Description |
|---|---|---|---|
| caseFileId | string | yes | — |
| dossierId | string | yes | — |
No output schema declared.
No examples provided.
dossier_group_certify ~151
Creates AND certifies a dossier from a single sealed evidence group in one call (express path). Requires: evidence_seal (CLOSED status), case_file_create → caseFileId, evidence_group_create → evidenceGroupId. Generate a UUID v4 string for `id`. Use when you have exactly one sealed evidence group and don't need multi-group aggregation. Returns dossierId immediately with CERTIFYING status → poll until CERTIFIED.
| Name | Type | Req | Description |
|---|---|---|---|
| caseFileId | string | yes | — |
| evidenceGroupId | string | yes | — |
| evidenceIds | array | — | — |
| id | string | yes | — |
| language | string | yes | — |
| modelId | string | — | — |
| name | string | yes | — |
No output schema declared.
No examples provided.
dossier_list ~84
Lists all dossiers in a case file with their status and metadata. Use to find an existing dossierId or monitor certification progress. Requires: caseFileId. Returns paginated list with IDs, names, status, and creation dates.
| Name | Type | Req | Description |
|---|---|---|---|
| caseFileId | string | yes | — |
| filter | object | — | — |
| order | object | — | — |
| page | object | — | — |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| caseFileId | string | yes | — |
| dossierId | string | yes | — |
No output schema declared.
No examples provided.
dossier_preview ~45
Returns an HTML preview URL of a dossier before certification. Requires: caseFileId and dossierId.
| Name | Type | Req | Description |
|---|---|---|---|
| caseFileId | string | yes | — |
| dossierId | string | yes | — |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| page | object | — | — |
No output schema declared.
No examples provided.
dossier_update ~132
Updates the metadata of an existing dossier (name, template fields, expiry). Requires: dossier_create → dossierId, caseFileId. Only available while dossier is in DRAFT status.
| Name | Type | Req | Description |
|---|---|---|---|
| accessToken | string | — | — |
| caseFileId | string | yes | — |
| dossierId | string | yes | — |
| dossierTemplateId | string | — | — |
| filledFields | object | — | — |
| language | string | — | — |
| modelId | string | — | — |
| name | string | — | — |
| purpose | string | — | — |
| validityFrom | string | — | — |
| validityTo | string | — | — |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| caseFileId | string | yes | — |
| dossierId | string | yes | — |
| visibility | string | yes | — |
No output schema declared.
No examples provided.
evidence_create ~421
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.
| Name | Type | Req | Description |
|---|---|---|---|
| caseFileId | string | yes | UUID of the case file |
| custodyType | string | — | INTERNAL = GoCertius stores the file; EXTERNAL = only hash registered |
| evidenceGroupId | string | yes | UUID of the evidence group |
| fileName | string | yes | Original file name including extension |
| fileUrl | string | — | Optional 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. |
| hash | string | yes | SHA-256 hex digest of the file content (64 hex chars) |
| id | string | yes | UUID v4 for the new evidence record (idempotency key) |
| title | string | yes | Human-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.
| Name | Type | Req | Description |
|---|---|---|---|
| caseFileId | string | yes | — |
| evidenceGroupId | string | yes | — |
| id | string | yes | — |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| attestation | object | — | — |
| caseFileId | string | yes | — |
| description | string | — | — |
| evidenceType | string | yes | — |
| id | string | yes | — |
| name | string | yes | — |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| caseFileId | string | yes | — |
| filter | object | — | — |
| order | object | — | — |
| page | object | — | — |
No output schema declared.
No examples provided.
evidence_list ~99
Lists all evidence records in a specific evidence group. Use to review uploaded documents before sealing the group, or to find a specific evidenceId. Requires: caseFileId and evidenceGroupId. Returns paginated list with IDs, titles, status, and timestamps.
| Name | Type | Req | Description |
|---|---|---|---|
| caseFileId | string | yes | — |
| evidenceGroupId | string | yes | — |
| filter | object | — | — |
| order | object | — | — |
| page | object | — | — |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| altitudeLocation | string | — | — |
| attestation | object | — | — |
| caseFileId | string | yes | — |
| deviceManufacturer | string | — | — |
| deviceModel | string | — | — |
| deviceOS | string | — | — |
| evidencesCount | number | yes | — |
| id | string | yes | — |
| latitudeLocation | string | — | — |
| locationAccuracy | string | — | — |
| longitudeLocation | string | — | — |
| userAgent | string | — | — |
| webUrl | string | — | — |
No output schema declared.
No examples provided.
evidence_upload ~377
Uploads a local file as evidence in one step: computes its SHA-256, registers the evidence record (custodyType INTERNAL = GoCertius stores the file), and uploads the bytes to S3 — no manual hashing or PUT needed. Internally this follows the required GoCertius 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.
| Name | Type | Req | Description |
|---|---|---|---|
| caseFileId | string | yes | UUID of the case file |
| contentBase64 | string | — | Base64-encoded file content (~10 MB max). The tool will create evidence, receive uploadFileUrl, and PUT these bytes to it. |
| evidenceGroupId | string | yes | UUID of the evidence group |
| fileName | string | yes | File name including extension |
| filePath | string | — | Absolute local path to the file (stdio/local mode only). The tool will create evidence, receive uploadFileUrl, and PUT this file to it. |
| title | string | yes | Human-readable title for the evidence |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| caseFileId | string | yes | — |
| id | string | yes | — |
| language | string | — | — |
| notificationRequestId | string | yes | — |
| receiverId | string | yes | — |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| caseFileId | string | yes | — |
| fileName | string | yes | — |
| fileSize | number | — | — |
| hash | string | yes | — |
| id | string | yes | — |
| notificationRequestId | string | yes | — |
No output schema declared.
No examples provided.
notification_receiver_add ~158
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 (e.g. your internal user ID). Returns receiverId — save it for notification_certificate_get. Add all receivers before calling notification_request_send.
| Name | Type | Req | Description |
|---|---|---|---|
| caseFileId | string | yes | — |
| string | yes | — | |
| firstName | string | yes | — |
| id | string | yes | — |
| lastName | string | yes | — |
| notificationRequestId | string | yes | — |
| otpRequired | boolean | — | — |
| phoneNumber | string | — | — |
| phonePrefix | string | — | — |
| sendWaUrl | boolean | — | — |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| caseFileId | string | yes | — |
| content | string | yes | — |
| id | string | yes | — |
| language | string | yes | — |
| otpByDefault | boolean | — | — |
| sendWaUrlByDefault | boolean | — | — |
| subject | string | yes | — |
| type | string | — | — |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| caseFileId | string | yes | — |
| notificationRequestId | string | yes | — |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| caseFileId | string | yes | — |
| notificationRequestId | string | yes | — |
No output schema declared.
No examples provided.
profile_get ~145
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 (the personal case file — the one chats must use). 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 ~68
Authenticate with GoCertius. 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.