br.com.signdocs/mcp-server

NPM · @SIGNDOCS-BRASIL/MCP-SERVER · 2 COMPONENTS · SCANNED AUG 3

SignDocs Brasil e-signature tools for AI agents — signing sessions, envelopes, verification.

Available components

remote · mcp.signdocs.com.br 36 npm · @signdocs-brasil/mcp-server 70

+18 this week 70 70 Trust /100

Trust breakdown (6 categories)

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 (96 of 100), 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 (96 of 100), 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
Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
Clear OSI-approved license (MIT).Pass
Actively maintained (last published 35 days ago).Pass
Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail

Schema Quality & AI Usability82

100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
AI-judged instruction clarity (good).Pass
Tool/resource definitions use about 2238 tokens (~86/item across 26 items; 23 tools + 3 resources), lean.Pass
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 Coverage95

100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
85% of tool parameters carry a description.Partial

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Install

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 · @signdocs-brasil/mcp-server

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add br-com-signdocs-mcp-server -- npx -y @signdocs-brasil/mcp-server

# add to Codex CLI

codex mcp add br-com-signdocs-mcp-server -- npx -y @signdocs-brasil/mcp-server

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "br-com-signdocs-mcp-server": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@signdocs-brasil/mcp-server"
      ],
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add br-com-signdocs-mcp-server --command npx --arg -y --arg @signdocs-brasil/mcp-server

# ~/.hermes/config.yaml

mcp_servers:
  br-com-signdocs-mcp-server:
    command: "npx"
    args: ["-y", "@signdocs-brasil/mcp-server"]

// mcp.json

{
  "mcpServers": {
    "br-com-signdocs-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@signdocs-brasil/mcp-server"
      ]
    }
  }
}

Changelog

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 +43
- Provenance: unverified → fail ▼ security
- Known CVEs: unverified → partial ▲ security
- Install scripts: unverified → pass ▲ security
- Malware scan: unverified → pass ▲ security
- Maintenance: unverified → pass ▲ functional
- License: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Schema quality: unverified → good ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Stability: unverified → 0.23 ▲ functional
- Licence: MIT functional
1 Aug 26 −8
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
31 Jul 26 −18
- Malware scan: pass → unverified ▼ security
27 Jul 26 52

First indexed and scored.

Show 2 earlier entries Hide earlier entries

Diagnostics

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/@signdocs-brasil/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Dependencies 96 packages

96 packages in the resolved dependency tree · 95 deprecated · 29 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 23 exposed · ~2,099 tokens

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.

Tool Tokens

add_session_to_envelope Add signer to envelope ~233

⚠️ This performs a consequential, possibly irreversible action (legally-binding signature request and/or quota consumption). Confirm with the human before calling. Add a signing session for one signer to an envelope. Returns IDs plus a ready-to-share `signingUrl`.

Input Output Examples

Name	Type	Req	Description
cancelUrl	string	—	—
envelopeId	string	yes	The envelope to add a signer to.
metadata	object	—	Free-form key/value tags (keys ≤256, values ≤1024 chars).
policyProfile	string	yes	Identity-assurance profile: CLICK_ONLY, CLICK_PLUS_OTP, BIOMETRIC, BIOMETRIC_PLUS_OTP, or CUSTOM. Read the signdocs://policy-profiles resource for the authoritative list — an invalid value returns 40…
purpose	string	—	DOCUMENT_SIGNATURE to sign a PDF; ACTION_AUTHENTICATION to authenticate an action with no document.
returnUrl	string	—	—
signer	object	yes	The person who will sign / authenticate.
signerIndex	integer	yes	Zero-based position of this signer (0..totalSigners-1).

No output schema declared.

No examples provided.

cancel_signing_session Cancel signing session ~67

⚠️ This performs a consequential, possibly irreversible action (legally-binding signature request and/or quota consumption). Confirm with the human before calling. Cancel an active signing session. This cannot be undone.

Input Output Examples

Name	Type	Req	Description
sessionId	string	yes	The signing session ID (sigex_…).

No output schema declared.

No examples provided.

cancel_transaction Cancel transaction ~63

Input Output Examples

Name	Type	Req	Description
transactionId	string	yes	The transaction ID (txn_…).

No output schema declared.

No examples provided.

create_envelope Create envelope ~272

⚠️ This performs a consequential, possibly irreversible action (legally-binding signature request and/or quota consumption). Confirm with the human before calling. Create a multi-signer envelope around one PDF. After creating, add each signer with add_session_to_envelope. Consumes quota.

Input Output Examples

Name	Type	Req	Description
cancelUrl	string	—	—
documentBase64	string	yes	Base64-encoded PDF (≤10MB) shared by all signers.
documentFilename	string	—	—
expiresInMinutes	integer	—	—
idempotencyKey	string	—	Idempotency key for safe retries; a UUID is generated if omitted.
locale	string	—	UI/email language. Default pt-BR.
metadata	object	—	Free-form key/value tags (keys ≤256, values ≤1024 chars).
owner	object	—	The requester (distinct from the signer). When set and signer.email differs, SignDocs auto-emails the signer an invite and notifies the owner on completion. Omit to deliver links yourself via webhook…
returnUrl	string	—	—
signingMode	string	yes	PARALLEL: anyone signs in any order. SEQUENTIAL: ordered.
totalSigners	integer	yes	How many signers will be added to this envelope.

No output schema declared.

No examples provided.

create_signing_session Create signing session ~431

⚠️ This performs a consequential, possibly irreversible action (legally-binding signature request and/or quota consumption). Confirm with the human before calling. Create a single-signer "express" signing (or action-authentication) session and return its IDs plus a ready-to-share `signingUrl` (url + embed token). Consumes signature quota.

Input Output Examples

Name	Type	Req	Description
action	object	—	What is being authenticated — used when purpose=ACTION_AUTHENTICATION.
cancelUrl	string	—	Redirect URL if the signer cancels.
customSteps	array	—	Ordered step types — REQUIRED only when policyProfile=CUSTOM (e.g. ["CLICKWRAP","OTP"]).
documentBase64	string	—	Base64-encoded PDF (≤10MB). Required when purpose=DOCUMENT_SIGNATURE.
documentFilename	string	—	Original filename, e.g. contrato.pdf.
expiresInMinutes	integer	—	Session lifetime, 5–1440 min (default 60).
idempotencyKey	string	—	Idempotency key for safe retries; a UUID is generated if omitted.
locale	string	—	UI/email language. Default pt-BR.
metadata	object	—	Free-form key/value tags (keys ≤256, values ≤1024 chars).
owner	object	—	The requester (distinct from the signer). When set and signer.email differs, SignDocs auto-emails the signer an invite and notifies the owner on completion. Omit to deliver links yourself via webhook…
policyProfile	string	yes	Identity-assurance profile: CLICK_ONLY, CLICK_PLUS_OTP, BIOMETRIC, BIOMETRIC_PLUS_OTP, or CUSTOM. Read the signdocs://policy-profiles resource for the authoritative list — an invalid value returns 40…
purpose	string	yes	DOCUMENT_SIGNATURE to sign a PDF; ACTION_AUTHENTICATION to authenticate an action with no document.
returnUrl	string	—	Redirect URL after completion (sessionId appended as query param).
signer	object	yes	The person who will sign / authenticate.

No output schema declared.

No examples provided.

delete_webhook Delete webhook ~64

⚠️ This performs a consequential, possibly irreversible action (legally-binding signature request and/or quota consumption). Confirm with the human before calling. Delete a registered webhook. Event delivery to it stops immediately.

Input Output Examples

Name	Type	Req	Description
webhookId	string	yes	The webhook ID to act on.

No output schema declared.

No examples provided.

download_document Download document ~37

Get presigned download URLs for a transaction’s document and signed artifacts.

Input Output Examples

Name	Type	Req	Description
transactionId	string	yes	The transaction ID (txn_…).

No output schema declared.

No examples provided.

get_envelope Get envelope ~37

Get envelope details including per-signer session summaries and completion counts.

Input Output Examples

Name	Type	Req	Description
envelopeId	string	yes	The envelope ID (env_…).

No output schema declared.

No examples provided.

get_envelope_combined_stamp Get envelope combined stamp ~48

Generate the combined stamped PDF (all signers) for a COMPLETED envelope and return a download URL.

Input Output Examples

Name	Type	Req	Description
envelopeId	string	yes	The envelope ID (env_…).

No output schema declared.

No examples provided.

get_evidence Get evidence ~44

Retrieve the cryptographic evidence (hashes, step proofs, evidenceId) for a completed transaction.

Input Output Examples

Name	Type	Req	Description
transactionId	string	yes	The transaction ID (txn_…).

No output schema declared.

No examples provided.

get_signing_session Get signing session details ~45

Get full bootstrap data for a signing session (signer, steps, document, appearance).

Input Output Examples

Name	Type	Req	Description
sessionId	string	yes	The signing session ID (sigex_…).

No output schema declared.

No examples provided.

get_signing_session_status Get signing session status ~51

Poll the current status of a signing session (ACTIVE/COMPLETED/CANCELLED/EXPIRED/FAILED).

Input Output Examples

Name	Type	Req	Description
sessionId	string	yes	The signing session ID (sigex_…).

No output schema declared.

No examples provided.

get_transaction Get transaction ~37

Get full details of a single transaction, including its steps and results.

Input Output Examples

Name	Type	Req	Description
transactionId	string	yes	The transaction ID (txn_…).

No output schema declared.

No examples provided.

list_signing_sessions List signing sessions ~74

List signing sessions filtered by status, with cursor pagination.

Input Output Examples

Name	Type	Req	Description
cursor	string	—	Pagination cursor from a previous response (nextCursor).
limit	integer	—	Page size (default server value).
status	string	yes	Filter by status: ACTIVE, COMPLETED, CANCELLED, EXPIRED, or FAILED.

No output schema declared.

No examples provided.

list_transactions List / find transactions ~129

Search transactions by status, signer external ID, document group, or date range (cursor pagination). Use this to find a transaction or check signing history.

Input Output Examples

Name	Type	Req	Description
documentGroupId	string	—	—
endDate	string	—	ISO date upper bound.
limit	integer	—	—
nextToken	string	—	Pagination token from a previous response.
startDate	string	—	ISO date lower bound.
status	string	—	Filter by transaction status (e.g. PENDING, COMPLETED, CANCELLED).
userExternalId	string	—	Filter by signer external ID.

No output schema declared.

No examples provided.

list_webhooks List webhooks ~18

List all registered webhooks for the tenant.

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

register_webhook Register webhook ~79

Register an HTTPS endpoint to receive event notifications. The response returns a signing secret — store it to verify the HMAC-SHA256 signature on incoming payloads.

Input Output Examples

Name	Type	Req	Description
events	array	yes	Event types to subscribe to. The response returns a signing secret for HMAC verification.
url	string	yes	HTTPS endpoint that will receive event POSTs.

No output schema declared.

No examples provided.

resend_signing_session_otp Resend signing session OTP ~55

Resend the OTP challenge for a signing session, optionally over a specific channel (email/sms).

Input Output Examples

Name	Type	Req	Description
channel	string	—	Override OTP delivery channel.
sessionId	string	yes	The signing session ID.

No output schema declared.

No examples provided.

test_webhook Test webhook ~37

Send a sample payload to a registered webhook and return the delivery result.

Input Output Examples

Name	Type	Req	Description
webhookId	string	yes	The webhook ID to act on.

No output schema declared.

No examples provided.

upload_document Upload document ~74

Upload a base64-encoded PDF to an existing transaction (≤10MB inline; use presign for larger).

Input Output Examples

Name	Type	Req	Description
documentBase64	string	yes	Base64-encoded PDF (≤10MB).
filename	string	—	—
transactionId	string	yes	Transaction to attach the document to (txn_…).

No output schema declared.

No examples provided.

verify_document Verify document signatures ~97

⚠️ This performs a consequential, possibly irreversible action (legally-binding signature request and/or quota consumption). Confirm with the human before calling. Inspect an uploaded PDF for embedded electronic/digital signatures. Requires PRODUCTION credentials + the verification:write scope and CONSUMES verification quota. Not available in HML.

Input Output Examples

Name	Type	Req	Description
documentBase64	string	yes	Base64-encoded PDF to inspect for embedded signatures.
filename	string	—	—

No output schema declared.

No examples provided.

verify_envelope Verify envelope (public) ~43

Publicly verify all signers of an envelope and get consolidated download URLs.

Input Output Examples

Name	Type	Req	Description
envelopeId	string	yes	Envelope ID to verify all signers for. Public endpoint.

No output schema declared.

No examples provided.

verify_evidence Verify evidence (public) ~64

Publicly verify a completed signature by its evidenceId. Returns status, document/evidence hashes, steps and signer display info. No authentication needed.

Input Output Examples

Name	Type	Req	Description
evidenceId	string	yes	Evidence ID (evd_…) to verify. Public — no signer PII is revealed.

No output schema declared.

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

27 Jul 3 Aug