LeashIndex Get the report

Index / messaging

com.mcparmory/mailersend

com-mcparmory-mailersend declares 89 capabilities across 89 tools, with 2 critical issues.

100/100 exposureHigh exposure

Manifest recorded 2026-10-11 from tools/list answered by the PyPI package mcparmory-mailersend==1.0.2 (published to PyPI as mcparmory-mailersend, listed in the official MCP registry as com.mcparmory/mailersend 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 · irreversible-uncapped · 22 of 89 tools

22 tools are classified as irreversible and declare no limit.

critical · no-revocation · All 89 tools

89 of 89 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.

high · no-expiry · All 89 tools

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

89 of 89 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 · 13 of 89 tools

13 tools can modify data and declare no limit.

low · uncapped-read · 54 of 89 tools

54 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
send_emailsend inferred
send_bulk_emailssend inferred
get_bulk_email_statusread declared
list_activities_for_domainread declared
get_activityread declared
get_activity_data_by_date_rangeread declared
list_opens_by_countryread declared
list_opens_by_user_agentread declared
get_opens_by_reading_environmentread declared
list_domainsread declared
create_domainwrite inferred
get_domainread declared
delete_domaindestructive declared
list_recipients_for_domainread declared
update_domain_settingswrite inferred
list_dns_recordsread declared
get_domain_verification_statusread declared
list_sender_identitiesread declared
create_sender_identitywrite inferred
get_sender_identityread declared
update_sender_identitywrite inferred
delete_sender_identitydestructive declared
get_sender_identity_by_emailread declared
update_sender_identity_by_emailwrite inferred
delete_sender_identity_by_emaildestructive declared
list_inbound_routesread declared
get_inbound_routeread declared
update_inbound_routewrite inferred
delete_inbound_routedestructive declared
list_messagesread declared
get_messageread declared
list_scheduled_messagesread declared
get_scheduled_messageread declared
delete_scheduled_messagedestructive declared
list_blocklist_recipientsread declared
add_blocklist_recipientsdestructive declared
delete_blocklist_recipientsdestructive declared
list_hard_bounces_recipientsread declared
add_recipients_to_hard_bounces_suppressionwrite inferred
delete_hard_bounces_recipientsdestructive declared
list_spam_complaint_recipientsread declared
add_spam_complaints_recipientswrite inferred
delete_spam_complaints_recipientsdestructive declared
list_unsubscribed_recipientsread declared
add_unsubscribe_recipientswrite inferred
delete_unsubscribed_recipientsdestructive declared
list_recipientsread declared
get_recipientread declared
delete_recipientdestructive declared
list_templatesread declared
list_webhooksread declared
get_webhookread declared
delete_webhookdestructive declared
verify_emailread inferred
list_email_verification_listsread declared
create_email_verification_listread inferred
get_email_verification_listread declared
verify_email_verification_listread declared
list_email_verification_resultsread declared
update_token_statusdestructive declared
delete_tokendestructive declared
list_usersread declared
get_userread declared
update_user_rolewrite inferred
delete_userdestructive declared
send_smssend inferred
list_sms_phone_numbersread declared
get_sms_phone_numberread declared
update_sms_phone_number_pause_statusread inferred
delete_sms_numberdestructive declared
list_sms_messagesread declared
get_sms_messageread declared
list_sms_activitiesread declared
get_sms_message_activityread declared
list_sms_recipientsread declared
get_sms_recipientread declared
update_sms_recipient_statusread inferred
list_sms_webhooksread declared
get_sms_webhookread declared
update_sms_webhookwrite inferred
delete_sms_webhookdestructive declared
list_sms_inbound_routesread declared
get_sms_inbound_routeread declared
update_sms_inbound_routewrite inferred
delete_sms_inbound_routedestructive declared
list_smtp_usersread declared
get_smtp_userread declared
update_smtp_userwrite inferred
delete_smtp_userdestructive 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.