# GoodSign (remote · goodsign.io)

Send documents for e-signature, track and remind signers, and download signed PDFs.

- Trust score: 76/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-25

## Components

- remote · `goodsign.io`: 76/100 (this document), [markdown](https://verifymcp.io/servers/io-goodsign-goodsign/goodsign.md), [page](https://verifymcp.io/servers/io-goodsign-goodsign/goodsign)

## Channel facts

- Endpoint: `https://goodsign.io/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.0`

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

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 69/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2221 tokens (~222/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% 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.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 11 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.

## Install

### How do I install the GoodSign MCP server?

GoodSign is a hosted endpoint at https://goodsign.io/mcp, 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-goodsign-goodsign 'https://goodsign.io/mcp'
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

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-09-25 (score 76, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 76, +1)

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

### 2026-09-22 (score 75, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-21 (score 74, +38)

- [security improvement] Transport: unverified → pass
- [security improvement] Injection markers: unverified → pass
- [security] First check of Judged manipulation: pass
- [security] Authorization: Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
- [functional regression] MCP protocol: unverified → fail
- [functional improvement] Tool coverage: unverified → 100
- [functional] First check of Schema quality: fail
- [functional] First check of Schema quality: excellent
- [functional] First check of Schema quality: fail
- [functional] First check of Destructive annotations: 100
- [functional] First check of Tool coverage: 100

### 2026-09-20 (score 36)

First indexed and scored.

## MCP tools (10)

### `account_status` (~46 tokens)

Account status and credits

Show the GoodSign account name and remaining credits. Each envelope sent costs 1 credit. Check this before bulk sending, or when the user asks "how many credits do I have?".

### `create_document_from_upload` (~228 tokens)

Create a document from an uploaded PDF

Turn a PDF you PUT to a create_upload_url url into a GoodSign document. Call this only after the PUT has finished successfully. GoodSign discovers any text tags in the PDF (see create_upload_url for the full TAG REFERENCE and rules) and creates one field per tag plus one signer per distinct signer key automatically. This does NOT send anything or email anyone — the result behaves like a template: check it with get_document, then send it with send_from_template. The created document can only be sent once — to send the same PDF again, upload it again with create_upload_url and call this tool a second time. If the response includes warnings about unreadable tags, fix the tag text in the source document, re-export the PDF, call create_upload_url again and retry.

Input parameters:

- `doc_name` (string): Optional name for the document, e.g. "SoW - Acme Q3". Defaults to "document".
- `upload_id` (string, required): The 40-character hex upload_id returned by create_upload_url, after the PUT to its upload_url has succeeded.

### `create_upload_url` (~692 tokens)

Get a URL to upload a PDF

Get a short-lived URL to upload a PDF that GoodSign will turn into a document. Use this for a document that is NOT based on an existing GoodSign template — e.g. a Statement of Work, contract or NDA drafted for this specific deal. After the PUT succeeds, call create_document_from_upload with the upload_id this returns. The URL is valid for 15 minutes.

If you are GENERATING the PDF yourself, embed text tags where fields should go — GoodSign places a real field at each tag's exact position, and each distinct KEY becomes one signer (reuse the same KEY on every tag that person fills).

TAG REFERENCE — this is the complete list; any other tag type is discarded:
\- [sign|KEY] signature. [in|KEY] initials. Signature size variants: [signxs|KEY] [signsm|KEY] [signmd|KEY] [signlg|KEY] [signxl|KEY].
\- [date|KEY] date of signing, filled in automatically.
\- [input|KEY] required text box. [input?|KEY] optional text box. [input|KEY|Some text] pre-filled, signer can edit.
\- [name|KEY] and [email|KEY] text boxes pre-filled with that signer's name / email address.
\- [c|KEY|Label] optional checkbox. [c*|KEY|Label] required checkbox. [c|KEY|x Label] pre-checked. [c1|KEY|Red] [c1|KEY|Blue] = radio group (same digit = one group, signer picks one).

RULES — breaking any of these corrupts or silently drops fields:
1\. KEY is the signer key: letters and digits ONLY (Client, signer1), identical spelling and case on every tag for that person. Keys differing only in case, spaces or punctuation collide into the wrong signer. Exception: trailing padding spaces before the closing ] (rule 4) are stripped before the key is matched, so [name|Client   ] still keys to Client.
2\. A tag must be one unbroken run of selectable text on a single line in a normal font — never an image, never wrapped across lines.
3\. Do not use square brackets anywhere else in the document — prose like "[insert date]" gets parsed as a tag. Use parentheses instead.
4\. The tag's printed size becomes the field's size: its font si…

### `download_document` (~72 tokens)

Get download link for a document PDF

Get an authenticated download URL for a document's PDF (including the audit certificate once complete). The URL requires the same `Authorization: Bearer` API key this MCP connection uses — download it with curl in a shell, do not try to fetch the bytes into the conversation.

Input parameters:

- `uuid` (string, required): Document uuid

### `get_document` (~120 tokens)

Get document / template detail

Fetch full detail for one document OR template by uuid. For a template: shows the signer keys ("key" on each signer) and field keys that send_from_template requires — always check this before sending. For a sent document: shows status and per-signer progress (who has signed, who is pending). Timestamps are unix epoch seconds. Field entries show structural info only (key, type, page, which signer); signer-entered field values are never returned.

Input parameters:

- `uuid` (string, required): Document or template uuid, from list_templates or list_documents

### `list_documents` (~83 tokens)

List documents by status

List this account's documents filtered by status. Use status "sent" (default) to see envelopes still waiting on signatures, "complete" for fully signed ones. Use this to answer questions like "what is still waiting to be signed?" — then get_document on a uuid for per-signer detail.

Input parameters:

- `status` (string): Filter status. Defaults to "sent".

### `list_templates` (~68 tokens)

List templates

List the reusable document templates in this GoodSign account. Call this first whenever the user wants to send a document — send_from_template needs a template uuid from here. Each template defines signer keys; call get_document with the template uuid to see exactly which signer keys and field keys it requires before sending.

### `remind_signers` (~95 tokens)

Remind pending signers

Re-send the signing invitation email to signers who have not completed yet. Omit signer_email to remind ALL pending signers of the document; pass signer_email to remind one specific person. Sends real email — do not call repeatedly; once per day per signer is plenty.

Input parameters:

- `signer_email` (string): Optional: remind only this signer
- `uuid` (string, required): Document uuid (a sent document, not a template)

### `send_from_template` (~312 tokens)

Send document for e-signature

Send a document for e-signature using a template. THIS EMAILS REAL PEOPLE and spends 1 credit — confirm each signer's name and email with the user before calling, or set draft=true to stage without emailing anyone. Requires one signers[] entry per signer key on the template (get_document on the template uuid lists the keys). For sequential signing set send_in_order=true: signers are emailed one at a time, in the order of the signers array (or explicit send_order values, lower first). Pre-fill text fields with fields[] using the field keys from get_document.

Input parameters:

- `cc_email` (string): Optional comma-separated CC addresses, notified when signing completes
- `doc_name` (string): Optional name for the sent document, e.g. "NDA - Acme Pty"
- `draft` (boolean): true = prepare the document but do NOT email anyone. Use when the user wants to review first.
- `email_message` (string): Optional message shown inside the signing invitation email
- `email_subject` (string): Optional subject for the signing invitation email
- `fields` (array): Optional pre-filled field values (field keys come from get_document on the template)
- `send_in_order` (boolean): true = sequential signing (signer 2 is only emailed after signer 1 completes)
- `signers` (array, required): One entry per signer key defined on the template. Every key must be covered.
- `template_uuid` (string, required): Template uuid from list_templates

### `void_document` (~104 tokens)

Void (cancel) a sent document

Cancel a sent document so nobody can sign it anymore. This cannot be undone — to re-send, use send_from_template again. By default signers are notified the document was voided; set notify=false to void silently. Confirm with the user before voiding.

Input parameters:

- `message` (string): Optional reason shown to signers in the void notification
- `notify` (boolean): Notify signers by email (default true)
- `uuid` (string, required): Document uuid to void

## Diagnostics

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

## Score history

- 2026-09-25: 76
- 2026-09-24: 76
- 2026-09-23: 75
- 2026-09-22: 75
- 2026-09-21: 74
- 2026-09-20: 36

## Common questions

### What is the GoodSign MCP server?

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

### Is the GoodSign MCP server safe to use?

GoodSign scores 76 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 GoodSign MCP server expose?

GoodSign exposes 10 tools: account_status, create_document_from_upload, create_upload_url, download_document, get_document, and 5 more. Their descriptions and schemas cost roughly 1,820 tokens of context every time the server is loaded.

### Does the GoodSign MCP server require authentication?

Yes. GoodSign asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the GoodSign MCP server still maintained?

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

## Links

- Remote endpoint: https://goodsign.io/mcp
- Authorisation metadata: https://goodsign.io/.well-known/oauth-protected-resource/mcp
- Website: https://goodsign.io/mcp-server
- Changelog RSS feed: https://verifymcp.io/servers/io-goodsign-goodsign/goodsign.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-goodsign-goodsign/goodsign.json
- HTML version of this page: https://verifymcp.io/servers/io-goodsign-goodsign/goodsign