com.mcparmory/mailersend
OCI · GHCR.IO/MCPARMORY/MAILERSEND:1.0.2 · 2 COMPONENTS · SCANNED SEP 20
Send transactional emails, manage domains, and track delivery analytics
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security0
- Malware scan not yet available for this package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
Provenance & Transparency32
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 130 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 6061 tokens (~68/item across 89 items; 89 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
- Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety96
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 17 of 20 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "send_email" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Partial
- An AI judge read all 89 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
How do I install the com.mcparmory/mailersend MCP server?
com.mcparmory/mailersend runs locally as a container image, launched with docker run --rm -i ghcr.io/mcparmory/mailersend:1.0.2. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/mcparmory/mailersend:1.0.2
claude mcp add com-mcparmory-mailersend -- docker run --rm -i ghcr.io/mcparmory/mailersend:1.0.2
{
"mcpServers": {
"com-mcparmory-mailersend": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/mailersend:1.0.2"
]
}
}
} {
"servers": {
"com-mcparmory-mailersend": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/mailersend:1.0.2"
]
}
}
} codex mcp add com-mcparmory-mailersend -- docker run --rm -i ghcr.io/mcparmory/mailersend:1.0.2
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-mcparmory-mailersend": {
"type": "local",
"command": [
"docker",
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/mailersend:1.0.2"
],
"enabled": true
}
}
} mcp_servers:
com-mcparmory-mailersend:
command: "docker"
args: ["run", "--rm", "-i", "ghcr.io/mcparmory/mailersend:1.0.2"] {
"McpServers": {
"com-mcparmory-mailersend": {
"Transport": "stdio",
"Command": "docker",
"Arguments": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/mailersend:1.0.2"
]
}
}
} {
"mcpServers": {
"com-mcparmory-mailersend": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/mailersend:1.0.2"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 −3
- Stability: pass → 0.80 functional
- 18 Sept 26 +1
- Stability: 0.97 → pass security
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 −3
- Stability: pass → 0.80 functional
- 11 Sept 26 +1
- Stability: 0.97 → pass security
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed oci/ghcr.io/mcparmory/mailersend:1.0.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
list_email_verification_lists List Email Verification Lists ~32
Retrieve all email verification lists available in the system. Use this to view existing verification lists and their configurations.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_email_verification_results List Email Verification Results ~59
Retrieve the verification results for a completed email verification list. Returns detailed status and outcome information for each email address that was processed.
| Name | Type | Req | Description |
|---|---|---|---|
| email_verification_id | string | yes | The unique identifier of the email verification list for which to retrieve results. |
No output schema declared.
No examples provided.
list_hard_bounces_recipients List Hard Bounces Recipients ~42
Retrieve all recipients from the hard bounces suppression list. This list contains email addresses that have permanently failed delivery and should not receive future messages.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_inbound_routes List Inbound Routes ~31
Retrieve a list of all configured inbound routes. Use this to view routing rules for incoming messages or requests.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_messages List Messages ~30
Retrieve a list of all messages. Use this operation to fetch messages for display, filtering, or further processing.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_opens_by_country List Opens by Country ~105
Retrieve email open metrics aggregated by country for a specified date range. Returns open counts and statistics grouped by geographic location.
| Name | Type | Req | Description |
|---|---|---|---|
| date_from | string | yes | Start of the date range as a Unix timestamp (seconds since epoch). Defines the beginning of the analytics period to query. |
| date_to | string | yes | End of the date range as a Unix timestamp (seconds since epoch). Defines the end of the analytics period to query. Must be equal to or after date_from. |
No output schema declared.
No examples provided.
list_opens_by_user_agent List Opens by User Agent ~110
Retrieves analytics data showing the number of opens grouped by user-agent within a specified time range. Use this to understand which browsers, devices, and applications are opening your content.
| Name | Type | Req | Description |
|---|---|---|---|
| date_from | string | yes | Start of the time range as a Unix timestamp (seconds since epoch). This defines the beginning of the analytics period to query. |
| date_to | string | yes | End of the time range as a Unix timestamp (seconds since epoch). This defines the end of the analytics period to query. |
No output schema declared.
No examples provided.
list_recipients List Recipients ~36
Retrieve a list of all recipients available in the system. Use this to view recipient configurations and details for message delivery or communication purposes.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_recipients_for_domain List Recipients for Domain ~53
Retrieve all recipients associated with a specific domain. This returns the list of email recipients configured for the given domain.
| Name | Type | Req | Description |
|---|---|---|---|
| domain_id | string | yes | The unique identifier of the domain for which to retrieve recipients. |
No output schema declared.
No examples provided.
list_scheduled_messages List Scheduled Messages ~33
Retrieve all scheduled messages that are queued for future delivery. Use this to view pending message schedules and their delivery status.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_sender_identities List Sender Identities ~28
Retrieve a list of all configured sender identities available for sending messages or emails from this account.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_sms_activities List SMS Activities ~34
Retrieve a list of all SMS activities. Use this to view the history and status of SMS messages sent through the system.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_sms_inbound_routes List SMS Inbound Routes ~34
Retrieve all configured SMS inbound routes for your account. This returns the complete list of routes that handle incoming SMS messages.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_sms_messages List SMS Messages ~29
Retrieve a list of all SMS messages. Use this operation to fetch SMS message records from the system.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_sms_phone_numbers List SMS Phone Numbers ~37
Retrieve a list of all SMS phone numbers available in your account. Use this to view phone numbers configured for sending and receiving SMS messages.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_sms_recipients List SMS Recipients ~35
Retrieve a list of all SMS recipients configured in the system. Use this to view and manage contacts eligible for SMS communications.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_sms_webhooks List SMS Webhooks ~71
Retrieve all SMS webhooks configured for a specific SMS phone number. This allows you to view all webhook endpoints that are currently set up to receive SMS events for the given number.
| Name | Type | Req | Description |
|---|---|---|---|
| sms_number_id | string | yes | The unique identifier of the SMS phone number for which you want to retrieve configured webhooks. |
No output schema declared.
No examples provided.
list_smtp_users List SMTP Users ~52
Retrieve all SMTP users configured for a specific domain. Returns a list of SMTP user accounts associated with the domain.
| Name | Type | Req | Description |
|---|---|---|---|
| domain_id | string | yes | The unique identifier of the domain for which to retrieve SMTP users. |
No output schema declared.
No examples provided.
list_spam_complaint_recipients List Spam Complaint Recipients ~37
Retrieve all email addresses that have been added to the spam complaints suppression list, preventing future sends to these recipients.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_templates List Templates ~25
Retrieve all available templates. Use this to discover template options for your workflows or integrations.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_unsubscribed_recipients List Unsubscribed Recipients ~41
Retrieve all recipients from the unsubscribes suppression list. This list contains email addresses that have opted out of communications and should not receive messages.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_users List Users ~29
Retrieve a complete list of all users in the system. Returns user records with their associated metadata and details.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_webhooks List Webhooks ~55
Retrieve all webhooks configured for a specific domain. Returns a list of webhook configurations including their endpoints, event subscriptions, and status.
| Name | Type | Req | Description |
|---|---|---|---|
| domain_id | string | yes | The unique identifier of the domain for which to retrieve webhooks. |
No output schema declared.
No examples provided.
send_bulk_emails Send Bulk Emails ~63
Send multiple emails in a single batch request. Accepts an array of email configurations to be processed and delivered.
| Name | Type | Req | Description |
|---|---|---|---|
| body | array | yes | Array of email objects to send. Each object should contain recipient, subject, and message content. Order is preserved for processing. |
No output schema declared.
No examples provided.
send_email Send Email ~219
Send an email message from a specified sender address to one or more recipients. Use this operation to deliver transactional or notification emails with a subject line and message body.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | The sender's email address in standard email format (e.g., info@yourdomain.com). This address will appear as the 'From' field in the email. | |
| name | string | – | The sender's display name or organization name that appears alongside the email address (e.g., 'Company Name'). Optional; if omitted, only the email address will be displayed. |
| subject | string | yes | The email subject line. Provide a clear, concise subject that summarizes the email content (e.g., 'Hello Client'). |
| text | string | yes | The email message body as plain text. Include the main content and any relevant information for the recipient (e.g., 'This is just a friendly hello from your friends.'). |
| to | array | yes | Array of recipient email addresses. Each address should be in standard email format. At least one recipient is required. |
No output schema declared.
No examples provided.
send_sms Send SMS ~168
Send an SMS message to one or more recipients with optional personalization support. Supports template variables for dynamic content customization.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | yes | The sender's phone number in E.164 format (e.g., +19191234567). This is the number that will appear as the message source. |
| personalization | array | – | Optional array of personalization objects that map template variables to recipient-specific values. Used to customize message content for each recipient based on template variables in the text parame… |
| text | string | yes | The message content as a string. Supports template variables (e.g., {{name}}) that will be replaced with values from the personalization array for each recipient. |
| to | array | yes | Array of recipient phone numbers in E.164 format. Each number will receive the message independently. |
No output schema declared.
No examples provided.
update_domain_settings Update Domain Settings ~76
Update configuration settings for a specific domain. Allows modification of domain-level preferences including content tracking behavior.
| Name | Type | Req | Description |
|---|---|---|---|
| domain_id | string | yes | The unique identifier of the domain whose settings should be updated. |
| track_content | boolean | – | Enable or disable content tracking for this domain. When enabled, the system will monitor and record domain content activity. |
No output schema declared.
No examples provided.
update_inbound_route Update Inbound Route ~267
Update configuration settings for an inbound route, including its name, domain enablement, priority, and filtering rules. Changes take effect immediately for new incoming requests matching this route.
| Name | Type | Req | Description |
|---|---|---|---|
| catch_filterType | string | – | The type of catch filter to apply as a fallback. Use 'catch_all' to handle requests that don't match other filters, or specify a more specific filter type. |
| domain_enabled | boolean | – | Enable or disable domain-based routing for this inbound route. When enabled, the route processes domain-specific logic. |
| forwards | array | – | An ordered list of forwarding destinations where matched inbound requests should be routed. The order determines the sequence in which destinations are attempted. |
| inbound_id | string | yes | The unique identifier of the inbound route to update. This ID is required to target the specific route for modification. |
| inbound_priority | integer | – | The priority level for this route when multiple routes could match the same inbound request. Lower numbers indicate higher priority and are evaluated first. |
| match_filterType | string | – | The type of matching filter to apply. Use 'match_all' to process all requests, or specify a more restrictive filter type to target specific request patterns. |
| name | string | – | A human-readable name for the inbound route to help identify its purpose or destination. |
No output schema declared.
No examples provided.
update_sender_identity Update Sender Identity ~82
Update the configuration of an existing sender identity, such as its display name. This allows you to modify how your sender identity appears in outgoing communications.
| Name | Type | Req | Description |
|---|---|---|---|
| identity_id | string | yes | The unique identifier of the sender identity to update. |
| name | string | – | The new display name for the sender identity. This is how the identity will be presented in outgoing messages. |
No output schema declared.
No examples provided.
update_sender_identity_by_email Update Sender Identity by Email ~87
Update the configuration of a sender identity using its email address. Allows modification of sender identity properties such as the display name.
| Name | Type | Req | Description |
|---|---|---|---|
| clientemail.com | string | yes | The email address of the sender identity to update. Must be a valid email format. |
| name | string | – | The new display name for the sender identity. Optional field to customize how the sender appears in outgoing communications. |
No output schema declared.
No examples provided.
update_sms_inbound_route Update SMS Inbound Route ~150
Update an existing inbound SMS route configuration, including the associated phone number, display name, webhook destination, and activation status.
| Name | Type | Req | Description |
|---|---|---|---|
| enabled | boolean | yes | Whether this inbound route is active and should process incoming messages. |
| forward_url | string | yes | The webhook URL where incoming SMS messages will be forwarded. Must be a valid URI (e.g., https://yourapp.com/hook). |
| name | string | yes | A descriptive name for this inbound route (e.g., 'Inbound'). |
| sms_inbound_id | string | yes | The unique identifier of the SMS inbound route to update. |
| sms_number_id | string | yes | The ID of the SMS phone number to associate with this inbound route. |
No output schema declared.
No examples provided.
update_sms_phone_number_pause_status Update SMS Phone Number Pause Status ~83
Update the pause status of an SMS phone number. Use this to temporarily disable or re-enable an SMS phone number for sending messages.
| Name | Type | Req | Description |
|---|---|---|---|
| paused | boolean | yes | Set to true to pause the SMS phone number (disable message sending), or false to resume it. |
| sms_number_id | string | yes | The unique identifier of the SMS phone number to update. |
No output schema declared.
No examples provided.
update_sms_recipient_status Update SMS Recipient Status ~91
Update the subscription status of an SMS recipient. Use this to activate a recipient or mark them as opted out from SMS communications.
| Name | Type | Req | Description |
|---|---|---|---|
| sms_recipient_id | string | yes | The unique identifier of the SMS recipient whose status you want to update. |
| status | string | yes | The new subscription status for the recipient. Set to 'active' to enable SMS communications or 'opt_out' to disable them. |
No output schema declared.
No examples provided.
update_sms_webhook Update SMS Webhook ~83
Update the configuration of an SMS webhook by enabling or disabling it. This allows you to control whether the webhook is active without deleting it.
| Name | Type | Req | Description |
|---|---|---|---|
| enabled | boolean | yes | Whether the SMS webhook should be active and receive events. Set to true to enable or false to disable. |
| sms_webhook_id | string | yes | The unique identifier of the SMS webhook to update. |
No output schema declared.
No examples provided.
update_smtp_user Update SMTP User ~105
Update an SMTP user's configuration within a domain, including their display name and enabled status.
| Name | Type | Req | Description |
|---|---|---|---|
| domain_id | string | yes | The unique identifier of the domain containing the SMTP user. |
| enabled | boolean | yes | Whether the SMTP user account is active and can be used for authentication. |
| name | string | yes | The display name for the SMTP user (e.g., 'New Name'). |
| smtp_user_id | string | yes | The unique identifier of the SMTP user to be updated. |
No output schema declared.
No examples provided.
update_token_status Update Token Status ~89
Update the operational status of a token by pausing or activating it. Use this to control whether a token is currently active or temporarily paused.
| Name | Type | Req | Description |
|---|---|---|---|
| status | string | yes | The desired operational status for the token. Set to 'active' to enable the token or 'pause' to temporarily disable it. |
| token_id | string | yes | The unique identifier of the token whose status you want to update. |
No output schema declared.
No examples provided.
update_user_role Update User Role ~90
Update the role assignment for a specific user. This operation allows you to change a user's access level or permissions by assigning them a new role (e.g., Admin).
| Name | Type | Req | Description |
|---|---|---|---|
| role | string | yes | The new role to assign to the user. Valid roles include Admin and other predefined role types supported by the system. |
| user_id | string | yes | The unique identifier of the user whose role should be updated. |
No output schema declared.
No examples provided.
verify_email Verify Email ~60
Verify the validity and deliverability of an email address. This operation checks whether the provided email address is properly formatted and active.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | The email address to verify. Must be a valid email format (e.g., user@domain.com). |
No output schema declared.
No examples provided.
verify_email_verification_list Verify Email Verification List ~67
Verify an email verification list by its ID. This operation processes and validates the email addresses in the specified verification list.
| Name | Type | Req | Description |
|---|---|---|---|
| email_verification_id | string | yes | The unique identifier of the email verification list to verify. This ID references a specific list that will be processed and validated. |
No output schema declared.
No examples provided.
What is the com.mcparmory/mailersend MCP server?
com.mcparmory/mailersend is an MCP server listed in the public MCP registry as com.mcparmory/mailersend. Send transactional emails, manage domains, and track delivery analytics. This page covers its container image (ghcr.io/mcparmory/mailersend:1.0.2).
Is the com.mcparmory/mailersend MCP server safe to use?
com.mcparmory/mailersend scores 50 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the com.mcparmory/mailersend MCP server expose?
com.mcparmory/mailersend exposes 89 tools: send_email, send_bulk_emails, get_bulk_email_status, list_activities_for_domain, get_activity, and 84 more. Their descriptions and schemas cost roughly 6,061 tokens of context every time the server is loaded.
Is the com.mcparmory/mailersend MCP server still maintained?
com.mcparmory/mailersend is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.