com.mcparmory/resend
OCI · GHCR.IO/MCPARMORY/RESEND:1.0.2 · 2 COMPONENTS
Send, track, and manage transactional emails at scale
Available components
Last scanned (11 hours ago)
Scores higher than 89% of OCI servers
Category Marketing and SEO
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
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.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 176 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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.
Checks we ran (12)
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (4)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Malware scan in Supply Chain Security (scores 0 for this)No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
- Known CVEs in Supply Chain Security (scores 0 for this)Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
- Install scripts in Supply Chain Security (scores 0 for this)Install-script risk not yet assessed.
- Dependency health in Supply Chain Security (scores 0 for this)Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 1 Nov 26 0
- Stability: 0.97 → pass security
- 31 Oct 26 0
- Stability: pass → 0.97 functional
- 24 Oct 26 0
- Stability: 0.97 → pass security
- 23 Oct 26 0
- Stability: pass → 0.97 functional
- 17 Oct 26 0
- Stability: 0.97 → pass security
- 16 Oct 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.
- 14 Oct 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.
- 12 Oct 26 −2
- Stability: pass → 0.83 functional
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 5 Nov 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 →
add_contact_to_segment Add Contact to Segment ~74
Add a contact to a segment, enabling you to organize and group contacts for targeted campaigns or management purposes.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_id | string | yes | The unique identifier or email address of the contact to add to the segment. |
| segment_id | string | yes | The unique identifier of the segment to which the contact will be added. |
No output schema declared.
No examples provided.
cancel_email Cancel Email ~41
Cancel the scheduled delivery of an email. This prevents a scheduled email from being sent.
| Name | Type | Req | Description |
|---|---|---|---|
| email_id | string | yes | The unique identifier of the email to cancel. |
No output schema declared.
No examples provided.
create_api_key Create API Key ~138
Create a new API key for authenticating requests to the Resend API. The key can be configured with either full access to all resources or restricted to sending emails only.
| Name | Type | Req | Description |
|---|---|---|---|
| domain_id | string | – | When using sending_access permission, optionally restrict the API key to send emails only from a specific domain by providing its domain ID. |
| name | string | yes | A descriptive name for the API key to help identify its purpose and usage. |
| permission | string | – | The access level for the API key: full_access grants permissions to create, delete, get, and update any resource, while sending_access restricts the key to only sending emails. |
No output schema declared.
No examples provided.
create_broadcast Create Broadcast ~317
Create an email broadcast to be sent to a specific audience segment. The broadcast can be sent immediately or scheduled for a future time, or saved as a draft for later editing.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | yes | The email address that will appear as the sender of this broadcast. |
| html | string | – | The HTML version of the message. |
| name | string | – | A human-readable name to identify this broadcast for internal reference. |
| preview_text | string | – | A short preview or snippet of the email content that appears in email clients before the full message is opened. |
| reply_to | array | – | One or more email addresses where recipient replies should be directed. Provide as an array of email addresses. |
| scheduled_at | string | – | The date and time when the broadcast should be sent, specified in ISO 8601 format. This can only be used when send is set to true. |
| segment_id | string | yes | The unique identifier of the audience segment that will receive this broadcast. This parameter determines who the email will be sent to. |
| send | boolean | – | Set to true to send the broadcast immediately, or false to save it as a draft. If true, you can optionally use scheduled_at to send at a future time. |
| subject | string | yes | The subject line displayed to recipients when they receive the email. |
| text | string | – | The plain text version of the message. |
| topic_id | string | – | The unique identifier of a topic to scope this broadcast to, allowing you to organize broadcasts by topic. |
No output schema declared.
No examples provided.
create_contact Create Contact ~223
Create a new contact in the system with email as the required identifier. Optionally include personal details, custom properties, segment assignments, and topic subscriptions.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | Email address uniquely identifying the contact (e.g., steve.wozniak@gmail.com). Required to create the contact. | |
| first_name | string | – | First name of the contact for personalization and identification purposes. |
| last_name | string | – | Last name of the contact for personalization and identification purposes. |
| properties | object | – | Custom key-value pairs to store additional contact attributes beyond standard fields. Values can be strings, numbers, or other JSON-compatible types. |
| segments | array | – | List of segment IDs to automatically add this contact to upon creation. Segments organize contacts into groups for targeted campaigns. |
| topics | array | – | List of topic IDs representing the contact's subscription preferences. Topics control which types of communications the contact receives. |
| unsubscribed | boolean | – | Global subscription status for the contact. When set to true, the contact is unsubscribed from all broadcasts and communications. |
No output schema declared.
No examples provided.
create_contact_property Create Contact Property ~141
Create a new custom property for contacts. This property can be used to store additional data on contact records, with an optional default value applied when the property is not explicitly set.
| Name | Type | Req | Description |
|---|---|---|---|
| fallback_value | string | – | An optional default value returned when the property is not set on a contact. The value must match the specified property type (string or number). |
| key | string | yes | A unique identifier for the property using only alphanumeric characters and underscores, up to 50 characters in length. |
| type | string | yes | The data type for this property, either string or number, which determines the format of values stored and the type required for the fallback value. |
No output schema declared.
No examples provided.
create_domain Create Domain ~269
Create a new domain for sending emails. Configure the domain with optional settings for region, tracking, TLS security, and custom return path.
| Name | Type | Req | Description |
|---|---|---|---|
| click_tracking | boolean | – | Enable click tracking to monitor links clicked within HTML email bodies. Disabled by default. |
| custom_return_path | string | – | A custom subdomain for the Return-Path address used in bounce handling. Defaults to 'send' (resulting in send.yourdomain.tld). Use this for advanced routing scenarios. |
| name | string | yes | The domain name to create (e.g., mail.example.com). This will be used as your sending domain. |
| open_tracking | boolean | – | Enable open rate tracking by injecting a tracking pixel into each email. Disabled by default. |
| region | string | – | The AWS region where emails will be sent from. Defaults to us-east-1 if not specified. Choose from: us-east-1 (N. Virginia), eu-west-1 (Ireland), sa-east-1 (São Paulo), or ap-northeast-1 (Tokyo). |
| tls | string | – | TLS encryption mode for outbound emails. 'Opportunistic' attempts a secure connection but falls back to unencrypted if unavailable. 'Enforced' requires TLS or the email will not be sent. Defaults to… |
No output schema declared.
No examples provided.
create_segment Create Segment ~83
Create a new segment with a name and optional filter conditions to organize and target specific data subsets.
| Name | Type | Req | Description |
|---|---|---|---|
| filter | object | – | Optional filter conditions that define which records belong to this segment. Specify filter criteria as a structured object to narrow the segment's scope. |
| name | string | yes | The display name for the segment. Used to identify and reference the segment in the system. |
No output schema declared.
No examples provided.
create_template Create Template ~232
Create a new email template with HTML content and optional configuration for sender, subject, and reply-to addresses. Templates can be referenced by name or alias for sending emails.
| Name | Type | Req | Description |
|---|---|---|---|
| alias | string | – | An alternative identifier for the template. Useful for programmatic references or shorter naming conventions. |
| from | string | – | The sender's email address, optionally formatted with a friendly name using the format 'Display Name <email@domain.com>'. |
| html | string | yes | The HTML content of the template. This is the main body rendered in email clients that support HTML. Supports variable substitution using defined variables. |
| name | string | yes | The display name for this template. Used to identify and reference the template when sending emails. |
| reply_to | array | – | One or more email addresses where recipients can reply. Specify as an array of email addresses. |
| subject | string | – | The subject line for emails sent using this template. Supports variable substitution if variables are defined. |
| variables | array | – | Template variables that can be dynamically substituted in the subject, HTML content, and sender field. Specify as an array of variable definitions. |
No output schema declared.
No examples provided.
create_topic Create Topic ~166
Create a new topic for managing contact subscriptions. Topics define subscription preferences that cannot be modified after creation.
| Name | Type | Req | Description |
|---|---|---|---|
| default_subscription | string | yes | The default subscription behavior for new contacts: 'opt_in' requires explicit subscription, 'opt_out' subscribes by default. This setting is permanent and cannot be changed after topic creation. |
| description | string | – | Optional description of the topic's purpose, up to 200 characters. Helps contacts understand what the topic covers. |
| name | string | yes | The topic name, up to 50 characters. Used to identify the topic in subscription management interfaces. |
| visibility | string | – | Controls topic visibility: 'public' topics appear on the unsubscribe page for all contacts, 'private' topics only appear for already opted-in contacts. Defaults to 'private'. |
No output schema declared.
No examples provided.
create_webhook Create Webhook ~120
Create a new webhook subscription to receive HTTP POST notifications for specified email events. The webhook will be triggered whenever any of the subscribed events occur.
| Name | Type | Req | Description |
|---|---|---|---|
| endpoint | string | yes | The HTTPS URL endpoint where webhook event notifications will be delivered. Must be a valid, publicly accessible URL that can receive POST requests. |
| events | array | yes | A list of one or more event types to subscribe to. Each event type is a string identifier (e.g., 'email.sent', 'email.delivered'). At least one event type is required. Order does not matter. |
No output schema declared.
No examples provided.
delete_api_key Delete API Key ~54
Permanently remove an API key by its ID. Once deleted, the key can no longer be used for authentication and cannot be recovered.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key_id | string | yes | The unique identifier of the API key to delete. |
No output schema declared.
No examples provided.
delete_broadcast Delete Broadcast ~62
Permanently remove a broadcast that is currently in draft status. Only draft broadcasts can be deleted; published or scheduled broadcasts cannot be removed through this operation.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the broadcast to delete. Must reference a broadcast in draft status. |
No output schema declared.
No examples provided.
delete_contact Delete Contact ~54
Permanently remove a contact from the system by specifying either its unique ID or email address.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier for the contact, provided as either the contact ID or the email address associated with the contact. |
No output schema declared.
No examples provided.
delete_contact_property Delete Contact Property ~44
Permanently remove a contact property from the system by its ID. This action cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the contact property to delete. |
No output schema declared.
No examples provided.
delete_domain Delete Domain ~40
Permanently remove a domain from the system. This action cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| domain_id | string | yes | The unique identifier of the domain to be deleted. |
No output schema declared.
No examples provided.
delete_segment Delete Segment ~38
Permanently remove a segment by its ID. This action cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the segment to delete. |
No output schema declared.
No examples provided.
delete_template Delete Template ~54
Permanently remove a template by its ID or alias. This action cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier or alias of the template to delete. Can be either the template's ID or a configured alias. |
No output schema declared.
No examples provided.
delete_topic Delete Topic ~38
Permanently remove a topic by its ID. This action cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the topic to delete. |
No output schema declared.
No examples provided.
delete_webhook Delete Webhook ~46
Permanently remove a webhook by its unique identifier. This action cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| webhook_id | string | yes | The unique identifier of the webhook to delete, formatted as a UUID. |
No output schema declared.
No examples provided.
duplicate_template Duplicate Template ~56
Creates a copy of an existing template, allowing you to reuse template configurations with a new instance.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier or alias of the template to duplicate. Can be either the template's ID or a configured alias. |
No output schema declared.
No examples provided.
get_broadcast Get Broadcast ~36
Retrieve detailed information about a specific broadcast by its unique identifier.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the broadcast to retrieve. |
No output schema declared.
No examples provided.
get_contact Get Contact ~61
Retrieve a single contact by its unique identifier or email address. Use this operation to fetch detailed information about a specific contact.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier for the contact or the contact's email address. Either format is accepted to retrieve the contact record. |
No output schema declared.
No examples provided.
get_contact_property Get Contact Property ~47
Retrieve a single contact property by its unique identifier. Use this to fetch detailed information about a specific contact property.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the contact property to retrieve. |
No output schema declared.
No examples provided.
get_domain Get Domain ~36
Retrieve detailed information about a specific domain by its unique identifier.
| Name | Type | Req | Description |
|---|---|---|---|
| domain_id | string | yes | The unique identifier of the domain to retrieve. |
No output schema declared.
No examples provided.
get_email Get Email ~47
Retrieve a single email message by its unique identifier. Returns the complete email record including headers, body, and metadata.
| Name | Type | Req | Description |
|---|---|---|---|
| email_id | string | yes | The unique identifier of the email to retrieve. |
No output schema declared.
No examples provided.
get_email_attachment Get Email Attachment ~72
Retrieve a specific attachment from a sent email by providing both the email ID and attachment ID.
| Name | Type | Req | Description |
|---|---|---|---|
| attachment_id | string | yes | The unique identifier of the attachment to retrieve. Must be a valid UUID. |
| email_id | string | yes | The unique identifier of the email containing the attachment. Must be a valid UUID. |
No output schema declared.
No examples provided.
get_log Get Log ~49
Retrieve a single log entry by its unique identifier. Returns the complete log record matching the provided ID.
| Name | Type | Req | Description |
|---|---|---|---|
| log_id | string | yes | The unique identifier of the log to retrieve, formatted as a UUID. |
No output schema declared.
No examples provided.
get_received_email Get Received Email ~54
Retrieve a single received email by its unique identifier. Use this to fetch the full details of a specific email in your inbox.
| Name | Type | Req | Description |
|---|---|---|---|
| email_id | string | yes | The unique identifier of the received email, formatted as a UUID. |
No output schema declared.
No examples provided.
get_received_email_attachment Get Received Email Attachment ~75
Retrieve a specific attachment from a received email by providing both the email ID and attachment ID. Returns the attachment file and metadata.
| Name | Type | Req | Description |
|---|---|---|---|
| attachment_id | string | yes | The unique identifier (UUID) of the attachment to retrieve. |
| email_id | string | yes | The unique identifier (UUID) of the received email containing the attachment. |
No output schema declared.
No examples provided.
get_segment Get Segment ~42
Retrieve a single segment by its unique identifier. Returns the complete segment details including configuration and metadata.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the segment to retrieve. |
No output schema declared.
No examples provided.
get_template Get Template ~71
Retrieve a single template by its ID or alias. Use this operation to fetch the full details of a specific template for viewing or further processing.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier or alias of the template to retrieve. Can be either the template's ID or a human-readable alias if supported by the API. |
No output schema declared.
No examples provided.
get_topic Get Topic ~42
Retrieve a single topic by its unique identifier. Returns the complete topic details including metadata and content.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the topic to retrieve. |
No output schema declared.
No examples provided.
get_webhook Get Webhook ~54
Retrieve the details of a specific webhook by its unique identifier. Use this to inspect webhook configuration, status, and settings.
| Name | Type | Req | Description |
|---|---|---|---|
| webhook_id | string | yes | The unique identifier of the webhook to retrieve, formatted as a UUID. |
No output schema declared.
No examples provided.
list_api_keys List API Keys ~63
Retrieve a paginated list of API keys for the authenticated user or organization. Use the limit parameter to control the number of results returned.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of API keys to return in the response. Must be between 1 and 100 items. |
No output schema declared.
No examples provided.
list_attachments_for_email List Attachments for Email ~78
Retrieve all attachments associated with a specific sent email. Use this to access files that were included when the email was sent.
| Name | Type | Req | Description |
|---|---|---|---|
| email_id | string | yes | The unique identifier of the email, formatted as a UUID. |
| limit | integer | – | The maximum number of attachments to return in the response. Useful for pagination or limiting results. |
No output schema declared.
No examples provided.
list_broadcasts List Broadcasts ~60
Retrieve a paginated list of broadcasts. Use the limit parameter to control how many broadcasts are returned in a single request.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of broadcasts to return in the response. Must be between 1 and 100 items. |
No output schema declared.
No examples provided.
list_contact_properties List Contact Properties ~61
Retrieve a paginated list of available contact properties. Use the limit parameter to control the number of properties returned in a single request.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of contact properties to return per request. Must be between 1 and 100 items. |
No output schema declared.
No examples provided.
list_contact_segments List Contact Segments ~83
Retrieve all segments that a contact belongs to. Use the contact's ID or email address to fetch their segment memberships.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_id | string | yes | The unique identifier for the contact. Accepts either the contact's ID or email address. |
| limit | integer | – | Maximum number of segments to return in the response. Must be between 1 and 100 items. |
No output schema declared.
No examples provided.
list_contact_topics List Contact Topics ~90
Retrieve a list of topics associated with a specific contact. Use the contact ID or email address to fetch their related topics with optional pagination.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_id | string | yes | The unique identifier for the contact, which can be either the contact ID or the contact's email address. |
| limit | integer | – | Maximum number of topics to return in the response. Must be between 1 and 100 items. |
No output schema declared.
No examples provided.
list_contacts List Contacts ~82
Retrieve a list of contacts, optionally filtered by segment and limited to a specific number of results.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of contacts to return in the response. Must be between 1 and 100 items. |
| segment_id | string | – | Filter the returned contacts to only those belonging to a specific segment. Omit to retrieve contacts from all segments. |
No output schema declared.
No examples provided.
list_domains List Domains ~58
Retrieve a paginated list of domains. Use the limit parameter to control the number of results returned in a single request.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of domains to return in this request. Must be between 1 and 100 items. |
No output schema declared.
No examples provided.
list_email_attachments List Email Attachments ~83
Retrieve all attachments associated with a received email. Use this to access files that were included with an incoming message.
| Name | Type | Req | Description |
|---|---|---|---|
| email_id | string | yes | The unique identifier of the received email, formatted as a UUID. |
| limit | integer | – | The maximum number of attachments to return in the response. Useful for pagination or limiting results when dealing with emails containing many files. |
No output schema declared.
No examples provided.
list_emails List Emails ~59
Retrieve a paginated list of emails. Use the limit parameter to control how many emails are returned in a single request.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of emails to return in this request. Must be between 1 and 100 items. |
No output schema declared.
No examples provided.
list_emails_receiving List Receiving Emails ~69
Retrieve a list of received emails from your inbox. Use the limit parameter to control how many emails are returned in the response.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of received emails to return in a single response. Limits the size of the result set to improve performance and reduce payload size. |
No output schema declared.
No examples provided.
list_logs List Logs ~63
Retrieve a paginated list of logs from the system. Use the limit parameter to control how many log entries are returned in a single request.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of log entries to return in the response. Must be between 1 and 100 items. |
No output schema declared.
No examples provided.
list_segments List Segments ~57
Retrieve a paginated list of segments. Use the limit parameter to control the number of results returned in a single request.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of segments to return per request. Must be between 1 and 100 items. |
No output schema declared.
No examples provided.
list_templates List Templates ~55
Retrieve a paginated list of available templates. Use the limit parameter to control the number of results returned.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of templates to return in the response. Must be between 1 and 100 items. |
No output schema declared.
No examples provided.
list_topics List Topics ~55
Retrieve a paginated list of available topics. Use the limit parameter to control the number of results returned.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of topics to return in the response. Must be between 1 and 100 items. |
No output schema declared.
No examples provided.
list_webhooks List Webhooks ~60
Retrieve a paginated list of webhooks configured for this API. Use the limit parameter to control the maximum number of results returned.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of webhooks to return in the response. Useful for pagination and controlling response size. |
No output schema declared.
No examples provided.
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
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 53 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 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the com.mcparmory/resend MCP server?
VerifyMCP ran 12 checks on com.mcparmory/resend, covering Source repository, Provenance, License, Maintenance and 8 more. 4 items could not be completed, a gap on our side rather than a finding about com.mcparmory/resend: Malware scan, Known CVEs, Install scripts and Dependency health. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a container image, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.