com.mcparmory/resend
OCI · GHCR.IO/MCPARMORY/RESEND:1.0.2 · 2 COMPONENTS · SCANNED SEP 20
Send, track, and manage transactional emails at scale
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 Usability83
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 5936 tokens (~94/item across 63 items; 63 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 Safety93
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 10 of 14 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 63 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/resend MCP server?
com.mcparmory/resend runs locally as a container image, launched with docker run --rm -i ghcr.io/mcparmory/resend: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/resend:1.0.2
claude mcp add com-mcparmory-resend -- docker run --rm -i ghcr.io/mcparmory/resend:1.0.2
{
"mcpServers": {
"com-mcparmory-resend": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/resend:1.0.2"
]
}
}
} {
"servers": {
"com-mcparmory-resend": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/resend:1.0.2"
]
}
}
} codex mcp add com-mcparmory-resend -- docker run --rm -i ghcr.io/mcparmory/resend:1.0.2
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-mcparmory-resend": {
"type": "local",
"command": [
"docker",
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/resend:1.0.2"
],
"enabled": true
}
}
} mcp_servers:
com-mcparmory-resend:
command: "docker"
args: ["run", "--rm", "-i", "ghcr.io/mcparmory/resend:1.0.2"] {
"McpServers": {
"com-mcparmory-resend": {
"Transport": "stdio",
"Command": "docker",
"Arguments": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/resend:1.0.2"
]
}
}
} {
"mcpServers": {
"com-mcparmory-resend": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/resend: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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 −3
- Stability: pass → 0.80 functional
- 18 Sept 26 0
- Stability: 0.97 → pass security
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 −2
- Stability: pass → 0.83 functional
- 12 Sept 26 0
- Stability: 0.97 → pass security
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 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/resend: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 →
publish_template Publish Template ~62
Publish a template to make it available for use. Once published, the template can be accessed and utilized by users or systems.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier or alias of the template to publish. Can be either the template's ID or a configured alias. |
No output schema declared.
No examples provided.
remove_contact_from_segment Remove Contact From Segment ~81
Remove a contact from a segment, effectively unsubscribing or disassociating them from that segment's audience.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_id | string | yes | The unique identifier for the contact, provided as either the Contact ID or the contact's email address. |
| segment_id | string | yes | The unique identifier for the segment from which the contact should be removed. |
No output schema declared.
No examples provided.
send_broadcast Send Broadcast ~93
Send a broadcast immediately or schedule it to be sent at a specified future time. Use the scheduled_at parameter to defer delivery, or omit it to send right away.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the broadcast to send or schedule. |
| scheduled_at | string | – | Optional ISO 8601 formatted date and time to schedule the broadcast for future delivery. If omitted, the broadcast will be sent immediately. |
No output schema declared.
No examples provided.
send_email Send Email ~459
Send an email to one or more recipients with optional scheduling, attachments, and custom headers. Supports templating and topic-based subscription management for opt-in/opt-out compliance.
| Name | Type | Req | Description |
|---|---|---|---|
| attachments | array | – | Array of file attachments to include with the email. Each attachment should specify the file content and metadata. |
| bcc | – | – | Blind carbon copy recipient email address or array of addresses. Provide as a single string or array of strings for multiple recipients. |
| cc | – | – | Carbon copy recipient email address or array of addresses. Provide as a single string or array of strings for multiple recipients. |
| from | string | yes | Sender email address. Include a friendly name using the format 'Your Name <sender@domain.com>' to display a custom sender name. |
| headers | object | – | Custom HTTP headers to include in the email message. Provide as key-value pairs. |
| html | string | – | The HTML version of the message. |
| reply_to | – | – | Reply-to email address or array of addresses. Provide as a single string or array of strings for multiple addresses. Overrides the sender address for reply routing. |
| scheduled_at | string | – | Schedule the email to be sent at a future date and time. Specify the date in ISO 8601 format (e.g., 2024-12-25T10:30:00Z). If omitted, the email is sent immediately. |
| subject | string | yes | Email subject line. |
| tags | array | – | Array of tags to categorize or label the email for tracking and organization purposes. |
| template | object | – | Email template identifier to use for rendering the email body. If specified, the template content is used instead of a raw body parameter. |
| text | string | – | The plain text version of the message. |
| to | – | yes | Recipient email address or array of addresses. Supports up to 50 recipients; provide as a single string for one recipient or an array of strings for multiple. |
| topic_id | string | – | Topic ID to enforce subscription-based delivery rules. If the recipient is a contact, the email is sent only if they're opted-in to the topic; if opted-out, it's blocked. For non-contacts, delivery f… |
No output schema declared.
No examples provided.
send_emails_batch Send Emails Batch ~80
Send up to 100 emails in a single batch request. This operation allows efficient bulk email delivery by processing multiple email configurations simultaneously.
| Name | Type | Req | Description |
|---|---|---|---|
| body | array | – | Array of email objects to send, with a maximum of 100 items per request. Each item in the array represents a single email configuration with its own recipient, subject, and content details. |
No output schema declared.
No examples provided.
update_broadcast Update Broadcast ~188
Update an existing broadcast's configuration including name, recipient segment, sender details, subject line, and topic association.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | The email address that will appear as the sender of the broadcast. |
| id | string | yes | The unique identifier of the broadcast to update. |
| name | string | – | The display name for the broadcast. |
| preview_text | string | – | The preview text shown in email clients before the recipient opens the message. |
| reply_to | array | – | One or more email addresses where replies to this broadcast should be directed. Specify as an array of email addresses. |
| segment_id | string | – | The unique identifier of the audience segment that will receive this broadcast. |
| subject | string | – | The subject line displayed in recipients' email clients. |
| topic_id | string | – | The unique identifier of the topic this broadcast is associated with for organizational and filtering purposes. |
No output schema declared.
No examples provided.
update_contact Update Contact ~165
Update contact details by ID or email address. Modify any combination of email, name, subscription status, or custom properties for an existing contact.
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | The contact's email address in standard email format (e.g., user@example.com). | |
| first_name | string | – | The contact's first name. |
| id | string | yes | The unique identifier for the contact, either as a Contact ID or email address. |
| last_name | string | – | The contact's last name. |
| properties | object | – | A map of custom property keys and their values to update or add to the contact's profile. |
| unsubscribed | boolean | – | Global subscription status for the contact. Set to true to unsubscribe the contact from all Broadcasts; false to maintain or restore subscription. |
No output schema declared.
No examples provided.
update_contact_property Update Contact Property ~89
Update the fallback value for an existing contact property. The fallback value is used as the default when the property is not set for a specific contact.
| Name | Type | Req | Description |
|---|---|---|---|
| fallback_value | string | – | The default value to use when this property is not set for a contact. Must be compatible with the property's data type (string or number). |
| id | string | yes | The unique identifier of the contact property to update. |
No output schema declared.
No examples provided.
update_domain Update Domain ~167
Update email tracking and TLS security settings for an existing domain. Modify open rate tracking, click tracking, and TLS enforcement preferences.
| Name | Type | Req | Description |
|---|---|---|---|
| click_tracking | boolean | – | Enable or disable tracking of link clicks within HTML email bodies. When enabled, the system monitors which links recipients click in emails from this domain. |
| domain_id | string | yes | The unique identifier of the domain to update. |
| open_tracking | boolean | – | Enable or disable tracking of email open rates. When enabled, the system monitors whether recipients open emails sent from this domain. |
| tls | string | – | Set the TLS security mode for outgoing emails: use 'enforced' to require TLS encryption for all connections, or 'opportunistic' to use TLS when available but allow unencrypted fallback. Defaults to '… |
No output schema declared.
No examples provided.
update_template Update Template ~177
Update an existing email template by modifying its name, alias, sender information, subject, reply-to addresses, or variables.
| Name | Type | Req | Description |
|---|---|---|---|
| alias | string | – | A unique alias or slug for referencing the template programmatically. |
| from | string | – | The sender's email address; optionally include a friendly name using the format 'Display Name <email@domain.com>'. |
| id | string | yes | The unique identifier or alias of the template to update. |
| name | string | – | The display name for the template. |
| reply_to | array | – | One or more email addresses to set as reply-to destinations for responses to emails sent with this template. |
| subject | string | – | The subject line for emails sent using this template. |
| variables | array | – | Template variables that can be dynamically substituted when sending emails; specify as an array of variable definitions. |
No output schema declared.
No examples provided.
update_topic Update Topic ~123
Update an existing topic's metadata including its name, description, and visibility settings. Provide the topic ID and specify which fields to modify.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | A detailed description of the topic's purpose or content. Must not exceed 200 characters. |
| id | string | yes | The unique identifier of the topic to update. |
| name | string | – | The new name for the topic. Must not exceed 50 characters. |
| visibility | string | – | Controls who can access this topic. Choose either 'public' for unrestricted access or 'private' for restricted access. |
No output schema declared.
No examples provided.
update_webhook Update Webhook ~159
Update the configuration of an existing webhook, including its endpoint URL, subscribed event types, and operational status.
| Name | Type | Req | Description |
|---|---|---|---|
| endpoint | string | – | The HTTPS URL where webhook events will be delivered. This endpoint must be publicly accessible and capable of receiving POST requests. |
| events | array | – | A list of event types this webhook should subscribe to. At least one event type is required. Events are specified as dot-separated strings (e.g., 'email.sent', 'email.delivered'). |
| status | string | – | The operational state of the webhook. Set to 'enabled' to activate event delivery or 'disabled' to pause it without removing the configuration. |
| webhook_id | string | yes | The unique identifier of the webhook to update, formatted as a UUID. |
No output schema declared.
No examples provided.
verify_domain Verify Domain ~41
Verify ownership or configuration of an existing domain by triggering validation checks against the specified domain.
| Name | Type | Req | Description |
|---|---|---|---|
| domain_id | string | yes | The unique identifier of the domain to verify. |
No output schema declared.
No examples provided.
What is the com.mcparmory/resend MCP server?
com.mcparmory/resend is an MCP server listed in the public MCP registry as com.mcparmory/resend. Send, track, and manage transactional emails at scale. This page covers its container image (ghcr.io/mcparmory/resend:1.0.2).
Is the com.mcparmory/resend MCP server safe to use?
com.mcparmory/resend scores 51 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/resend MCP server expose?
com.mcparmory/resend exposes 63 tools: list_emails, send_email, get_email, cancel_email, send_emails_batch, and 58 more. Their descriptions and schemas cost roughly 5,936 tokens of context every time the server is loaded.
Is the com.mcparmory/resend MCP server still maintained?
com.mcparmory/resend 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.