ZapSign MCP server
io.github.mcp-dir/zapsign-mcpmcp-dirstreamable-httpv0.1.0Scanned
ZapSign electronic document signing via the official API: create documents for signature (from PDF,
35 tools: 24 change things and 11 only read.
- Reads private data · 3
- Reads text others write · 1
- Can send data out · 0
- 2 findings
Tools listed without sign-in. Remote posture
With Anlyon
24 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
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 ZapSign MCP server can do
The ZapSign MCP server is published by the GitHub account mcp-dir. It has 35 tools. It can create or change data (24 tools: zapsign_documents_write_create, zapsign_documents_write_create_from_template, zapsign_documents_write_update, zapsign_documents_write_delete and 20 more), but cannot delete data. 11 tools only read.
3 tools read private data (zapsign_documents_list, zapsign_documents_get and zapsign_documents_signer_log); 1 tool brings in text other people can write (marketplace).
The fixed checks matched 2 findings (credentials-mention). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 8, 2026, version 0.1.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.
35 tools
Changes things 24Claude Code: ask
authenticateMCP.AI for IDE agents (Cursor, etc.): log in in the browser, copy the access token.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it MCP.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>" } after the user pastes, or with no args to get the link.
Annotations the server declares
- title: Authenticate
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
marketplaceThe official mcp.ai marketplace — the in-platform catalog of every MCP/tool, AND the way to run them.Reads text others write1 finding
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.
Findings
- Info
The description mentions "credential".
What this check looks forMatched text
description: "...ating the tool list. If the MCP needs a credential/login, invoke returns a connect link; i..."
Description, as the server wrote it The 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 MCP's full profile (every tool with its id + params, pricing, auth) so you pick the right tool_id → invoke RUNS that tool. KEY: invoke works even when the MCP is NOT installed — it runs the tool pontualmente (one-off), without adding the MCP to the toolkit and without bloating the tool list. If the MCP needs a credential/login, invoke returns a connect link; if it is paid and the wallet is empty, invoke returns a checkout/top-up link (the user opens it, then you retry). Use install only to make an MCP PERMANENT in the active toolkit (its tools then show up natively in future sessions); prefer invoke for a single/occasional use. list_tools lists what is callable right now. subscribe/cancel handle per-MCP billing; report_bug sends feedback; request_mcp asks us to build a NEW MCP when nothing fits. Search/describe flag installed_in_toolkit vs installed_in_workspace. Writes (install/uninstall/subscribe/cancel and the one-off install behind invoke) require workspace owner/admin. It also carries the mcp.ai PROMPT LIBRARY, which is about ready-made prompt TEXT rather than MCPs: search_prompts finds one, get_prompt returns its full text with {{variables}} filled, and publish_prompt saves a prompt and returns a shareable mcp.ai/p/<slug> link that opens without login.
Annotations the server declares
- title: Marketplace
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
report_bugReport a bug, missing feature, or send feedback.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Report a bug, missing feature, or send feedback. Include the conversation array with recent messages for reproduction.
Annotations the server declares
- title: Report Bug
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
zapsign_account_planConta ZapSign (leitura).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Conta 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]
Annotations the server declares
- title: zapsign_account_plan
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
zapsign_account_usersConta ZapSign (leitura).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Conta 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]
Annotations the server declares
- title: zapsign_account_users
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
zapsign_account_write_create_userGerenciar usuários da conta ZapSign.No findings
Why it is in this group
- The name "zapsign_account_write_create_user" says "write": a word for a change.
Description, as the server wrote it Gerenciar 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 action: create_user]
Annotations the server declares
- title: zapsign_account_write_create_user
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
zapsign_account_write_delete_userGerenciar usuários da conta ZapSign.No findings
Why it is in this group
- The name "zapsign_account_write_delete_user" says "write": a word for a change.
Description, as the server wrote it Gerenciar 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 action: delete_user]
Annotations the server declares
- title: zapsign_account_write_delete_user
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
zapsign_checks_write_createCriar verificação de antecedentes no ZapSign (consome créditos).No findings
Why it is in this group
- The name "zapsign_checks_write_create" says "write": a word for a change.
Description, as the server wrote it Criar 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]
Annotations the server declares
- title: zapsign_checks_write_create
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
zapsign_documents_write_add_extra_docCriar/alterar documentos de assinatura no ZapSign.No findings
Why it is in this group
- The name "zapsign_documents_write_add_extra_doc" says "write": a word for a change.
Description, as the server wrote it Criar/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, disable_signer_emails, date_limit_to_sign, signature_order_active, folder_path, external_id. - create_from_template (data): cria via template. Campos: template_id*, signer_name*, data[]* (cada {de, para} substituindo {{VAR}}); opc signer_email, send_automatic_email, send_automatic_whatsapp, folder_path, external_id, lang. - update (doc_token, data): só com doc "em andamento". Campos: name, date_limit_to_sign, folder_path, extra_docs[]. - delete (doc_token): soft-delete. - refuse (data): cancela/recusa. Campos: doc_token*, rejected_reason*, notify_signer. - place_signatures (doc_token, data): posiciona assinaturas por coordenadas. Campo: rubricas[] ({signer_token, page 0-based, relative_position_left/bottom, relative_size_x/y, type signature|visto}). - add_extra_doc (doc_token, data): anexa PDF extra. Campos: name*, url_pdf | base64_pdf. [Flattened action: add_extra_doc]
Annotations the server declares
- title: zapsign_documents_write_add_extra_doc
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
zapsign_documents_write_createCriar/alterar documentos de assinatura no ZapSign.No findings
Why it is in this group
- The name "zapsign_documents_write_create" says "write": a word for a change.
Description, as the server wrote it Criar/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, disable_signer_emails, date_limit_to_sign, signature_order_active, folder_path, external_id. - create_from_template (data): cria via template. Campos: template_id*, signer_name*, data[]* (cada {de, para} substituindo {{VAR}}); opc signer_email, send_automatic_email, send_automatic_whatsapp, folder_path, external_id, lang. - update (doc_token, data): só com doc "em andamento". Campos: name, date_limit_to_sign, folder_path, extra_docs[]. - delete (doc_token): soft-delete. - refuse (data): cancela/recusa. Campos: doc_token*, rejected_reason*, notify_signer. - place_signatures (doc_token, data): posiciona assinaturas por coordenadas. Campo: rubricas[] ({signer_token, page 0-based, relative_position_left/bottom, relative_size_x/y, type signature|visto}). - add_extra_doc (doc_token, data): anexa PDF extra. Campos: name*, url_pdf | base64_pdf. [Flattened action: create]
Annotations the server declares
- title: zapsign_documents_write_create
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
zapsign_documents_write_create_from_templateCriar/alterar documentos de assinatura no ZapSign.No findings
Why it is in this group
- The name "zapsign_documents_write_create_from_template" says "write": a word for a change.
Description, as the server wrote it Criar/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, disable_signer_emails, date_limit_to_sign, signature_order_active, folder_path, external_id. - create_from_template (data): cria via template. Campos: template_id*, signer_name*, data[]* (cada {de, para} substituindo {{VAR}}); opc signer_email, send_automatic_email, send_automatic_whatsapp, folder_path, external_id, lang. - update (doc_token, data): só com doc "em andamento". Campos: name, date_limit_to_sign, folder_path, extra_docs[]. - delete (doc_token): soft-delete. - refuse (data): cancela/recusa. Campos: doc_token*, rejected_reason*, notify_signer. - place_signatures (doc_token, data): posiciona assinaturas por coordenadas. Campo: rubricas[] ({signer_token, page 0-based, relative_position_left/bottom, relative_size_x/y, type signature|visto}). - add_extra_doc (doc_token, data): anexa PDF extra. Campos: name*, url_pdf | base64_pdf. [Flattened action: create_from_template]
Annotations the server declares
- title: zapsign_documents_write_create_from_template
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
zapsign_documents_write_deleteCriar/alterar documentos de assinatura no ZapSign.No findings
Why it is in this group
- The name "zapsign_documents_write_delete" says "write": a word for a change.
Description, as the server wrote it Criar/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, disable_signer_emails, date_limit_to_sign, signature_order_active, folder_path, external_id. - create_from_template (data): cria via template. Campos: template_id*, signer_name*, data[]* (cada {de, para} substituindo {{VAR}}); opc signer_email, send_automatic_email, send_automatic_whatsapp, folder_path, external_id, lang. - update (doc_token, data): só com doc "em andamento". Campos: name, date_limit_to_sign, folder_path, extra_docs[]. - delete (doc_token): soft-delete. - refuse (data): cancela/recusa. Campos: doc_token*, rejected_reason*, notify_signer. - place_signatures (doc_token, data): posiciona assinaturas por coordenadas. Campo: rubricas[] ({signer_token, page 0-based, relative_position_left/bottom, relative_size_x/y, type signature|visto}). - add_extra_doc (doc_token, data): anexa PDF extra. Campos: name*, url_pdf | base64_pdf. [Flattened action: delete]
Annotations the server declares
- title: zapsign_documents_write_delete
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
zapsign_documents_write_place_signaturesCriar/alterar documentos de assinatura no ZapSign.No findings
Why it is in this group
- The name "zapsign_documents_write_place_signatures" says "write": a word for a change.
Description, as the server wrote it Criar/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, disable_signer_emails, date_limit_to_sign, signature_order_active, folder_path, external_id. - create_from_template (data): cria via template. Campos: template_id*, signer_name*, data[]* (cada {de, para} substituindo {{VAR}}); opc signer_email, send_automatic_email, send_automatic_whatsapp, folder_path, external_id, lang. - update (doc_token, data): só com doc "em andamento". Campos: name, date_limit_to_sign, folder_path, extra_docs[]. - delete (doc_token): soft-delete. - refuse (data): cancela/recusa. Campos: doc_token*, rejected_reason*, notify_signer. - place_signatures (doc_token, data): posiciona assinaturas por coordenadas. Campo: rubricas[] ({signer_token, page 0-based, relative_position_left/bottom, relative_size_x/y, type signature|visto}). - add_extra_doc (doc_token, data): anexa PDF extra. Campos: name*, url_pdf | base64_pdf. [Flattened action: place_signatures]
Annotations the server declares
- title: zapsign_documents_write_place_signatures
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
zapsign_documents_write_refuseCriar/alterar documentos de assinatura no ZapSign.No findings
Why it is in this group
- The name "zapsign_documents_write_refuse" says "write": a word for a change.
Description, as the server wrote it Criar/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, disable_signer_emails, date_limit_to_sign, signature_order_active, folder_path, external_id. - create_from_template (data): cria via template. Campos: template_id*, signer_name*, data[]* (cada {de, para} substituindo {{VAR}}); opc signer_email, send_automatic_email, send_automatic_whatsapp, folder_path, external_id, lang. - update (doc_token, data): só com doc "em andamento". Campos: name, date_limit_to_sign, folder_path, extra_docs[]. - delete (doc_token): soft-delete. - refuse (data): cancela/recusa. Campos: doc_token*, rejected_reason*, notify_signer. - place_signatures (doc_token, data): posiciona assinaturas por coordenadas. Campo: rubricas[] ({signer_token, page 0-based, relative_position_left/bottom, relative_size_x/y, type signature|visto}). - add_extra_doc (doc_token, data): anexa PDF extra. Campos: name*, url_pdf | base64_pdf. [Flattened action: refuse]
Annotations the server declares
- title: zapsign_documents_write_refuse
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
zapsign_documents_write_updateCriar/alterar documentos de assinatura no ZapSign.No findings
Why it is in this group
- The name "zapsign_documents_write_update" says "write": a word for a change.
Description, as the server wrote it Criar/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, disable_signer_emails, date_limit_to_sign, signature_order_active, folder_path, external_id. - create_from_template (data): cria via template. Campos: template_id*, signer_name*, data[]* (cada {de, para} substituindo {{VAR}}); opc signer_email, send_automatic_email, send_automatic_whatsapp, folder_path, external_id, lang. - update (doc_token, data): só com doc "em andamento". Campos: name, date_limit_to_sign, folder_path, extra_docs[]. - delete (doc_token): soft-delete. - refuse (data): cancela/recusa. Campos: doc_token*, rejected_reason*, notify_signer. - place_signatures (doc_token, data): posiciona assinaturas por coordenadas. Campo: rubricas[] ({signer_token, page 0-based, relative_position_left/bottom, relative_size_x/y, type signature|visto}). - add_extra_doc (doc_token, data): anexa PDF extra. Campos: name*, url_pdf | base64_pdf. [Flattened action: update]
Annotations the server declares
- title: zapsign_documents_write_update
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
zapsign_signers_write_addGerenciar signatários no ZapSign.No findings
Why it is in this group
- The name "zapsign_signers_write_add" says "write": a word for a change.
Description, as the server wrote it Gerenciar 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_whatsapp, require_document_photo. - update (signer_token, data): atualiza (só antes de assinar) ou reenvia lembrete. Mesmos campos de add. - remove (signer_token): remove (não pode remover quem já assinou nem o único signatário). - sign (data): assina em lote via API (assíncrono). Campos: signer_tokens[]*; opc selfie_photo, document_photo_url. (user_token é injetado automaticamente.) [Flattened action: add]
Annotations the server declares
- title: zapsign_signers_write_add
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
zapsign_signers_write_removeGerenciar signatários no ZapSign.No findings
Why it is in this group
- The name "zapsign_signers_write_remove" says "write": a word for a change.
Description, as the server wrote it Gerenciar 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_whatsapp, require_document_photo. - update (signer_token, data): atualiza (só antes de assinar) ou reenvia lembrete. Mesmos campos de add. - remove (signer_token): remove (não pode remover quem já assinou nem o único signatário). - sign (data): assina em lote via API (assíncrono). Campos: signer_tokens[]*; opc selfie_photo, document_photo_url. (user_token é injetado automaticamente.) [Flattened action: remove]
Annotations the server declares
- title: zapsign_signers_write_remove
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
zapsign_signers_write_signGerenciar signatários no ZapSign.No findings
Why it is in this group
- The name "zapsign_signers_write_sign" says "write": a word for a change.
Description, as the server wrote it Gerenciar 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_whatsapp, require_document_photo. - update (signer_token, data): atualiza (só antes de assinar) ou reenvia lembrete. Mesmos campos de add. - remove (signer_token): remove (não pode remover quem já assinou nem o único signatário). - sign (data): assina em lote via API (assíncrono). Campos: signer_tokens[]*; opc selfie_photo, document_photo_url. (user_token é injetado automaticamente.) [Flattened action: sign]
Annotations the server declares
- title: zapsign_signers_write_sign
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
zapsign_signers_write_updateGerenciar signatários no ZapSign.No findings
Why it is in this group
- The name "zapsign_signers_write_update" says "write": a word for a change.
Description, as the server wrote it Gerenciar 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_whatsapp, require_document_photo. - update (signer_token, data): atualiza (só antes de assinar) ou reenvia lembrete. Mesmos campos de add. - remove (signer_token): remove (não pode remover quem já assinou nem o único signatário). - sign (data): assina em lote via API (assíncrono). Campos: signer_tokens[]*; opc selfie_photo, document_photo_url. (user_token é injetado automaticamente.) [Flattened action: update]
Annotations the server declares
- title: zapsign_signers_write_update
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
zapsign_templates_write_createGerenciar templates no ZapSign.No findings
Why it is in this group
- The name "zapsign_templates_write_create" says "write": a word for a change.
Description, as the server wrote it Gerenciar 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, lang, observers[], first_signer, folder_path/token, redirect_link. - delete (template_token): irreversível. [Flattened action: create]
Annotations the server declares
- title: zapsign_templates_write_create
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
zapsign_templates_write_deleteGerenciar templates no ZapSign.No findings
Why it is in this group
- The name "zapsign_templates_write_delete" says "write": a word for a change.
Description, as the server wrote it Gerenciar 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, lang, observers[], first_signer, folder_path/token, redirect_link. - delete (template_token): irreversível. [Flattened action: delete]
Annotations the server declares
- title: zapsign_templates_write_delete
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
zapsign_templates_write_updateGerenciar templates no ZapSign.No findings
Why it is in this group
- The name "zapsign_templates_write_update" says "write": a word for a change.
Description, as the server wrote it Gerenciar 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, lang, observers[], first_signer, folder_path/token, redirect_link. - delete (template_token): irreversível. [Flattened action: update]
Annotations the server declares
- title: zapsign_templates_write_update
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
zapsign_webhooks_write_createGerenciar webhooks no ZapSign (não há endpoint de listagem na API).No findings
Why it is in this group
- The name "zapsign_webhooks_write_create" says "write": a word for a change.
Description, as the server wrote it Gerenciar 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 webhook pelo id retornado na criação. [Flattened action: create] Bulk support: accepts ids for batched execution.
Annotations the server declares
- title: zapsign_webhooks_write_create
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
zapsign_webhooks_write_deleteGerenciar webhooks no ZapSign (não há endpoint de listagem na API).No findings
Why it is in this group
- The name "zapsign_webhooks_write_delete" says "write": a word for a change.
Description, as the server wrote it Gerenciar 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 webhook pelo id retornado na criação. [Flattened action: delete] Bulk support: accepts ids for batched execution.
Annotations the server declares
- title: zapsign_webhooks_write_delete
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
Only reads 11Show 11 read-only tools
connectReturns connection status and URLs.1 finding
Why it is in this group
- The description's first verb is "return": a word for reading.
Findings
- Info
The description mentions "credentials".
What this check looks forMatched text
description: "...nticated:true and empty pending[]. When credentials are missing, returns connect_url for th..."
Description, as the server wrote it Returns 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.
Annotations the server declares
- title: Connection Status
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
show_versionShow the current MCP platform and adapter versions.No findings
Why it is in this group
- The name "show_version" says "show": a word for reading.
Description, as the server wrote it Show the current MCP platform and adapter versions.
Annotations the server declares
- title: Show Version
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
toolkit_infoReturns the current toolkit state: installed MCPs, their connection status, the accounts connected to each one, and how many catalog tools each exposes.No findings
Why it is in this group
- The description's first verb is "return": a word for reading.
Description, as the server wrote it Returns the current toolkit state: installed MCPs, their connection status, the accounts connected to each one, and how many catalog tools each exposes.
Annotations the server declares
- title: Toolkit Info
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
zapsign_checks_getVerificação de antecedentes no ZapSign (leitura).No findings
Why it is in this group
- The name "zapsign_checks_get" says "get": a word for reading.
Description, as the server wrote it Verificaçã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.
Annotations the server declares
- title: zapsign_checks_get
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
zapsign_documents_getDocumentos de assinatura no ZapSign (leitura).Reads private dataNo findings
Why it is in this group
- The name "zapsign_documents_get" says "get": a word for reading.
What it can reach
- private-dataThe name "zapsign_documents_get" says "get" and "document": it reads documents.
- private-dataThe input names a folder (input.folder_path), and the tool reads: it reads files.
Description, as the server wrote it Documentos 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 arquivo, que expiram em 60min); signer_log (doc_token — trilha de auditoria; download_pdf=true retorna o PDF do log). [Flattened action: get]
Annotations the server declares
- title: zapsign_documents_get
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
zapsign_documents_listDocumentos de assinatura no ZapSign (leitura).Reads private dataNo findings
Why it is in this group
- The name "zapsign_documents_list" says "list": a word for reading.
What it can reach
- private-dataThe name "zapsign_documents_list" says "list" and "document": it reads documents.
- private-dataThe input names a folder (input.folder_path), and the tool reads: it reads files.
Description, as the server wrote it Documentos 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 arquivo, que expiram em 60min); signer_log (doc_token — trilha de auditoria; download_pdf=true retorna o PDF do log). [Flattened action: list]
Annotations the server declares
- title: zapsign_documents_list
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
zapsign_documents_signer_logDocumentos de assinatura no ZapSign (leitura).Reads private dataNo findings
Why it is in this group
- The name "zapsign_documents_signer_log" says "log": a word for reading.
What it can reach
- private-dataThe name "zapsign_documents_signer_log" says "log" and "document": it reads documents.
- private-dataThe input names a folder (input.folder_path), and the tool reads: it reads files.
Description, as the server wrote it Documentos 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 arquivo, que expiram em 60min); signer_log (doc_token — trilha de auditoria; download_pdf=true retorna o PDF do log). [Flattened action: signer_log]
Annotations the server declares
- title: zapsign_documents_signer_log
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
zapsign_list_accountsLista contas ZapSign vinculadas a este install — id e apelido.No findings
Why it is in this group
- The name "zapsign_list_accounts" says "list": a word for reading.
Description, as the server wrote it Lista contas ZapSign vinculadas a este install — id e apelido.
Annotations the server declares
- title: zapsign_list_accounts
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
zapsign_signers_getSignatários no ZapSign (leitura).No findings
Why it is in this group
- The name "zapsign_signers_get" says "get": a word for reading.
Description, as the server wrote it Signatários no ZapSign (leitura). Ação: get (signer_token — status, sign_url, visualizações, geo, auth_mode etc.). [Flattened action: get]
Annotations the server declares
- title: zapsign_signers_get
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
zapsign_templates_getTemplates (modelos DOCX) no ZapSign (leitura).No findings
Why it is in this group
- The name "zapsign_templates_get" says "get": a word for reading.
Description, as the server wrote it Templates (modelos DOCX) no ZapSign (leitura). Ações: list (page — 20/página); get (template_token — inclui inputs[] das variáveis {{VAR}}). [Flattened action: get]
Annotations the server declares
- title: zapsign_templates_get
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
zapsign_templates_listTemplates (modelos DOCX) no ZapSign (leitura).No findings
Why it is in this group
- The name "zapsign_templates_list" says "list": a word for reading.
Description, as the server wrote it Templates (modelos DOCX) no ZapSign (leitura). Ações: list (page — 20/página); get (template_token — inclui inputs[] das variáveis {{VAR}}). [Flattened action: list]
Annotations the server declares
- title: zapsign_templates_list
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: 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.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.
- Reads private data3
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
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.
Looked at Nov 20, 2026, 19:39 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
- 24
- 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
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 24 tools that change things (24 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://api.mcp.ai/p_zapsign: tools/list returned 35 tools to an anonymous client, including zapsign_documents_write_create (write), zapsign_documents_write_create_from_template (write), zapsign_documents_write_update (write), zapsign_documents_write_delete (write), zapsign_documents_write_refuse (write) and 19 more
Findings
Matches of fixed checks, with the text they matched.
- Infoconnect
The description mentions "credentials".
What this check looks forMatched text
description: "...nticated:true and empty pending[]. When credentials are missing, returns connect_url for th..."
- Infomarketplace
The description mentions "credential".
What this check looks forMatched text
description: "...ating the tool list. If the MCP needs a credential/login, invoke returns a connect link; i..."
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 0.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http zapsign https://api.mcp.ai/p_zapsignclaude mcp add --transport http zapsign https://api.mcp.ai/p_zapsignRun 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.
{
"permissions": {
"allow": [
"mcp__zapsign__zapsign_list_accounts",
"mcp__zapsign__zapsign_documents_list",
"mcp__zapsign__zapsign_documents_get",
"mcp__zapsign__zapsign_documents_signer_log",
"mcp__zapsign__zapsign_signers_get",
"mcp__zapsign__zapsign_templates_list",
"mcp__zapsign__zapsign_templates_get",
"mcp__zapsign__zapsign_checks_get",
"mcp__zapsign__show_version",
"mcp__zapsign__connect",
"mcp__zapsign__toolkit_info"
],
"ask": [
"mcp__zapsign__zapsign_documents_write_create",
"mcp__zapsign__zapsign_documents_write_create_from_template",
"mcp__zapsign__zapsign_documents_write_update",
"mcp__zapsign__zapsign_documents_write_delete",
"mcp__zapsign__zapsign_documents_write_refuse",
"mcp__zapsign__zapsign_documents_write_place_signatures",
"mcp__zapsign__zapsign_documents_write_add_extra_doc",
"mcp__zapsign__zapsign_signers_write_add",
"mcp__zapsign__zapsign_signers_write_update",
"mcp__zapsign__zapsign_signers_write_remove",
"mcp__zapsign__zapsign_signers_write_sign",
"mcp__zapsign__zapsign_templates_write_create",
"mcp__zapsign__zapsign_templates_write_update",
"mcp__zapsign__zapsign_templates_write_delete",
"mcp__zapsign__zapsign_webhooks_write_create",
"mcp__zapsign__zapsign_webhooks_write_delete",
"mcp__zapsign__zapsign_checks_write_create",
"mcp__zapsign__zapsign_account_plan",
"mcp__zapsign__zapsign_account_users",
"mcp__zapsign__zapsign_account_write_create_user",
"mcp__zapsign__zapsign_account_write_delete_user",
"mcp__zapsign__report_bug",
"mcp__zapsign__marketplace",
"mcp__zapsign__authenticate"
],
"deny": []
}
}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 zapsign. Review it before you use it.
Capability tags behind 4 rules
- mcp__zapsign__zapsign_documents_list private-data
- mcp__zapsign__zapsign_documents_get private-data
- mcp__zapsign__zapsign_documents_signer_log private-data
- mcp__zapsign__marketplace 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.github.mcp-dir/zapsign-mcp/verify?hash=0b268c93722e2a742b1815d417686849626c2605ee3cd43b554ef281fc76a7c6" | jq -e '.changed == false'Pinned hash 0b268c93722e, from Nov 8, 2026, 10:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.mcp-dir/zapsign-mcp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.mcp-dir/zapsign-mcp)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:40 UTC.
ZapSign MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the ZapSign MCP server safe?
- No scan can promise that. What its definitions show: 35 tools, 24 of which can change, send or delete something, and 2 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the ZapSign MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the ZapSign MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the ZapSign MCP server have?
- 35 tools: 24 write, 11 read. zapsign_documents_write_create, zapsign_documents_write_create_from_template, zapsign_documents_write_update, zapsign_documents_write_delete, zapsign_documents_write_refuse, zapsign_documents_write_place_signatures, zapsign_documents_write_add_extra_doc, zapsign_signers_write_add and 27 more.
Does the ZapSign MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the ZapSign MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the ZapSign MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 8, 2026.