# ZapSign (unofficial) (npm · zapsign-mcp)

ZapSign e-signature API: reads run freely, writes ask first, personal data filtered out.

- Trust score: 77/100 (medium)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-23

## Components

- npm · `zapsign-mcp`: 77/100 (this document), [markdown](https://verifymcp.io/servers/blancasj-zapsign-mcp/zapsign-mcp.md), [page](https://verifymcp.io/servers/blancasj-zapsign-mcp/zapsign-mcp)

## Channel facts

- Registry: `npm`
- Package: `zapsign-mcp`
- Version: `1.0.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-23.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to BlancasJ/zapsign-mcp).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 7 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 68/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 687 tokens (~57/item across 12 items; 12 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 86/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 57% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

**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.

## Install

### 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.

### Claude

```bash
claude mcp add blancasj-zapsign-mcp -- npx -y zapsign-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "blancasj-zapsign-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "zapsign-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "blancasj-zapsign-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "zapsign-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add blancasj-zapsign-mcp -- npx -y zapsign-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "blancasj-zapsign-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "zapsign-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add blancasj-zapsign-mcp --command npx --arg -y --arg zapsign-mcp
```

### Hermes

```yaml
mcp_servers:
  blancasj-zapsign-mcp:
    command: "npx"
    args: ["-y", "zapsign-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "blancasj-zapsign-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "zapsign-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add blancasj-zapsign-mcp -t stdio -c npx -a -y zapsign-mcp
```

### Other

```json
{
  "mcpServers": {
    "blancasj-zapsign-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "zapsign-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-16 (score 77)

First indexed and scored.

## MCP tools (12)

### `get_document` (~40 tokens)

One document by its token: status, dates, and each signer with their status and signed_at.

Input parameters:

- `doc_token` (string, required): Token of the document

### `list_documents` (~95 tokens)

Documents of the account, one page at a time, newest first unless sort_order says otherwise.

Input parameters:

- `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)

### `get_document_audit_trail` (~46 tokens)

What happened to a document, event by event: who did what, when, and how they were authenticated.

Input parameters:

- `doc_token` (string, required): Token of the document

### `get_signer` (~39 tokens)

One signer by their token: status, signed_at, views and how they must authenticate.

Input parameters:

- `signer_token` (string, required): Token of the signer

### `list_templates` (~26 tokens)

Templates of the account, one page at a time.

Input parameters:

- `page` (integer)

### `get_template` (~36 tokens)

One template by its token: name, language, fields and first signer settings.

Input parameters:

- `template_token` (string, required): Token of the template

### `get_signer_validations` (~71 tokens)

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.

Input parameters:

- `signer_token` (string, required): Token of the signer

### `get_plan` (~35 tokens)

The account's plan: name, credits left, status (paid, pending_payment, unpaid, canceled), period and when it ends.

### `list_users` (~39 tokens)

Users of the organization, 25 a page: name, email, whether the email is verified, and permission group.

Input parameters:

- `page` (integer)

### `get_partner_plans_csv` (~91 tokens)

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.

Input parameters:

- `end_date` (string): YYYY-MM-DD
- `start_date` (string): YYYY-MM-DD

### `get_background_check` (~77 tokens)

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.

Input parameters:

- `check_id` (string, required): Id of the background check (CHK…)

### `get_background_check_details` (~92 tokens)

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.

Input parameters:

- `check_id` (string, required): Id of the background check (CHK…)
- `lang` (string)
- `start_key` (string): The next page: the start_key in the `next` of the previous answer

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/blancasj-zapsign-mcp/zapsign-mcp#diagnostics

## Score history

- 2026-10-23: 77
- 2026-10-22: 77
- 2026-10-21: 77
- 2026-10-20: 77
- 2026-10-19: 77
- 2026-10-18: 77
- 2026-10-17: 77
- 2026-10-16: 77

## Common questions

### 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.

## Links

- npm package: https://www.npmjs.com/package/zapsign-mcp
- Socket report: https://socket.dev/npm/package/zapsign-mcp
- Repository: https://github.com/BlancasJ/zapsign-mcp
- Changelog RSS feed: https://verifymcp.io/servers/blancasj-zapsign-mcp/zapsign-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/blancasj-zapsign-mcp/zapsign-mcp.json
- HTML version of this page: https://verifymcp.io/servers/blancasj-zapsign-mcp/zapsign-mcp