# io.zsign/zsign (remote · zsign.io)

Send documents for e-signature from AI assistants, track signers, and download sealed, signed PDFs.

- Trust score: 66/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `zsign.io`: 66/100 (this document), [markdown](https://verifymcp.io/servers/io-zsign-zsign/mcp-open.md), [page](https://verifymcp.io/servers/io-zsign-zsign/mcp-open)
- remote · `zsign.io`: 36/100, [markdown](https://verifymcp.io/servers/io-zsign-zsign/zsign.md), [page](https://verifymcp.io/servers/io-zsign-zsign/zsign)

## Channel facts

- Endpoint: `https://zsign.io/mcp/open`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.4`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-11-21.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (delete_draft).
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 73/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 4870 tokens (~162/item across 30 items; 29 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 5 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 31 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the io.zsign/zsign MCP server?

io.zsign/zsign is a hosted endpoint at https://zsign.io/mcp/open, so there is nothing to install locally. 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 --transport http io-zsign-zsign 'https://zsign.io/mcp/open'
```

### Cursor

```json
{
  "mcpServers": {
    "io-zsign-zsign": {
      "url": "https://zsign.io/mcp/open"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-zsign-zsign": {
      "type": "http",
      "url": "https://zsign.io/mcp/open"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-zsign-zsign]
url = "https://zsign.io/mcp/open"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-zsign-zsign": {
      "type": "remote",
      "url": "https://zsign.io/mcp/open",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-zsign-zsign --url 'https://zsign.io/mcp/open' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-zsign-zsign:
    url: "https://zsign.io/mcp/open"
```

### Netclaw

```json
{
  "McpServers": {
    "io-zsign-zsign": {
      "Transport": "http",
      "Url": "https://zsign.io/mcp/open"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-zsign-zsign -t streamable-http -u 'https://zsign.io/mcp/open'
```

### Other

```json
{
  "mcpServers": {
    "io-zsign-zsign": {
      "type": "http",
      "url": "https://zsign.io/mcp/open"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-11-20 (score 66, 0)

- [security] Tool “correct_recipient_email” rewrote its description, which is the text the model reads
- [security] Tool “download_signed_document” rewrote its description, which is the text the model reads

### 2026-11-19 (score 66, +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.

### 2026-11-17 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-15 (score 64, +1)

- [security] Tool “prepare_document” rewrote its description, which is the text the model reads

### 2026-11-13 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-12 (score 62, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-11 (score 62)

First indexed and scored.

## MCP tools (29)

### `create_account` (~190 tokens)

Create Account

Create a zSign account and API key in one call. Email is optional.
    The returned key starts with zs_live_; pass it as
    `Authorization: Bearer <key>` on this MCP connection (or REST) for all
    other tools. Unverified accounts stay at 0 credits (anonymous-abuse
    guard). Pass an email, then POST /api/v1/email/verify with the mailed
    token (or click the link) to receive the same starting credits as a
    dashboard signup. After that, send_envelope works; buy_credits when you
    need more. `source` is an optional attribution ref (a short slug). Omit
    it and the account is created the same way as before. An invalid source
    is ignored and does not block signup.

Input parameters:

- `email`
- `name`
- `source`

Output parameters:

- `result` (string)

### `get_pricing` (~29 tokens)

Get Pricing

Credit packs and billing model (1 credit = 1 envelope send). No
    authentication required.

Output parameters:

- `result` (string)

### `get_account` (~119 tokens)

Get Account

Connected account: email, email_verified, name, organization id and
    name, and the credit balance from the same ledger as check_balance.
    auth.method is api_key or oauth, plus the scopes this call holds. An
    API key response includes key_prefix (the stored non-secret prefix)
    and never the key. OAuth responses set key_prefix to null and never
    return the token. Read-only, no credit charge. Accepts envelopes:read
    or credits:read. Requires `Authorization: Bearer zs_...`.

Output parameters:

- `result` (string)

### `check_balance` (~27 tokens)

Check Credit Balance

Current credit balance and available packs. Requires
    `Authorization: Bearer zs_...`.

Output parameters:

- `result` (string)

### `get_usage` (~94 tokens)

Get Usage

Daily credit-consumption report. start_date and end_date are
    inclusive UTC dates (YYYY-MM-DD). Returns 400 when
    (end_date - start_date).days >= 400. Rows are only days with an
    envelope debit, refund, or void_refund. Requires
    `Authorization: Bearer zs_...`.

Input parameters:

- `end_date` (string, required)
- `start_date` (string, required)

Output parameters:

- `result` (string)

### `get_referral_link` (~33 tokens)

Get Referral Link

This account's referral code and shareable referral link. Requires
    `Authorization: Bearer zs_...`.

Output parameters:

- `result` (string)

### `buy_credits` (~78 tokens)

Buy Credits

Create a Stripe Checkout session for a credit pack ('starter',
    'growth', or 'scale' — see get_pricing). Returns a checkout_url: open
    and pay it (card), and the webhook credits this account automatically
    within seconds. Requires `Authorization: Bearer zs_...`.

Input parameters:

- `pack` (string, required)

Output parameters:

- `result` (string)

### `send_envelope` (~1012 tokens)

Send Envelope for Signature

Send a PDF for legally binding signature, or leave it as a Draft for a human to approve. Immediate send costs 1 credit. Provide the PDF either as document_base64 OR as a public https document_url (max 10MB). recipients = [{"name": "...", "email": "...", "role": "signer"}]. Each recipient gets a signing email; poll get_envelope_status for progress. Requires `Authorization: Bearer zs_...`.

auto_send defaults true (existing one-tool send). Set auto_send=false or draft=true to create a Draft: status Draft, no credit debit, no invite emails. draft=true always wins if both flags are set. Then a human Approves/Sends in the dashboard, or call send_draft.

Immediate send: the PDF is REJECTED unless it contains signing-field placeholder tags. For an untagged PDF (no zSign field tags), call prepare_document first to place the fields, call it again with that prepare_id and approve true when the response has no PDF, then send the pdf_base64 it returns as document_base64. Draft mode accepts an untagged PDF (human places fields) or optional `fields`.
zSign field placeholder syntax:
\- Format: {type:party:name} -- add * after the type to mark the field required, e.g. {signature*:signer}
\- On upload, a tag or PDF form field with no explicit required marker is required when the account's fields_required_by_default is true (the default) and optional when it is false; a * is always required. A JSON field list stores the required boolean you send (default false) and does not apply this setting.
\- Types: signature, initials, text, date, radio
\- party must exactly match the recipient's "role" value passed when sending (MCP default role is "signer")
\- name is optional for signature/initials/date and REQUIRED for text fields; letters, digits, and underscores only
\- radio fields take FOUR parts: {radio:party:group:option}. Every tag sharing a party and group forms one exclusive set -- the signer picks exactly one, and the chosen option is the value reported back. Mark the set required with…

Input parameters:

- `auto_send` (boolean)
- `document_base64`
- `document_url`
- `documents`
- `draft` (boolean)
- `fields`
- `filename` (string)
- `metadata`
- `name`
- `prefill`
- `recipients`
- `send_completion_email` (boolean)
- `send_invite` (boolean)
- `sequential` (boolean)

Output parameters:

- `result` (string)

### `prepare_document` (~328 tokens)

Prepare Document

Place signature, initials, date, and printed-name fields on an untagged PDF. Provide document_base64 or an https document_url (max 10MB). Optional signers hints: [{"name", "email", "role", "order"}]. Until the user has approved one preview, every call returns status preview with confidence, reasons, fields, pages, and prepare_id, and no PDF. pages lists each page's visible area (x, y, width, height) in the same coordinates a field position uses. Show it to the user, then call again with that prepare_id and approve true to get pdf_base64. A prepare_id expires 15 minutes after the preview; approve within that window or call prepare_document again. After that first approval, a call returns status ready and pdf_base64 when confidence is at least 0.85, and a preview otherwise. Creates no envelope and charges no credit. Radio and checkbox are not placed. A filled form field that is not a zSign tag is a 422 with code filled_form_field. Encrypted PDFs are refused. Flatten or clear filled form fields first, since zSign may not catch every one. An encrypted PDF is a 422 with code pdf_encrypted. An expired prepare_id is a 404 with code prepare_expired. An unknown prepare_id is a 404 with code prepare_not_found. Requires `Authorization: Bearer zs_...`.

Input parameters:

- `approve` (boolean)
- `document_base64`
- `document_url`
- `prepare_id`
- `signers`

Output parameters:

- `result` (string)

### `update_draft` (~134 tokens)

Update Draft Fields

Replace the fields on an unsent Draft. No credit debit, no invites.
    `fields` is a whole-list replace: [{type, party, name?, required,
    position: {page_number, x, y, width, height}}]. Text fields may also
    carry default_value (prefilled for the signer, who can edit it) and
    locked=true (signer cannot edit; needs default_value; not allowed on
    semantic_type "full_name"). Requires
    `Authorization: Bearer zs_...`.

Input parameters:

- `document_id` (string, required)
- `fields` (array, required)

Output parameters:

- `result` (string)

### `add_document_to_draft` (~198 tokens)

Add Document to Draft

Append a document to an existing Draft. Provide exactly one of document_base64, document_url, or template_id. A multi-document template inserts ALL of its documents (each counts toward the limit of 10) and `name` is then not allowed. `role_mapping` (template only) maps the template's roles onto this envelope's roles, e.g. {"customer": "client"}; unmapped roles are inserted as-is, never guessed. Fields already placed keep their pages; inserted pages come after them. Returns the draft with its `documents[]` (page ranges) so you can place fields with `document_id` + document-relative page. Requires `Authorization: Bearer zs_...`.

Input parameters:

- `document_base64`
- `document_id` (string, required)
- `document_url`
- `filename` (string)
- `name`
- `role_mapping`
- `template_id`

Output parameters:

- `result` (string)

### `send_draft` (~221 tokens)

Send Draft

Send a previously created Draft. Costs 1 credit. Recipients default
    to those stored when the draft was created. After send, status is Sent
    and invite emails fire (unless send_invite=false). sequential defaults
    true (one at a time); set false for everyone at once. prefill =
    {"party:name": "text"} sets or overrides text field defaults for this
    send only; unknown or non-text keys are a 422 invalid_prefill_key. An
    encrypted PDF stored on the draft is a 422 with code pdf_encrypted and
    is not charged. Set metadata.revision_of to a changes-requested source
    document_id for its one-time free resend while the promotion is enabled.
    Requires `Authorization: Bearer zs_...`.

Input parameters:

- `document_id` (string, required)
- `metadata`
- `prefill`
- `recipients`
- `send_completion_email` (boolean)
- `send_invite` (boolean)
- `sequential` (boolean)

Output parameters:

- `result` (string)

### `revise_envelope` (~203 tokens)

Revise Envelope

Copy an envelope the signer requested changes on into a new unsent
    Draft: same documents, fields, recipients and public metadata, plus
    metadata.revision_of set to the source document_id. Wraps
    POST /api/v1/documents/{document_id}/revise. Costs no credit. Read the
    signer's comments with get_envelope_status, edit the Draft with
    update_draft / add_document_to_draft, then call
    send_draft(document_id=<the new draft's document_id>): revision_of is
    carried, so the first qualifying revision is free while the promotion
    is enabled. Errors: 404 if the envelope is missing or in another org;
    409 not_changes_requested unless its newest session was declined with
    a change request. Not idempotent: each call creates another Draft.
    Requires `Authorization: Bearer zs_...`.

Input parameters:

- `document_id` (string, required)

Output parameters:

- `result` (string)

### `delete_draft` (~115 tokens)

Delete Draft

Delete an unsent Draft entirely: the envelope, its documents, and the
    stored PDF bytes. Wraps DELETE /api/v1/documents/drafts/{document_id}.
    Use when a draft is abandoned -- there is no archive. Sent and completed
    envelopes cannot be deleted (use void_envelope on a live send instead);
    on one of those this returns the same 404 as a draft that never existed.
    Requires `Authorization: Bearer zs_...`.

Input parameters:

- `document_id` (string, required)

Output parameters:

- `result` (string)

### `create_template` (~112 tokens)

Create Template

Save an existing Draft as a reusable template. Mirrors dashboard
    POST /api/documents/drafts/{id}/save-as-template (API-key twin
    POST /api/v1/documents/drafts/{id}/save-as-template). There is no
    blank-template flow — start from a Draft. Returns template_id and
    role names. The Draft itself is unchanged. Requires
    `Authorization: Bearer zs_...`.

Input parameters:

- `document_id` (string, required)
- `name` (string, required)

Output parameters:

- `result` (string)

### `list_templates` (~64 tokens)

List Templates

List saved templates in the caller's org. Returns template_id,
    name, updated_at, and role names — enough to pick a template for
    add_document_to_draft(template_id=...) or send_from_template.
    Requires `Authorization: Bearer zs_...`.

Output parameters:

- `result` (string)

### `send_from_template` (~351 tokens)

Send From Template

First-class send from a saved template. Stamps a new Draft from
    template_id (same service as dashboard draft-from-template), then
    sends it. Costs 1 credit. recipients =
    [{"name": "...", "email": "...", "role": "signer"}]. role_mapping
    maps the template's roles onto recipient roles, e.g.
    {"customer": "client"}; unmapped roles stay literal. This is the
    send-from-template path — do not also pass template_id to
    send_envelope. prefill = {"party:name": "text"} fills or overrides
    the template's text defaults for this send only; the template itself
    is unchanged. metadata.revision_of may name a changes-requested source
    document_id for its one-time free resend while the promotion is enabled.
    To compose a Draft without sending, keep using
    add_document_to_draft(template_id=...). If send fails after the
    stamp, the new draft is left in place and the error includes
    `draft_id`. The stamp does not store recipients or send options —
    retry with send_draft(document_id=draft_id, recipients=<same
    recipients>) and repeat any metadata / send_invite /
    send_completion_email / sequential, or discard that draft.
    Requires `Authorization: Bearer zs_...`.

Input parameters:

- `metadata`
- `name`
- `prefill`
- `recipients` (array, required)
- `role_mapping`
- `send_completion_email` (boolean)
- `send_invite` (boolean)
- `sequential` (boolean)
- `template_id` (string, required)

Output parameters:

- `result` (string)

### `list_envelopes` (~182 tokens)

List Envelopes

Search the caller's envelopes. Optional filters: status (pending,
    in_progress, completed, voided, declined, expired, cancelled, draft,
    ready_to_send), q (name / filename / recipient / id substring),
    date_from and date_to (ISO-8601, inclusive on created_at). limit max
    50 (default 20). Includes unsent drafts unless status selects a
    session status. Each item includes thin recipients[] (recipient_id,
    email, name, status, can_remind) for remind_envelope, plus
    document_id for get_envelope_status. Requires
    `Authorization: Bearer zs_...`.

Input parameters:

- `date_from`
- `date_to`
- `limit` (integer)
- `offset` (integer)
- `q`
- `status`

Output parameters:

- `result` (string)

### `get_envelope_status` (~97 tokens)

Get Envelope Status

Envelope progress: session status, per-recipient signing status, and —
    once completed — the completed_document_id to pass to
    download_signed_document. A changes-requested recipient includes
    change_request.reason, comments (page/field/normalized anchors/text), and
    timestamp; revision resends include session.revision_of. Requires
    `Authorization: Bearer zs_...`.

Input parameters:

- `document_id` (string, required)

Output parameters:

- `result` (string)

### `get_signing_links` (~197 tokens)

Get Signing Links

Fetch recipient signing URLs for an already-sent envelope without
    sending again. Output is the same `signing_urls` shape
    send_envelope / send_draft / send_from_template return:
    [{recipient_email, recipient_name, signing_url, token}].

    Each signing_url / token authenticates as that recipient on
    /sign/{token}, so this tool requires envelopes:send (same class as
    send / remind), not envelopes:read.

    These URLs are the ordinary agent-link. They are valid iframe
    `signingUrl` values for `@zsign/embed` / `@zsign/react`. This tool
    does not mint a second URL scheme and does not replace agent-link as
    the default. Optional recipient_email keeps one recipient. Requires
    `Authorization: Bearer zs_...`.

Input parameters:

- `document_id` (string, required)
- `recipient_email`

Output parameters:

- `result` (string)

### `remind_envelope` (~163 tokens)

Remind Envelope Recipient

Send one signing reminder to a still-unsigned recipient.

    Wraps POST /api/v1/documents/{document_id}/recipients/{recipient_id}/remind
    — same policy as the dashboard Remind button and the cron sweep (cap,
    spacing, sequential can_sign_now). REMINDERS_ENABLED does not apply.
    Envelopes sent with send_invite=false are refused unless
    override_send_invite is true. Not idempotent: each success increments
    reminder_count, and a second call inside REMINDER_DELAY_HOURS is 429.
    Requires `Authorization: Bearer zs_...`.

Input parameters:

- `document_id` (string, required)
- `override_send_invite` (boolean)
- `recipient_id` (string, required)

Output parameters:

- `result` (string)

### `correct_recipient_email` (~179 tokens)

Correct Recipient Email

Correct the email of an unsigned recipient on an in-flight envelope.

    Wraps POST /api/v1/documents/{document_id}/recipients/{recipient_id}/email.
    Same recipient_id; the signing credential rotates to the new address and
    the previous address is notified — does not void, so signatures already
    collected from other recipients stay valid. Refuses a recipient who has
    already signed (409 recipient_already_signed) and an envelope that is
    voided, completed, declined, or expired. Sends a fresh invite when the
    envelope was sent with invites enabled. Later remind_envelope calls go
    to the new address. Requires `Authorization: Bearer zs_...`.

Input parameters:

- `document_id` (string, required)
- `email` (string, required)
- `recipient_id` (string, required)

Output parameters:

- `result` (string)

### `void_envelope` (~70 tokens)

Void Envelope

Void a sent envelope so it can no longer be signed.

    Signing links stop working immediately and recipients who have not yet
    signed are emailed. The send credit is returned only if nobody has
    opened the envelope.

Input parameters:

- `document_id` (string, required)
- `reason` (string)

Output parameters:

- `result` (string)

### `download_signed_document` (~262 tokens)

Download Signed Document

Download the sealed, signed PDF. Takes the completed_document_id from
    get_envelope_status; the original document_id also works and resolves to
    that document's most recent completed session. Returns the bytes as
    `content_base64` with `content_type` from the HTTP response. PDF
    responses also include `pdf_base64` (same bytes). MCP clients truncate
    large tool responses, so for anything beyond a page or two prefer
    `download_url`: a short-lived bearer URL (valid until
    `download_url_expires_at`) that serves the same bytes with no
    Authorization header — pass it to the user or fetch it directly.
    Requires `Authorization: Bearer zs_...`.

    document_id: one of `documents[].id` from get_envelope_status to download
    just that document (its pages plus the certificate pages — an extract;
    the certificate hash identifies the full envelope). `format='pdf'` (the
    default) returns the combined signed PDF; `format='zip'`: every document
    as its own PDF in one archive (`application/zip`).

Input parameters:

- `completed_document_id` (string, required)
- `document_id`
- `format`

Output parameters:

- `result` (string)

### `download_certificate` (~81 tokens)

Download Certificate

Download the standalone Certificate of Signature PDF for a completed
    envelope. Takes the original document_id from send_envelope /
    get_envelope_status / list_envelopes (NOT completed_document_id).
    Incomplete envelopes error. Returns the PDF as base64. Requires
    `Authorization: Bearer zs_...`.

Input parameters:

- `document_id` (string, required)

Output parameters:

- `result` (string)

### `get_audit_trail` (~82 tokens)

Get Audit Trail

JSON audit trail for an envelope. Completed envelopes include the
    persisted completion certificate; voided / declined / expired
    envelopes return an on-the-fly trail with an empty certificate.
    Still-active envelopes are not found. Takes the original document_id.
    Requires `Authorization: Bearer zs_...`.

Input parameters:

- `document_id` (string, required)

Output parameters:

- `result` (string)

### `list_comments` (~28 tokens)

List Comments

List comment threads for the latest envelope session of a document.

Input parameters:

- `document_id` (string, required)

Output parameters:

- `result` (string)

### `reply_comment` (~35 tokens)

Reply to Comment

Reply to a comment thread using an agent-authored comment.

Input parameters:

- `comment_id` (string, required)
- `text` (string, required)

Output parameters:

- `result` (string)

### `resolve_comment` (~36 tokens)

Resolve or Reopen Comment

Resolve a comment thread, or reopen it when resolved is false.

Input parameters:

- `comment_id` (string, required)
- `resolved` (boolean)

Output parameters:

- `result` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-zsign-zsign/mcp-open#diagnostics

## Score history

- 2026-11-21: 66
- 2026-11-20: 66
- 2026-11-19: 66
- 2026-11-18: 65
- 2026-11-17: 65
- 2026-11-16: 64
- 2026-11-15: 64
- 2026-11-14: 63
- 2026-11-13: 63
- 2026-11-12: 62
- 2026-11-11: 62

## Common questions

### What is the io.zsign/zsign MCP server?

io.zsign/zsign is an MCP server listed in the public MCP registry as io.zsign/zsign. Send documents for e-signature from AI assistants, track signers, and download sealed, signed PDFs. This page covers its hosted endpoint (https://zsign.io/mcp/open).

### Is the io.zsign/zsign MCP server safe to use?

io.zsign/zsign scores 66 out of 100 on VerifyMCP. 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 io.zsign/zsign MCP server expose?

io.zsign/zsign exposes 29 tools: create_account, get_pricing, get_account, check_balance, get_usage, and 24 more. Their descriptions and schemas cost roughly 4,720 tokens of context every time the server is loaded.

### Does the io.zsign/zsign MCP server require authentication?

No. We connected to io.zsign/zsign without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the io.zsign/zsign MCP server still maintained?

io.zsign/zsign is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the io.zsign/zsign MCP server?

VerifyMCP ran 13 checks on io.zsign/zsign, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://zsign.io/mcp/open
- Website: https://zsign.io/
- Changelog RSS feed: https://verifymcp.io/servers/io-zsign-zsign/mcp-open.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-zsign-zsign/mcp-open/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/io-zsign-zsign/mcp-open.json
- HTML version of this page: https://verifymcp.io/servers/io-zsign-zsign/mcp-open
