Legal

ZapSign

Create and manage electronic document signatures via ZapSign API

Connects to ZapSign for electronic document signing. Create documents from PDF or DOCX, add signers, manage templates, track signature status, and handle background checks. Supports multiple authentication modes and audit trails.

Try asking Muse: "Create a contract for signature, add signers by email, and check if they've signed it"

Working now?

Working

Worked last 7 days

96.6% of checks

How to get it

Extra setup

Account

No account needed

Price

Not stated

Source: Found in the official MCP Registry (io.github.mcp-dir/zapsign-mcp) · First listed September 25, 2026

Last 24 hours

Each bar is one check, every 15 minutes. Green means it answered. Last checked 2 h ago.

Is it safe to connect?

What Muse can see: It does not ask you to sign in, so it cannot see your accounts. It only sees what Muse sends it from your request.

Before it acts: Read what Muse plans to do before you approve it, and remove the app from Muse when you stop using it.

musedirectory.ai is not part of Meta. More about how Muse handles your information

How to add it to Muse

Not in Muse's Connectors list yet, but Muse can still use it. Copy the request below and paste it into Muse. Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.

Paste this into Muse

Use ZapSign to help me. It is a free service with an MCP server at https://api.mcp.ai/p_zapsign. It does not need an API key. Ask me before you share anything with it.

Open Muse

https://api.mcp.ai/p_zapsign

Not in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.

Technical details: safety screening, tools, response time and recent checks

Response time at the last check: 110ms. Worked in 96.6% of checks over 30 days.

Screening · September 25, 2026

Screened, no issues found

MCP handshake

Pass

Answered in 162ms

Domain against threat feeds (Cloudflare security DNS)

Pass

api.mcp.ai not flagged

Published packages against the OSV malicious-package database

n/a

No npm or PyPI package published

Hidden instructions or invisible characters in tool text

Pass

35 tools read, nothing found

Inputs asking for passwords, card numbers or seed phrases

Pass

None found

Domain and redirects

Pass

No redirects off the domain

AI review of purpose and tool behavior

Pass

No concerns

Screening looks for known threats and hidden instructions at the time of the check, and runs again weekly and whenever the tool list changes. It cannot see the server's code, so only connect what you need and review what Muse asks to do. How screening works.

Tools · 35

zapsign_list_accountsLista contas ZapSign vinculadas a este install — id e apelido.

zapsign_documents_listDocumentos de assinatura no ZapSign (leitura). Ações: list (filtros: page, status pending|signed|refused, folder_path, deleted, signer_email, created_from/created_to YYYY-MM-DD, sort_order asc|desc, include_signers); get (doc_token — detalhe + signatários + extra_docs + URLs de a

zapsign_documents_getDocumentos de assinatura no ZapSign (leitura). Ações: list (filtros: page, status pending|signed|refused, folder_path, deleted, signer_email, created_from/created_to YYYY-MM-DD, sort_order asc|desc, include_signers); get (doc_token — detalhe + signatários + extra_docs + URLs de a

zapsign_documents_signer_logDocumentos de assinatura no ZapSign (leitura). Ações: list (filtros: page, status pending|signed|refused, folder_path, deleted, signer_email, created_from/created_to YYYY-MM-DD, sort_order asc|desc, include_signers); get (doc_token — detalhe + signatários + extra_docs + URLs de a

zapsign_documents_write_createCriar/alterar documentos de assinatura no ZapSign. Ações: - create (data): cria documento. Campos: name*, signers[]* (cada {name, email, phone_country, phone_number, auth_mode}); UMA fonte de arquivo: url_pdf | base64_pdf | url_docx | base64_docx | markdown_text; opc lang, disabl

zapsign_documents_write_create_from_templateCriar/alterar documentos de assinatura no ZapSign. Ações: - create (data): cria documento. Campos: name*, signers[]* (cada {name, email, phone_country, phone_number, auth_mode}); UMA fonte de arquivo: url_pdf | base64_pdf | url_docx | base64_docx | markdown_text; opc lang, disabl

zapsign_documents_write_updateCriar/alterar documentos de assinatura no ZapSign. Ações: - create (data): cria documento. Campos: name*, signers[]* (cada {name, email, phone_country, phone_number, auth_mode}); UMA fonte de arquivo: url_pdf | base64_pdf | url_docx | base64_docx | markdown_text; opc lang, disabl

zapsign_documents_write_deleteCriar/alterar documentos de assinatura no ZapSign. Ações: - create (data): cria documento. Campos: name*, signers[]* (cada {name, email, phone_country, phone_number, auth_mode}); UMA fonte de arquivo: url_pdf | base64_pdf | url_docx | base64_docx | markdown_text; opc lang, disabl

zapsign_documents_write_refuseCriar/alterar documentos de assinatura no ZapSign. Ações: - create (data): cria documento. Campos: name*, signers[]* (cada {name, email, phone_country, phone_number, auth_mode}); UMA fonte de arquivo: url_pdf | base64_pdf | url_docx | base64_docx | markdown_text; opc lang, disabl

zapsign_documents_write_place_signaturesCriar/alterar documentos de assinatura no ZapSign. Ações: - create (data): cria documento. Campos: name*, signers[]* (cada {name, email, phone_country, phone_number, auth_mode}); UMA fonte de arquivo: url_pdf | base64_pdf | url_docx | base64_docx | markdown_text; opc lang, disabl

zapsign_documents_write_add_extra_docCriar/alterar documentos de assinatura no ZapSign. Ações: - create (data): cria documento. Campos: name*, signers[]* (cada {name, email, phone_country, phone_number, auth_mode}); UMA fonte de arquivo: url_pdf | base64_pdf | url_docx | base64_docx | markdown_text; opc lang, disabl

zapsign_signers_getSignatários no ZapSign (leitura). Ação: get (signer_token — status, sign_url, visualizações, geo, auth_mode etc.). [Flattened action: get]

zapsign_signers_write_addGerenciar signatários no ZapSign. Ações: - add (doc_token, data): adiciona signatário. Campos: name*, email*; opc phone_country, phone_number, auth_mode (assinaturaTela|tokenEmail|tokenSms|tokenWhatsapp), lock_name/email/phone, qualification, send_automatic_email, send_automatic_

zapsign_signers_write_updateGerenciar signatários no ZapSign. Ações: - add (doc_token, data): adiciona signatário. Campos: name*, email*; opc phone_country, phone_number, auth_mode (assinaturaTela|tokenEmail|tokenSms|tokenWhatsapp), lock_name/email/phone, qualification, send_automatic_email, send_automatic_

zapsign_signers_write_removeGerenciar signatários no ZapSign. Ações: - add (doc_token, data): adiciona signatário. Campos: name*, email*; opc phone_country, phone_number, auth_mode (assinaturaTela|tokenEmail|tokenSms|tokenWhatsapp), lock_name/email/phone, qualification, send_automatic_email, send_automatic_

zapsign_signers_write_signGerenciar signatários no ZapSign. Ações: - add (doc_token, data): adiciona signatário. Campos: name*, email*; opc phone_country, phone_number, auth_mode (assinaturaTela|tokenEmail|tokenSms|tokenWhatsapp), lock_name/email/phone, qualification, send_automatic_email, send_automatic_

zapsign_templates_listTemplates (modelos DOCX) no ZapSign (leitura). Ações: list (page — 20/página); get (template_token — inclui inputs[] das variáveis {{VAR}}). [Flattened action: list]

zapsign_templates_getTemplates (modelos DOCX) no ZapSign (leitura). Ações: list (page — 20/página); get (template_token — inclui inputs[] das variáveis {{VAR}}). [Flattened action: get]

zapsign_templates_write_createGerenciar templates no ZapSign. Ações: - create (data): cria template DOCX. Campos: name*, docx_url | base64_docx*; opc first_signer{}, lang, observers[], folder_path/folder_token, redirect_link. - update (template_token, data): metadados (o DOCX em si é imutável). Campos: name,

zapsign_templates_write_updateGerenciar templates no ZapSign. Ações: - create (data): cria template DOCX. Campos: name*, docx_url | base64_docx*; opc first_signer{}, lang, observers[], folder_path/folder_token, redirect_link. - update (template_token, data): metadados (o DOCX em si é imutável). Campos: name,

zapsign_templates_write_deleteGerenciar templates no ZapSign. Ações: - create (data): cria template DOCX. Campos: name*, docx_url | base64_docx*; opc first_signer{}, lang, observers[], folder_path/folder_token, redirect_link. - update (template_token, data): metadados (o DOCX em si é imutável). Campos: name,

zapsign_webhooks_write_createGerenciar webhooks no ZapSign (não há endpoint de listagem na API). Ações: - create (data): cria webhook (1 por conta cobre todos os docs). Campos: url*; opc type ("" = todos | doc_signed | doc_created | doc_deleted | ...), doc_token, headers. Retorna {id}. - delete (id): remove

zapsign_webhooks_write_deleteGerenciar webhooks no ZapSign (não há endpoint de listagem na API). Ações: - create (data): cria webhook (1 por conta cobre todos os docs). Campos: url*; opc type ("" = todos | doc_signed | doc_created | doc_deleted | ...), doc_token, headers. Retorna {id}. - delete (id): remove

zapsign_checks_getVerificação de antecedentes no ZapSign (leitura). Ação: get (check_id — status not_started|in_progress|delayed|error|completed + pdf_report). [Flattened action: get] Bulk support: accepts check_ids for batched execution.

zapsign_checks_write_createCriar verificação de antecedentes no ZapSign (consome créditos). Ação: create (data). Campos: country* (BR|CO|CL|MX|PE), type* (ex.: person | credit_person_br), user_authorized: true*, e um identificador: national_id | foreign_id. [Flattened action: create]

zapsign_account_planConta ZapSign (leitura). Ações: plan (info do plano: créditos, status, período); users (page — lista usuários da conta, 25/página). [Flattened action: plan]

zapsign_account_usersConta ZapSign (leitura). Ações: plan (info do plano: créditos, status, período); users (page — lista usuários da conta, 25/página). [Flattened action: users]

zapsign_account_write_create_userGerenciar usuários da conta ZapSign. Ações: - create_user (data): adiciona usuário. Campos: email*; opc role (member|admin|self_docs_limited), first_name, last_name, phone_country, phone_number. - delete_user (email): remove usuário (donos não podem ser removidos). [Flattened act

zapsign_account_write_delete_userGerenciar usuários da conta ZapSign. Ações: - create_user (data): adiciona usuário. Campos: email*; opc role (member|admin|self_docs_limited), first_name, last_name, phone_country, phone_number. - delete_user (email): remove usuário (donos não podem ser removidos). [Flattened act

show_versionShow the current MCP platform and adapter versions.

report_bugReport a bug, missing feature, or send feedback. Include the conversation array with recent messages for reproduction.

connectReturns connection status and URLs. When all providers are connected, returns authenticated:true and empty pending[]. When credentials are missing, returns connect_url for the toolkit and per-install URLs.

toolkit_infoReturns the current toolkit state: installed MCPs, their connection status, the accounts connected to each one, and how many catalog tools each exposes.

marketplaceThe official mcp.ai marketplace — the in-platform catalog of every MCP/tool, AND the way to run them. Covers capability requests like "find an MCP that does X", "consulta um CPF", "is there a tool for Y". Core flow: action=search discovers MCPs by intent → describe returns one MC

authenticateMCP.AI for IDE agents (Cursor, etc.): log in in the browser, copy the access token. Best: add it to this server's config as a header `Authorization: Bearer <token>` for a permanent, non-expiring connection. Or paste it here for a session-only login: call with { token: "<jwt>" } a

Recent checks

2026-09-28 07:46:00live · HTTP 200110ms

2026-09-28 05:30:47live · HTTP 2001475ms

2026-09-28 03:01:14live · HTTP 2001808ms

2026-09-28 00:45:53live · HTTP 200320ms

2026-09-27 22:16:18live · HTTP 2002304ms

2026-09-27 20:01:22live · HTTP 200643ms

2026-09-27 17:45:54live · HTTP 2002356ms

2026-09-27 15:32:30degraded · HTTP 2005445ms

2026-09-27 13:16:49live · HTTP 200333ms

2026-09-27 11:01:36live · HTTP 2002476ms

2026-09-27 08:45:53live · HTTP 200839ms

2026-09-27 06:16:21live · HTTP 2003675ms

Link

https://api.mcp.ai/p_zapsign

Questions about ZapSign in Muse

How do I connect ZapSign to Muse?

Not in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use ZapSign to help me. It is a free service with an MCP server at https://api.mcp.ai/p_zapsign. It does not need an API key. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.

Is ZapSign working right now?

At the last check (September 28, 2026, 07:46 UTC) the endpoint was working, answering in 110ms. Over the last 7 days it answered 96.6% of health checks. It is checked every 15 minutes.

Is ZapSign safe to connect to Muse?

It was screened on September 25, 2026 with the result "screened, no issues found". Screening checks the domain against threat feeds and reads the tools for hidden instructions and requests for passwords or card numbers. It cannot see the server's code, so grant only the access you need.

What can ZapSign do in Muse?

It exposes 35 tools, including zapsign_list_accounts, zapsign_documents_list, zapsign_documents_get, zapsign_documents_signer_log. For example, you could ask Muse: "Create a contract for signature, add signers by email, and check if they've signed it"

Follow ZapSign

Made this app? Claim it or get a status badge

Is this yours?

This listing was added from public sources (Found in the official MCP Registry (io.github.mcp-dir/zapsign-mcp)). If you build ZapSign, claim it to correct the details and get your badge.

Claim this listing

Paste this on your site or README. It always shows the latest check.

<a href="https://musedirectory.ai/connector/zapsign"><img src="https://musedirectory.ai/badge/zapsign.svg" alt="ZapSign on musedirectory.ai" width="236" height="40"></a>

More for app makers