LeashIndex Get the report

Index / crm

com.mcparmory/resend

com-mcparmory-resend declares 63 capabilities across 63 tools, with 2 critical issues.

99/100 exposureHigh exposure

Manifest recorded 2026-10-11 from tools/list answered by the PyPI package mcparmory-resend==1.0.2 (published to PyPI as mcparmory-resend, listed in the official MCP registry as com.mcparmory/resend 1.0.2), run in an isolated container with no network access and no 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 63 tools

63 of 63 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 · 15 of 63 tools

15 tools are classified as irreversible and declare no limit.

high · no-expiry · All 63 tools

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

63 of 63 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 · 18 of 63 tools

18 tools can modify data and declare no limit.

low · uncapped-read · 30 of 63 tools

30 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
list_emailsread declared
send_emailsend inferred
get_emailread declared
cancel_emaildestructive declared
send_emails_batchsend inferred
list_attachments_for_emailread declared
get_email_attachmentread declared
list_emails_receivingread declared
get_received_emailread declared
list_email_attachmentsread declared
get_received_email_attachmentread declared
list_domainsread declared
create_domainwrite inferred
get_domainread declared
update_domainwrite inferred
delete_domaindestructive declared
verify_domainread inferred
list_api_keysread declared
create_api_keywrite inferred
delete_api_keydestructive declared
list_templatesread declared
create_templatewrite inferred
get_templateread declared
update_templatewrite inferred
delete_templatedestructive declared
publish_templatesend inferred
duplicate_templatewrite inferred
list_contactsread declared
create_contactwrite inferred
get_contactread declared
update_contactwrite inferred
delete_contactdestructive declared
list_broadcastsread declared
create_broadcastwrite inferred
get_broadcastread declared
update_broadcastwrite inferred
delete_broadcastdestructive declared
send_broadcastsend inferred
list_webhooksread declared
create_webhookwrite inferred
get_webhookread declared
update_webhookwrite inferred
delete_webhookdestructive declared
list_segmentsread declared
create_segmentwrite inferred
get_segmentread declared
delete_segmentdestructive declared
list_topicsread declared
create_topicwrite inferred
get_topicread declared
update_topicwrite inferred
delete_topicdestructive declared
list_contact_propertiesread declared
create_contact_propertywrite inferred
get_contact_propertyread declared
update_contact_propertywrite inferred
delete_contact_propertydestructive declared
list_contact_segmentsread declared
add_contact_to_segmentwrite inferred
remove_contact_from_segmentdestructive declared
list_contact_topicsread declared
list_logsread declared
get_logread declared
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.