LeashIndex Get the report

Index / storage

ZapSign

io-github-mcp-dir-zapsign-mcp declares 35 capabilities across 35 tools, with 2 critical issues.

89/100 exposureHigh exposure

Manifest recorded 2026-10-11 from tools/list on https://api.mcp.ai/p_zapsign, published in the official MCP registry as io.github.mcp-dir/zapsign-mcp 0.1.0. The date changes only when the manifest does. Not verified by a maintainer.

Issues

These describe what this server's manifest declares. A product can provide controls that MCP has no way to express — token revocation, an admin console, audit logs — and this page cannot see them. The absence of a declaration is not evidence that a control is absent.

critical · no-revocation · All 35 tools

35 of 35 tools declare no way for the customer to switch them off once granted. This applies to every tool because MCP has no field in which to declare a revocation mechanism; the product may provide one outside MCP that a manifest cannot show.

critical · irreversible-uncapped · 5 of 35 tools

5 tools are classified as irreversible and declare no limit.

high · no-expiry · All 35 tools

35 of 35 tools declare no expiry. This applies to every tool because MCP has no field in which to declare an expiry; the product may provide one outside MCP that a manifest cannot show.

high · no-audit-trail · All 35 tools

35 of 35 tools declare no record of their actions that the customer can read. This applies to every tool because MCP has no field in which to declare an audit requirement; the product may provide one outside MCP that a manifest cannot show.

high · uncapped-write · 17 of 35 tools

17 tools can modify data and declare no limit.

low · uncapped-read · 13 of 35 tools

13 tools can read data and declare no limit.

Declared capabilities

How each tool was read. declared means the server's own annotation said so — self-reported and unverified. inferred is from the tool's name. assumed means nothing indicated either way.

ToolRead asBasis
zapsign_list_accountsread declared
zapsign_documents_listread declared
zapsign_documents_getread declared
zapsign_documents_signer_logread declared
zapsign_documents_write_createwrite inferred
zapsign_documents_write_create_from_templatewrite inferred
zapsign_documents_write_updatewrite inferred
zapsign_documents_write_deletedelete inferred
zapsign_documents_write_refusewrite inferred
zapsign_documents_write_place_signatureswrite inferred
zapsign_documents_write_add_extra_docwrite inferred
zapsign_signers_getread declared
zapsign_signers_write_addwrite inferred
zapsign_signers_write_updatewrite inferred
zapsign_signers_write_removedelete inferred
zapsign_signers_write_signwrite inferred
zapsign_templates_listread declared
zapsign_templates_getread declared
zapsign_templates_write_createwrite inferred
zapsign_templates_write_updatewrite inferred
zapsign_templates_write_deletedelete inferred
zapsign_webhooks_write_createwrite inferred
zapsign_webhooks_write_deletedelete inferred
zapsign_checks_getread declared
zapsign_checks_write_createwrite inferred
zapsign_account_planread declared
zapsign_account_usersread declared
zapsign_account_write_create_userwrite inferred
zapsign_account_write_delete_userdelete inferred
show_versionread declared
report_bugwrite assumed
connectread declared
toolkit_inforead declared
marketplacewrite assumed
authenticatewrite assumed
Answering this question about your own agent? The self-serve stack report applies the same reading to your own stack or server and gives you a dated document you can hand to a customer's security review. It is generated in your browser, with nobody to wait for. Buying one does not change this page, its score or its place in the index — see Independence.
Maintain this server? If this page misreads your manifest, or your server has changed, submit its current tools/list response and it will be re-scored and dated. Corrections are published alongside the original, not in place of it.