LeashIndex Get the report

Index / messaging

nintact

com-nintact-nintact declares 32 capabilities across 32 tools, with 2 critical issues.

89/100 exposureHigh exposure

Manifest recorded 2026-10-11 from tools/list answered by the npm package nintact-mcp@0.5.1 (published to npm as nintact-mcp, listed in the official MCP registry as com.nintact/nintact 0.5.2), run in an isolated container with no network access and placeholder credentials. 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 32 tools

32 of 32 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 · 7 of 32 tools

7 tools are classified as irreversible and declare no limit.

high · no-expiry · All 32 tools

32 of 32 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 32 tools

32 of 32 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 · 12 of 32 tools

12 tools can modify data and declare no limit.

low · uncapped-read · 13 of 32 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
check_deliverabilityread inferred
design_formwrite assumed
create_formwrite inferred
list_formsread inferred
get_formread inferred
update_formwrite inferred
duplicate_formwrite assumed
set_form_logowrite inferred
remove_form_logodelete inferred
delete_formdelete inferred
list_messagesread inferred
get_messageread inferred
update_message_statusread inferred
regenerate_draftsend inferred
update_draftwrite inferred
approve_draftwrite inferred
list_knowledgeread inferred
add_knowledgewrite inferred
update_knowledgewrite inferred
delete_knowledgedelete inferred
get_organizationread inferred
update_organizationwrite inferred
list_inbound_addressesread inferred
create_inbound_addresswrite inferred
transfer_workspacewrite inferred
scan_site_for_knowledgeread inferred
get_sending_domainread inferred
set_sending_domainsend inferred
verify_sending_domainread inferred
remove_sending_domaindelete inferred
delete_inbound_addressdelete inferred
get_usageread inferred
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.