com.mcparmory/mailersend
PYPI · MCPARMORY-MAILERSEND · 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 Security37
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Install-script risk not yet assessed.Unverified
- 2 of 41 dependencies flagged as unhealthy. View diagnostics → Partial
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: the license (MIT License) isn't a recognized OSI-approved license. 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 Management90
- Stability observed for 27 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 current MCP spec version (2026-07-28).Pass
How do I install the com.mcparmory/mailersend MCP server?
com.mcparmory/mailersend runs locally as a PyPI package, launched with uvx mcparmory-mailersend. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · mcparmory-mailersend
claude mcp add com-mcparmory-mailersend -- uvx mcparmory-mailersend
{
"mcpServers": {
"com-mcparmory-mailersend": {
"command": "uvx",
"args": [
"mcparmory-mailersend"
]
}
}
} {
"servers": {
"com-mcparmory-mailersend": {
"command": "uvx",
"args": [
"mcparmory-mailersend"
]
}
}
} codex mcp add com-mcparmory-mailersend -- uvx mcparmory-mailersend
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-mcparmory-mailersend": {
"type": "local",
"command": [
"uvx",
"mcparmory-mailersend"
],
"enabled": true
}
}
} openclaw mcp add com-mcparmory-mailersend --command uvx --arg mcparmory-mailersend
mcp_servers:
com-mcparmory-mailersend:
command: "uvx"
args: ["mcparmory-mailersend"] {
"McpServers": {
"com-mcparmory-mailersend": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"mcparmory-mailersend"
]
}
}
} assistant mcp add com-mcparmory-mailersend -t stdio -c uvx -a mcparmory-mailersend
{
"mcpServers": {
"com-mcparmory-mailersend": {
"command": "uvx",
"args": [
"mcparmory-mailersend"
]
}
}
} 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 +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.
- 18 Sept 26 −3
- Stability: pass → 0.83 functional
- 17 Sept 26 +1
- Stability: 0.97 → pass security
- 15 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.
- 13 Sept 26 −14
- Malware scan: pass → unverified ▼ security
- 12 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 11 Sept 26 −3
- Stability: pass → 0.80 functional
- 10 Sept 26 −14
- Malware scan: pass → unverified ▼ security
- Stability: 0.97 → pass security
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 pypi/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 | pypi |
Background: How many MCP packages publish verified provenance →
Dependencies 41 packages
| Packages resolved | 41 |
|---|---|
| Stale | 1 |
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
add_blocklist_recipients Add Blocklist Recipients ~92
Add one or more email recipients to the blocklist suppression list for a specific domain. Blocklisted recipients will not receive emails sent through this domain.
| Name | Type | Req | Description |
|---|---|---|---|
| domain_id | string | yes | The unique identifier for the domain to which blocklist recipients will be added. |
| recipients | array | yes | An array of email recipient addresses to add to the blocklist. Each item should be a valid email address string. |
No output schema declared.
No examples provided.
add_recipients_to_hard_bounces_suppression Add Recipients to Hard Bounces Suppression ~106
Add one or more email recipients to the hard bounces suppression list for a specific domain. Hard-bounced addresses will be suppressed from future email sends to prevent delivery failures.
| Name | Type | Req | Description |
|---|---|---|---|
| domain_id | string | yes | The unique identifier of the domain to which the hard bounce suppression list applies. |
| recipients | array | yes | An array of email recipient addresses to add to the hard bounces suppression list. Each item should be a valid email address string. |
No output schema declared.
No examples provided.
add_spam_complaints_recipients Add Spam Complaints Recipients ~97
Add one or more email recipients to the spam complaints suppression list for a specific domain. Suppressed recipients will not receive emails sent through this domain.
| Name | Type | Req | Description |
|---|---|---|---|
| domain_id | string | yes | The unique identifier of the domain to which spam complaint suppressions will be applied. |
| recipients | array | yes | A list of email addresses to add to the spam complaints suppression list. Each item should be a valid email address string. |
No output schema declared.
No examples provided.
add_unsubscribe_recipients Add Unsubscribe Recipients ~89
Add one or more email recipients to the unsubscribes suppression list for a specific domain, preventing them from receiving future messages.
| Name | Type | Req | Description |
|---|---|---|---|
| domain_id | string | yes | The unique identifier for the domain to which the unsubscribe recipients will be added. |
| recipients | array | yes | A list of email recipients to add to the unsubscribes suppression list. Each item should be a valid email address. |
No output schema declared.
No examples provided.
create_domain Create Domain ~61
Register a new domain in the system. The domain name should be a valid fully-qualified domain name (e.g., domain.com).
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | The fully-qualified domain name to register (e.g., domain.com). Must be a valid domain format. |
No output schema declared.
No examples provided.
create_email_verification_list Create Email Verification List ~99
Create a new email verification list with a name and set of email addresses to verify. This list can be used to batch-process email validation across multiple addresses.
| Name | Type | Req | Description |
|---|---|---|---|
| emails | array | yes | An array of email addresses to include in the verification list. Each item should be a valid email address string. |
| name | string | yes | A descriptive name for the email verification list (e.g., 'List'). Used to identify and organize verification batches. |
No output schema declared.
No examples provided.
create_sender_identity Create Sender Identity ~118
Register a new sender identity for your domain, enabling you to send emails from a specific email address with an associated display name.
| Name | Type | Req | Description |
|---|---|---|---|
| domain_id | string | yes | The unique identifier of your domain where this sender identity will be registered. |
| string | yes | The email address for this sender identity. Must be a valid email format (e.g., user@example.com). | |
| name | string | yes | The display name associated with this sender identity, shown to recipients when emails are sent (e.g., 'John Smith' or 'Support Team'). |
No output schema declared.
No examples provided.
delete_blocklist_recipients Delete Blocklist Recipients ~76
Remove recipients from the blocklist suppression list. Use the all parameter to delete all blocklisted recipients at once, or omit it to delete specific recipients via request body.
| Name | Type | Req | Description |
|---|---|---|---|
| all | boolean | – | When set to true, removes all recipients from the blocklist. Omit or set to false to delete only specified recipients. |
No output schema declared.
No examples provided.
delete_domain Delete Domain ~42
Permanently delete a domain and remove it from the system. This action cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| domain_id | string | yes | The unique identifier of the domain to delete. |
No output schema declared.
No examples provided.
delete_hard_bounces_recipients Delete Hard Bounces Recipients ~77
Remove recipients from the hard bounces suppression list. Set the all parameter to true to clear all hard bounced addresses, or omit it to remove specific recipients.
| Name | Type | Req | Description |
|---|---|---|---|
| all | boolean | – | When set to true, removes all recipients from the hard bounces suppression list. Omit this parameter to remove specific recipients instead. |
No output schema declared.
No examples provided.
delete_inbound_route Delete Inbound Route ~69
Permanently delete an inbound route by its ID. This action cannot be undone and will remove all routing rules associated with the specified inbound route.
| Name | Type | Req | Description |
|---|---|---|---|
| inbound_id | string | yes | The unique identifier of the inbound route to delete. This must be a valid inbound route ID that exists in the system. |
No output schema declared.
No examples provided.
delete_recipient Delete Recipient ~40
Permanently delete a recipient from the system. This action cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| recipient_id | string | yes | The unique identifier of the recipient to delete. |
No output schema declared.
No examples provided.
delete_scheduled_message Delete Scheduled Message ~47
Permanently delete a scheduled message by its ID, preventing it from being sent at its scheduled time.
| Name | Type | Req | Description |
|---|---|---|---|
| message_id | string | yes | The unique identifier of the scheduled message to delete. |
No output schema declared.
No examples provided.
delete_sender_identity Delete Sender Identity ~63
Permanently delete a sender identity from your account. Once deleted, this identity can no longer be used to send messages.
| Name | Type | Req | Description |
|---|---|---|---|
| identity_id | string | yes | The unique identifier of the sender identity to delete. This ID must correspond to an existing sender identity in your account. |
No output schema declared.
No examples provided.
delete_sender_identity_by_email Delete Sender Identity by Email ~56
Permanently delete a sender identity from your account using its email address. This action cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| clientemail.com | string | yes | The email address of the sender identity to delete. Must be a valid email format. |
No output schema declared.
No examples provided.
delete_sms_inbound_route Delete SMS Inbound Route ~58
Permanently delete an SMS inbound route by its ID. This action cannot be undone and will stop processing inbound SMS messages for this route.
| Name | Type | Req | Description |
|---|---|---|---|
| sms_inbound_id | string | yes | The unique identifier of the SMS inbound route to delete. |
No output schema declared.
No examples provided.
delete_sms_number Delete SMS Phone Number ~54
Permanently delete an SMS phone number from your account. This action cannot be undone and will remove the number from all associated configurations.
| Name | Type | Req | Description |
|---|---|---|---|
| sms_number_id | string | yes | The unique identifier of the SMS phone number to delete. |
No output schema declared.
No examples provided.
delete_sms_webhook Delete SMS Webhook ~73
Permanently delete an SMS webhook by its ID. Once deleted, the webhook will no longer receive SMS events.
| Name | Type | Req | Description |
|---|---|---|---|
| enabled | boolean | yes | A boolean flag indicating the desired state. Set to false to proceed with deletion. |
| sms_webhook_id | string | yes | The unique identifier of the SMS webhook to delete. |
No output schema declared.
No examples provided.
delete_smtp_user Delete SMTP User ~83
Permanently delete an SMTP user from a domain. This action cannot be undone and will immediately revoke the user's ability to send emails through this domain.
| Name | Type | Req | Description |
|---|---|---|---|
| domain_id | string | yes | The unique identifier of the domain that contains the SMTP user to be deleted. |
| smtp_user_id | string | yes | The unique identifier of the SMTP user to be deleted from the domain. |
No output schema declared.
No examples provided.
delete_spam_complaints_recipients Delete Spam Complaints Recipients ~81
Remove recipients from the spam complaints suppression list. Use the 'all' parameter to delete all recipients at once, or omit it to delete specific recipients via request body.
| Name | Type | Req | Description |
|---|---|---|---|
| all | boolean | – | When set to true, removes all recipients from the spam complaints suppression list. Omit or set to false to delete only specified recipients. |
No output schema declared.
No examples provided.
delete_token Delete Token ~49
Permanently delete a token by its ID. This action cannot be undone and will immediately invalidate the token for all future requests.
| Name | Type | Req | Description |
|---|---|---|---|
| token_id | string | yes | The unique identifier of the token to delete. |
No output schema declared.
No examples provided.
delete_unsubscribed_recipients Delete Unsubscribed Recipients ~72
Remove recipients from the unsubscribes suppression list. Set the all parameter to true to clear all unsubscribed recipients at once.
| Name | Type | Req | Description |
|---|---|---|---|
| all | boolean | – | When set to true, removes all recipients from the unsubscribes suppression list. Omit or set to false to perform targeted removals. |
No output schema declared.
No examples provided.
delete_user Delete User ~57
Permanently delete a user account and all associated data from the system. This action cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| user_id | string | yes | The unique identifier of the user to delete. This must be a valid user ID that exists in the system. |
No output schema declared.
No examples provided.
delete_webhook Delete Webhook ~52
Permanently delete a webhook by its ID. This action cannot be undone and will stop all event notifications to the webhook's configured endpoint.
| Name | Type | Req | Description |
|---|---|---|---|
| webhook_id | string | yes | The unique identifier of the webhook to delete. |
No output schema declared.
No examples provided.
get_activity Get Activity ~36
Retrieve detailed information about a specific activity by its unique identifier.
| Name | Type | Req | Description |
|---|---|---|---|
| activity_id | string | yes | The unique identifier of the activity to retrieve. |
No output schema declared.
No examples provided.
get_activity_data_by_date_range Get Activity Data by Date Range ~139
Retrieves activity data for a specified date range. Returns analytics events that occurred between the provided start and end timestamps.
| Name | Type | Req | Description |
|---|---|---|---|
| date_from | string | yes | Start of the date range as a Unix timestamp (seconds since epoch). Must be earlier than or equal to date_to. |
| date_to | string | yes | End of the date range as a Unix timestamp (seconds since epoch). Must be later than or equal to date_from. |
| events | array | yes | List of event types to include in the results. Specify which activity events to retrieve (e.g., user_login, page_view, transaction). Order may affect result grouping or filtering behavior. |
No output schema declared.
No examples provided.
get_bulk_email_status Get Bulk Email Status ~66
Retrieve the current status and details of a bulk email campaign. Use this to check delivery progress, completion state, and any associated metrics for a specific bulk email operation.
| Name | Type | Req | Description |
|---|---|---|---|
| bulk_email_id | string | yes | The unique identifier of the bulk email campaign whose status you want to retrieve. |
No output schema declared.
No examples provided.
get_domain Get Domain ~46
Retrieve detailed information about a specific domain by its ID. Returns the domain's configuration, status, and metadata.
| Name | Type | Req | Description |
|---|---|---|---|
| domain_id | string | yes | The unique identifier of the domain to retrieve. |
No output schema declared.
No examples provided.
get_domain_verification_status Get Domain Verification Status ~54
Retrieve the current verification status of a domain, including whether it has been successfully verified and any relevant verification details.
| Name | Type | Req | Description |
|---|---|---|---|
| domain_id | string | yes | The unique identifier of the domain whose verification status you want to check. |
No output schema declared.
No examples provided.
get_email_verification_list Get Email Verification List ~59
Retrieve a single email verification list by its unique identifier. Use this to fetch details about a specific email verification list for review or further processing.
| Name | Type | Req | Description |
|---|---|---|---|
| email_verification_id | string | yes | The unique identifier of the email verification list to retrieve. |
No output schema declared.
No examples provided.
get_inbound_route Get Inbound Route ~60
Retrieve the configuration and details of a specific inbound route by its ID. Use this to view routing rules, destination settings, and other properties of an individual inbound route.
| Name | Type | Req | Description |
|---|---|---|---|
| inbound_id | string | yes | The unique identifier of the inbound route to retrieve. |
No output schema declared.
No examples provided.
get_message Get Message ~48
Retrieve detailed information for a specific message by its ID. Returns the complete message data including content, metadata, and timestamps.
| Name | Type | Req | Description |
|---|---|---|---|
| message_id | string | yes | The unique identifier of the message to retrieve. |
No output schema declared.
No examples provided.
get_opens_by_reading_environment Get Opens by Reading Environment ~106
Retrieves analytics data on content opens segmented by reading environment (e.g., web, mobile, app). Results are filtered by the specified date range.
| Name | Type | Req | Description |
|---|---|---|---|
| date_from | string | yes | Start of the date 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 date 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.
get_recipient Get Recipient ~37
Retrieve detailed information for a specific recipient by their unique identifier.
| Name | Type | Req | Description |
|---|---|---|---|
| recipient_id | string | yes | The unique identifier of the recipient to retrieve. |
No output schema declared.
No examples provided.
get_scheduled_message Get Scheduled Message ~49
Retrieve the details of a single scheduled message by its ID, including its content, schedule, and delivery status.
| Name | Type | Req | Description |
|---|---|---|---|
| message_id | string | yes | The unique identifier of the scheduled message to retrieve. |
No output schema declared.
No examples provided.
get_sender_identity Get Sender Identity ~51
Retrieve detailed information about a specific sender identity by its ID. Use this to view configuration and settings for an individual sender identity.
| Name | Type | Req | Description |
|---|---|---|---|
| identity_id | string | yes | The unique identifier of the sender identity to retrieve. |
No output schema declared.
No examples provided.
get_sender_identity_by_email Get Sender Identity by Email ~59
Retrieve a single sender identity by its email address. Use this to look up configuration and details for a specific sender.
| Name | Type | Req | Description |
|---|---|---|---|
| clientemail.com | string | yes | The email address of the sender identity to retrieve. Must be a valid email format. |
No output schema declared.
No examples provided.
get_sms_inbound_route Get SMS Inbound Route ~47
Retrieve the configuration and details of a specific SMS inbound route by its unique identifier.
| Name | Type | Req | Description |
|---|---|---|---|
| sms_inbound_id | string | yes | The unique identifier of the SMS inbound route to retrieve. |
No output schema declared.
No examples provided.
get_sms_message Get SMS Message ~55
Retrieve a specific SMS message by its unique identifier. Returns the full message details including content, sender, recipient, timestamp, and delivery status.
| Name | Type | Req | Description |
|---|---|---|---|
| sms_message_id | string | yes | The unique identifier of the SMS message to retrieve. |
No output schema declared.
No examples provided.
get_sms_message_activity Get SMS Message Activity ~60
Retrieve the activity history and delivery status for a specific SMS message. This includes details about message processing, delivery attempts, and any related events.
| Name | Type | Req | Description |
|---|---|---|---|
| sms_message_id | string | yes | The unique identifier of the SMS message whose activity you want to retrieve. |
No output schema declared.
No examples provided.
get_sms_phone_number Get SMS Phone Number ~50
Retrieve details for a specific SMS phone number by its ID. Returns the phone number configuration and associated metadata.
| Name | Type | Req | Description |
|---|---|---|---|
| sms_number_id | string | yes | The unique identifier of the SMS phone number to retrieve. |
No output schema declared.
No examples provided.
get_sms_recipient Get SMS Recipient ~42
Retrieve detailed information about a specific SMS recipient by their unique identifier.
| Name | Type | Req | Description |
|---|---|---|---|
| sms_recipient_id | string | yes | The unique identifier of the SMS recipient to retrieve. |
No output schema declared.
No examples provided.
get_sms_webhook Get SMS Webhook ~59
Retrieve the configuration and details of a specific SMS webhook by its ID. Use this to inspect webhook settings, URL, event subscriptions, and other metadata.
| Name | Type | Req | Description |
|---|---|---|---|
| sms_webhook_id | string | yes | The unique identifier of the SMS webhook to retrieve. |
No output schema declared.
No examples provided.
get_smtp_user Get SMTP User ~76
Retrieve detailed information about a specific SMTP user within a domain. Use this to fetch configuration, credentials, and status for a single SMTP user account.
| Name | Type | Req | Description |
|---|---|---|---|
| domain_id | string | yes | The unique identifier of the domain that contains the SMTP user. |
| smtp_user_id | string | yes | The unique identifier of the SMTP user to retrieve. |
No output schema declared.
No examples provided.
get_user Get User ~41
Retrieve a single user by their unique identifier. Returns the user's profile information and details.
| Name | Type | Req | Description |
|---|---|---|---|
| user_id | string | yes | The unique identifier of the user to retrieve. |
No output schema declared.
No examples provided.
get_webhook Get Webhook ~49
Retrieve the details of a specific webhook by its ID. Returns the webhook configuration including its URL, events, and status.
| Name | Type | Req | Description |
|---|---|---|---|
| webhook_id | string | yes | The unique identifier of the webhook to retrieve. |
No output schema declared.
No examples provided.
list_activities_for_domain List Activities for Domain ~118
Retrieve a list of activities for a specific domain within a given time range. Results are filtered by start and end dates in UTC.
| Name | Type | Req | Description |
|---|---|---|---|
| date_from | string | yes | The start of the activity time range as a Unix timestamp in UTC. Activities on or after this date will be included. |
| date_to | string | yes | The end of the activity time range as a Unix timestamp in UTC. Activities on or before this date will be included. |
| domain_id | string | yes | The unique identifier of the domain for which to retrieve activities. |
No output schema declared.
No examples provided.
list_blocklist_recipients List Blocklist Recipients ~36
Retrieve all recipients currently on the blocklist suppression list. This list contains email addresses that have been suppressed from receiving communications.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_dns_records List DNS Records ~55
Retrieve all DNS records configured for a specific domain. Returns a collection of DNS records including their types, values, and configuration details.
| Name | Type | Req | Description |
|---|---|---|---|
| domain_id | string | yes | The unique identifier of the domain for which to retrieve DNS records. |
No output schema declared.
No examples provided.
list_domains List Domains ~34
Retrieve a complete list of all domains available in the system. Use this operation to discover and enumerate domains for management or reference purposes.
Input schema present but exposes no named parameters.
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 PyPI package (mcparmory-mailersend).
Is the com.mcparmory/mailersend MCP server safe to use?
com.mcparmory/mailersend scores 62 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. 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.