ZapSign (unofficial)
NPM · ZAPSIGN-MCP
ZapSign e-signature API: reads run freely, writes ask first, personal data filtered out.
Available components
Last scanned (7 hours ago)
Scores higher than 49% of npm servers
Category Documents and Files
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 → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to BlancasJ/zapsign-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 7 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability68
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 687 tokens (~57/item across 12 items; 12 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage86
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 57% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 16 Oct 26 77
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 23 Oct 2026 · Analysed npm/zapsign-mcp@1.0.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | BlancasJ/zapsign-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/BlancasJ/zapsign-mcp/.github/workflows/publish.yml@refs/tags/v1.0.1 |
| Rekor log index | 3274498616 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:10862540b44e96feb3e7ab8879ca4638d9427816a1b3b63387a943c23097a3f6781afefe375ea52d3d5bebed4e52079c6bb4d21487ab5497a7b41e11d |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_background_check ~77
A background check by its id: who was checked, status (not_started, in_progress, delayed, error, completed), type, country, and whether its PDF report is ready. Ids, dates of birth and the report link stay in the log.
| Name | Type | Req | Description |
|---|---|---|---|
| check_id | string | yes | Id of the background check (CHK…) |
No output schema declared.
No examples provided.
get_background_check_details ~92
What each database consulted by a background check returned: database, result, severity, the name found and the labels of what it found. The values found stay in the log.
| Name | Type | Req | Description |
|---|---|---|---|
| check_id | string | yes | Id of the background check (CHK…) |
| lang | string | – | – |
| start_key | string | – | The next page: the start_key in the `next` of the previous answer |
No output schema declared.
No examples provided.
get_document ~40
One document by its token: status, dates, and each signer with their status and signed_at.
| Name | Type | Req | Description |
|---|---|---|---|
| doc_token | string | yes | Token of the document |
No output schema declared.
No examples provided.
get_document_audit_trail ~46
What happened to a document, event by event: who did what, when, and how they were authenticated.
| Name | Type | Req | Description |
|---|---|---|---|
| doc_token | string | yes | Token of the document |
No output schema declared.
No examples provided.
get_partner_plans_csv ~91
Partner API: a CSV with one row for this account and one for each partner account under it: plan, credits, status, and usage (documents, envelopes, SMS, WhatsApp, biometrics) over at most 30 days, the last 30 when no date is given.
| Name | Type | Req | Description |
|---|---|---|---|
| end_date | string | – | YYYY-MM-DD |
| start_date | string | – | YYYY-MM-DD |
No output schema declared.
No examples provided.
get_plan ~35
The account's plan: name, credits left, status (paid, pending_payment, unpaid, canceled), period and when it ends.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_signer ~39
One signer by their token: status, signed_at, views and how they must authenticate.
| Name | Type | Req | Description |
|---|---|---|---|
| signer_token | string | yes | Token of the signer |
No output schema declared.
No examples provided.
get_signer_validations ~71
Every identity validation a signer went through (document, selfie, name, CPF): its type, status, the reason it failed, and the name and number read from the identity document. Photos and the date of birth stay in the log.
| Name | Type | Req | Description |
|---|---|---|---|
| signer_token | string | yes | Token of the signer |
No output schema declared.
No examples provided.
get_template ~36
One template by its token: name, language, fields and first signer settings.
| Name | Type | Req | Description |
|---|---|---|---|
| template_token | string | yes | Token of the template |
No output schema declared.
No examples provided.
list_documents ~95
Documents of the account, one page at a time, newest first unless sort_order says otherwise.
| Name | Type | Req | Description |
|---|---|---|---|
| created_by | string | – | – |
| created_from | string | – | YYYY-MM-DD |
| created_to | string | – | YYYY-MM-DD |
| external_id | string | – | – |
| folder_path | string | – | – |
| page | integer | – | – |
| sort_order | string | – | – |
| status | string | – | – |
No output schema declared.
No examples provided.
list_templates ~26
Templates of the account, one page at a time.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | – |
No output schema declared.
No examples provided.
list_users ~39
Users of the organization, 25 a page: name, email, whether the email is verified, and permission group.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | – |
No output schema declared.
No examples provided.
How do I install the ZapSign (unofficial) MCP server?
ZapSign (unofficial) runs locally as an npm package, launched with npx -y zapsign-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · zapsign-mcp
claude mcp add blancasj-zapsign-mcp -- npx -y zapsign-mcp
What is the ZapSign (unofficial) MCP server?
ZapSign (unofficial) is an MCP server listed in the public MCP registry as io.github.BlancasJ/zapsign-mcp. ZapSign e-signature API: reads run freely, writes ask first, personal data filtered out. This page covers its npm package (zapsign-mcp).
Is the ZapSign (unofficial) MCP server safe to use?
ZapSign (unofficial) scores 77 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 23 October 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the ZapSign (unofficial) MCP server expose?
ZapSign (unofficial) exposes 12 tools: get_document, list_documents, get_document_audit_trail, get_signer, list_templates, and 7 more. Their descriptions and schemas cost roughly 687 tokens of context every time the server is loaded.
Is the ZapSign (unofficial) MCP server still maintained?
ZapSign (unofficial) is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the ZapSign (unofficial) MCP server under?
ZapSign (unofficial) declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.