Skip to content

GoodSign MCP server

io.goodsign/goodsigngoodsign.iostreamable-httpv1.0.0Scanned

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

10 tools: 1 can delete or cancel things, 1 do something that can't be undone, 3 change things and 5 only read.

Tools: 1 delete, 1 irreversible, 3 write, 5 read.
  • Reads private data · 4
  • Reads text others write · 4
  • Can send data out · 1
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here can delete or cancel things and 1 does something that can't be undone. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the GoodSign MCP server can do

The GoodSign MCP server is published by goodsign.io, a domain the MCP Registry verified. It has 10 tools. It can delete or cancel things (1 tool: void_document), do things that cannot be undone, such as sending, paying or publishing (send_from_template) and create or change data (3 tools: create_document_from_upload, create_upload_url and remind_signers). 5 tools only read.

4 tools read private data (download_document, get_document, list_documents and 1 more); 4 tools bring in text other people can write (download_document, remind_signers, send_from_template and 1 more); 1 tool can send data out of your system (send_from_template). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

The fixed checks matched 1 finding (long-description). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 18, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

10 tools

Deletes or cancels 1Claude Code: deny
  • void_documentCancel a sent document so nobody can sign it anymore.Reads text others writeNo findings

    Why it is in this group

    • The name "void_document" says "void": a word for removing or ending something.
    • The description says "cannot be undone".
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • openWorldHint: true
Can't be undone 1Claude Code: ask
  • send_from_templateSend a document for e-signature using a template.Reads text others writeCan send data outNo findings

    Why it is in this group

    • The name "send_from_template" says "send": a word for sending, and what is sent cannot be taken back.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe name "send_from_template" says "send": it sends or publishes something to other people.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
Changes things 3Claude Code: ask
  • create_document_from_uploadTurn a PDF you PUT to a create_upload_url url into a GoodSign document.No findings

    Why it is in this group

    • The name "create_document_from_upload" says "create": a word for a change.
    Description, as the server wrote it
    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. MULTIPLE PDFs IN ONE ENVELOPE (e.g. an NDA plus a contractor agreement, signed together for 1 credit): create the first document normally, then for each extra PDF call create_upload_url, PUT it, and call this tool with attach_to_uuid set to the first document's uuid. Signers see the files in the order they were added. Use the same signer keys across files for the same person — one signer per distinct key across the whole envelope. Send once, with the first document's uuid.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • create_upload_urlGet a short-lived URL to upload a PDF that GoodSign will turn into a document.1 finding

    Why it is in this group

    • The name "create_upload_url" says "create": a word for a change.

    Findings

    • Info

      The description is 2,854 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: "...m with get_document that the signer keys and field count match what you embedded."

      What this check looks for
    Description, as the server wrote it
    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 size sets the field height, and an input/name/email box is exactly as wide as the printed tag text — write the tag at the size you want the answer to be. To WIDEN an input/name/email field without making it taller, pad with trailing spaces INSIDE the tag before the ] — e.g. [name|Client ] — the spaces count toward the printed width but are stripped from KEY. Spaces after the ] do nothing. Print the tag in a monospace font (e.g. Courier) so each padding space adds a full, predictable character width. 5. Leave 2-3 blank lines of clear space around sign/in tags: the drawn signature renders much larger than the tag text. GoodSign erases the tag text from the final PDF and renders the field value in its place. After create_document_from_upload, confirm with get_document that the signer keys and field count match what you embedded.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: false
  • remind_signersRe-send the signing invitation email to signers who have not completed yet.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: true
Only reads 5Show 5 read-only tools
  • account_statusShow the GoodSign account name and remaining credits.No findings

    Why it is in this group

    • The name "account_status" says "status": a word for reading.
    Description, as the server wrote it
    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?".

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • download_documentGet an authenticated download URL for a document's PDF (including the audit certificate once complete).Reads private dataReads text others writeNo findings

    Why it is in this group

    • The description's first verb is "get": a word for reading.

    What it can reach

    • private-dataThe name "download_document" says "document": it reads documents.
    • private-dataThe description's first sentence says "get" and "document": it reads documents.
    • untrusted-inputThe description's first sentence says "get" and "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    Get an authenticated download URL for a document's PDF (including the audit certificate once complete). If the document has several PDFs (extra files added with attach_to_uuid), `files` lists one download URL per PDF — download every one. 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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • get_documentFetch full detail for one document OR template by uuid.Reads private dataNo findings

    Why it is in this group

    • The name "get_document" says "get": a word for reading.

    What it can reach

    • private-dataThe name "get_document" says "get" and "document": it reads documents.
    • private-dataThe description's first sentence says "fetch" and "document": it reads documents.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • list_documentsList this account's documents filtered by status.Reads private dataNo findings

    Why it is in this group

    • The name "list_documents" says "list": a word for reading.

    What it can reach

    • private-dataThe name "list_documents" says "list" and "document": it reads documents.
    • private-dataThe description's first sentence says "list" and "document": it reads documents.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • list_templatesList the reusable document templates in this GoodSign account.Reads private dataNo findings

    Why it is in this group

    • The name "list_templates" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "document": it reads documents.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

16 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.

Reads private data4
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write4
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__goodsign__send_from_template"
    ]
  }
}

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:13 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
5
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 5 tools that change things (1 destructive, 1 irreversible, 3 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://goodsign.io/mcp: tools/list returned 10 tools to an anonymous client, including void_document (destructive), send_from_template (irreversible), create_document_from_upload (write), create_upload_url (write), remind_signers (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 info
  • The description is 2,854 characters long, over the 2,000 this check looks for.

    Matched text

    description ends: "...m with get_document that the signer keys and field count match what you embedded."

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools2 changed.~2 changedView diff

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http goodsign https://goodsign.io/mcp --header 'Authorization: <your-authorization>'
claude mcp add --transport http goodsign https://goodsign.io/mcp --header 'Authorization: <your-authorization>'

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__goodsign__account_status",
      "mcp__goodsign__download_document",
      "mcp__goodsign__get_document",
      "mcp__goodsign__list_documents",
      "mcp__goodsign__list_templates"
    ],
    "ask": [
      "mcp__goodsign__create_document_from_upload",
      "mcp__goodsign__create_upload_url",
      "mcp__goodsign__remind_signers",
      "mcp__goodsign__send_from_template"
    ],
    "deny": [
      "mcp__goodsign__void_document"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as goodsign. Review it before you use it.

Capability tags behind 7 rules
  • mcp__goodsign__download_document private-data, untrusted-input
  • mcp__goodsign__get_document private-data
  • mcp__goodsign__list_documents private-data
  • mcp__goodsign__list_templates private-data
  • mcp__goodsign__remind_signers untrusted-input
  • mcp__goodsign__send_from_template untrusted-input, outbound
  • mcp__goodsign__void_document untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.goodsign/goodsign/verify?hash=476d401b6dea6e8c9ef12220bb6bef0fd91f0e82755282514c19e9e7cd5e4e9c" | jq -e '.changed == false'

Pinned hash 476d401b6dea, from Nov 18, 2026, 11:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.goodsign/goodsign/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.goodsign/goodsign
[![Anlyon Radar](https://radar.anlyon.com/badge/io.goodsign/goodsign.svg)](https://radar.anlyon.com/servers/io.goodsign/goodsign)

Source: MCP Registry. Synced Oct 21, 2026, 18:52 UTC.

GoodSign MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the GoodSign MCP server safe?

No scan can promise that. What its definitions show: 10 tools, 5 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the GoodSign MCP server delete data?

Yes. 1 tool can delete, cancel or revoke something: void_document.

Can the GoodSign MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: send_from_template.

What tools does the GoodSign MCP server have?

10 tools: 1 destructive, 1 irreversible, 3 write, 5 read. void_document, send_from_template, create_document_from_upload, create_upload_url, remind_signers, account_status, download_document, get_document and 2 more.

Does the GoodSign MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the GoodSign MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): send_from_template.

Has the GoodSign MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 4, 2026. Every change is on this page and in its Atom feed.