com.mcparmory/postmark
OCI · GHCR.IO/MCPARMORY/POSTMARK:1.0.2 · 2 COMPONENTS · SCANNED SEP 20
Send, track, and manage transactional and bulk email delivery
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 Usability75
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 4966 tokens (~127/item across 39 items; 39 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 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 Safety79
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 1 of 6 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 39 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/postmark MCP server?
com.mcparmory/postmark runs locally as a container image, launched with docker run --rm -i ghcr.io/mcparmory/postmark: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/postmark:1.0.2
claude mcp add com-mcparmory-postmark -- docker run --rm -i ghcr.io/mcparmory/postmark:1.0.2
{
"mcpServers": {
"com-mcparmory-postmark": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/postmark:1.0.2"
]
}
}
} {
"servers": {
"com-mcparmory-postmark": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/postmark:1.0.2"
]
}
}
} codex mcp add com-mcparmory-postmark -- docker run --rm -i ghcr.io/mcparmory/postmark:1.0.2
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-mcparmory-postmark": {
"type": "local",
"command": [
"docker",
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/postmark:1.0.2"
],
"enabled": true
}
}
} mcp_servers:
com-mcparmory-postmark:
command: "docker"
args: ["run", "--rm", "-i", "ghcr.io/mcparmory/postmark:1.0.2"] {
"McpServers": {
"com-mcparmory-postmark": {
"Transport": "stdio",
"Command": "docker",
"Arguments": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/postmark:1.0.2"
]
}
}
} {
"mcpServers": {
"com-mcparmory-postmark": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/postmark: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 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.80 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 +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.
- 11 Sept 26 −3
- Stability: pass → 0.80 functional
- 10 Sept 26 +1
- Stability: 0.97 → pass security
- 8 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.
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/postmark: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 →
activate_bounce Activate Bounce ~62
Reactivate a bounce record in Postmark, allowing it to be processed again. This operation marks a previously bounced email address as active.
| Name | Type | Req | Description |
|---|---|---|---|
| bounceid | string | yes | The unique identifier of the bounce record to activate. Must be a valid 64-bit integer. |
No output schema declared.
No examples provided.
bypass_inbound_message_rules Bypass Inbound Message Rules ~63
Allow a blocked inbound message to bypass email filtering rules. Use this to whitelist or recover messages that were incorrectly filtered by the server's inbound rules.
| Name | Type | Req | Description |
|---|---|---|---|
| messageid | string | yes | The unique identifier of the inbound message that should be exempted from rule filtering. |
No output schema declared.
No examples provided.
create_template Create Template ~156
Create a new email template with a subject line and optional alias for easy reference. Templates can be used to standardize email content across your application.
| Name | Type | Req | Description |
|---|---|---|---|
| Alias | string | – | Optional unique identifier for this template using alphanumeric characters, dots, hyphens, and underscores. Must start with a letter. Useful for programmatic template references. |
| HtmlBody | string | – | The HTML template definition for this Template. |
| Name | string | yes | Human-readable name for the template displayed in the Postmark dashboard and API responses. |
| Subject | string | yes | Template definition for the email subject line. Supports template variables and dynamic content using Postmark's templating syntax. |
| TextBody | string | – | The Text template definition for this Template. |
No output schema declared.
No examples provided.
delete_template Delete Template ~57
Permanently delete a template by its ID or alias. This action cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| templateIdOrAlias | string | yes | The unique identifier or alias of the template to delete. You can use either the TemplateID or the Alias value. |
No output schema declared.
No examples provided.
get_bounce_by_id Get Bounce by ID ~67
Retrieve detailed information about a specific bounce event by its ID. Use this to inspect bounce details such as type, email address, and timestamp for a particular bounce occurrence.
| Name | Type | Req | Description |
|---|---|---|---|
| bounceid | string | yes | The unique identifier of the bounce record to retrieve. Must be a positive integer. |
No output schema declared.
No examples provided.
get_bounce_dump Get Bounce Dump ~65
Retrieve the detailed dump data for a specific bounce event. This provides comprehensive information about why a message bounced, including diagnostic details and headers.
| Name | Type | Req | Description |
|---|---|---|---|
| bounceid | string | yes | The unique identifier of the bounce event whose dump data you want to retrieve. Must be a positive integer. |
No output schema declared.
No examples provided.
get_delivery_stats Get Delivery Stats ~31
Retrieve delivery statistics for messages sent through your Postmark server. This provides insights into message delivery performance and status.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_inbound_message_details Get Inbound Message Details ~51
Retrieve detailed information about a specific inbound message, including its content, metadata, and delivery status.
| Name | Type | Req | Description |
|---|---|---|---|
| messageid | string | yes | The unique identifier of the inbound message whose details you want to retrieve. |
No output schema declared.
No examples provided.
get_message_opens_by_id Get Message Opens by ID ~122
Retrieve a paginated list of open events for a specific outbound message. Use offset and count parameters to navigate through the results.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | The number of open records to return in this request. Must be between 1 and 500 (defaults to 1). |
| messageid | string | yes | The unique identifier of the outbound message for which to retrieve open statistics. |
| offset | integer | yes | The number of open records to skip before returning results, used for pagination. Must be 0 or greater (defaults to 0). |
No output schema declared.
No examples provided.
get_outbound_bounce_statistics Get Outbound Bounce Statistics ~114
Retrieve bounce statistics for outbound emails, with optional filtering by tag and date range to analyze delivery failures.
| Name | Type | Req | Description |
|---|---|---|---|
| fromdate | string | – | Filter statistics to include data starting from this date (inclusive). Specify in ISO 8601 date format (YYYY-MM-DD). |
| tag | string | – | Filter bounce statistics to a specific tag associated with your emails. |
| todate | string | – | Filter statistics to include data up to this date (inclusive). Specify in ISO 8601 date format (YYYY-MM-DD). |
No output schema declared.
No examples provided.
get_outbound_click_stats Get Outbound Click Stats ~114
Retrieve click count statistics for outbound links, with optional filtering by tag and date range to analyze link performance over time.
| Name | Type | Req | Description |
|---|---|---|---|
| fromdate | string | – | Filter statistics to include only clicks from this date forward (inclusive). Specify as a calendar date in YYYY-MM-DD format. |
| tag | string | – | Filter statistics to only include clicks associated with a specific tag. |
| todate | string | – | Filter statistics to include only clicks up to this date (inclusive). Specify as a calendar date in YYYY-MM-DD format. |
No output schema declared.
No examples provided.
get_outbound_clicks_by_location Get Outbound Clicks by Location ~113
Retrieve click statistics for outbound links aggregated by body location. Use optional filters to narrow results by tag and date range.
| Name | Type | Req | Description |
|---|---|---|---|
| fromdate | string | – | Include statistics starting from this date (inclusive). Specify in ISO 8601 date format (YYYY-MM-DD). |
| tag | string | – | Filter results to include only clicks from messages tagged with this value. |
| todate | string | – | Include statistics up to this date (inclusive). Specify in ISO 8601 date format (YYYY-MM-DD). |
No output schema declared.
No examples provided.
get_outbound_email_opens Get Outbound Email Opens ~116
Retrieve email open statistics for outbound messages, with optional filtering by tag and date range to analyze engagement metrics.
| Name | Type | Req | Description |
|---|---|---|---|
| fromdate | string | – | Filter statistics to include only data from this date forward, specified in ISO 8601 date format (YYYY-MM-DD). |
| tag | string | – | Filter results to only include statistics for messages tagged with this value. |
| todate | string | – | Filter statistics to include only data up to and including this date, specified in ISO 8601 date format (YYYY-MM-DD). |
No output schema declared.
No examples provided.
get_outbound_message_details Get Outbound Message Details ~52
Retrieve detailed information about a specific outbound message, including delivery status, recipient information, and message content.
| Name | Type | Req | Description |
|---|---|---|---|
| messageid | string | yes | The unique identifier of the outbound message whose details you want to retrieve. |
No output schema declared.
No examples provided.
get_outbound_message_dump Get Outbound Message Dump ~61
Retrieve the full dump of an outbound message, including all metadata and content details. This operation requires authentication via a Postmark server token.
| Name | Type | Req | Description |
|---|---|---|---|
| messageid | string | yes | The unique identifier of the outbound message for which to retrieve the complete dump data. |
No output schema declared.
No examples provided.
get_outbound_send_stats Get Outbound Send Stats ~119
Retrieve statistics on sent messages, with optional filtering by tag and date range. Use this to analyze outbound sending activity over time.
| Name | Type | Req | Description |
|---|---|---|---|
| fromdate | string | – | Filter statistics to include only data from this date forward, specified in ISO 8601 date format (YYYY-MM-DD). |
| tag | string | – | Filter results to only include statistics for messages with this specific tag. |
| todate | string | – | Filter statistics to include only data up to and including this date, specified in ISO 8601 date format (YYYY-MM-DD). |
No output schema declared.
No examples provided.
get_outbound_spam_stats Get Outbound Spam Stats ~121
Retrieve spam complaint statistics for outbound messages. Filter results by tag and date range to analyze spam performance metrics.
| Name | Type | Req | Description |
|---|---|---|---|
| fromdate | string | – | Start date for the statistics query in ISO 8601 format (YYYY-MM-DD). Results will include data from this date onward. |
| tag | string | – | Filter statistics by a specific tag to isolate metrics for tagged message groups. |
| todate | string | – | End date for the statistics query in ISO 8601 format (YYYY-MM-DD). Results will include data up to and including this date. |
No output schema declared.
No examples provided.
get_outbound_stats Get Outbound Stats ~131
Retrieve outbound email statistics and performance overview. Optionally filter results by tag and date range to analyze specific sending campaigns or time periods.
| Name | Type | Req | Description |
|---|---|---|---|
| fromdate | string | – | Start date for the statistics range in ISO 8601 format (YYYY-MM-DD). Results will include data from this date onward. |
| tag | string | – | Filter statistics to a specific tag, useful for segmenting results by campaign, sender, or other classification. |
| todate | string | – | End date for the statistics range in ISO 8601 format (YYYY-MM-DD). Results will include data up to and including this date. |
No output schema declared.
No examples provided.
get_outbound_tracked_email_stats Get Outbound Tracked Email Stats ~134
Retrieve counts of tracked outbound emails, with optional filtering by tag and date range. Use this to monitor email delivery metrics for a specific time period or tag.
| Name | Type | Req | Description |
|---|---|---|---|
| fromdate | string | – | Start date for the stats query in ISO 8601 format (YYYY-MM-DD). Only emails sent on or after this date will be included. |
| tag | string | – | Filter results to only include emails associated with this specific tag. |
| todate | string | – | End date for the stats query in ISO 8601 format (YYYY-MM-DD). Only emails sent on or before this date will be included. |
No output schema declared.
No examples provided.
get_server_configuration Get Server Configuration ~34
Retrieve the configuration and settings for the authenticated Postmark server, including delivery settings, bounce handling, and other server-level configurations.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_template Get Template ~81
Retrieve a specific email template by its unique identifier or alias. Use this to fetch template details for rendering, previewing, or managing email communications.
| Name | Type | Req | Description |
|---|---|---|---|
| templateIdOrAlias | string | yes | The unique identifier or alias of the template to retrieve. You can use either the TemplateID (numeric identifier) or the Alias (custom name) to look up the template. |
No output schema declared.
No examples provided.
list_bounces List Bounces ~254
Retrieve a paginated list of email bounces from your Postmark server, with optional filtering by bounce type, email address, date range, and other criteria.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | Number of bounce records to return per request, up to a maximum of 500. |
| emailFilter | string | – | Filter results by a specific email address. |
| fromdate | string | – | Filter results to include only bounces starting from and after this date (format: YYYY-MM-DD). |
| inactive | boolean | – | Filter results to show only emails that were deactivated by Postmark (true), only active emails (false), or both if not specified. |
| messageID | string | – | Filter results by the message ID associated with the bounce. |
| offset | integer | yes | Number of bounce records to skip from the beginning of the result set for pagination. |
| tag | string | – | Filter results by a tag assigned to the message. |
| todate | string | – | Filter results to include only bounces up to and including this date (format: YYYY-MM-DD). |
| type | string | – | Filter results by bounce type category (e.g., HardBounce, SoftBounce, SpamComplaint, DMARCPolicy, etc.). |
No output schema declared.
No examples provided.
list_email_opens_by_platform List Email Opens by Platform ~117
Retrieve email open statistics aggregated by email client platform. Filter results by tag and date range to analyze which platforms your recipients use to open emails.
| Name | Type | Req | Description |
|---|---|---|---|
| fromdate | string | – | Include statistics starting from this date (inclusive). Specify in ISO 8601 date format (YYYY-MM-DD). |
| tag | string | – | Filter statistics to only include opens from messages tagged with this value. |
| todate | string | – | Include statistics up to this date (inclusive). Specify in ISO 8601 date format (YYYY-MM-DD). |
No output schema declared.
No examples provided.
list_inbound_rule_triggers List Inbound Rule Triggers ~92
Retrieve a paginated list of inbound rule triggers configured for the server. Use count and offset parameters to control pagination through the results.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | The maximum number of trigger records to return in this request. Must be a positive integer. |
| offset | integer | yes | The number of records to skip before returning results, enabling pagination through large result sets. Must be a non-negative integer. |
No output schema declared.
No examples provided.
list_message_opens List Message Opens ~262
Retrieve a paginated list of message open events across all messages, with optional filtering by recipient, tags, client details, location, and platform.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | Filter results by city or region name where the message was opened (e.g., Moscow, New York). |
| client_company | string | – | Filter results by client company name (e.g., Microsoft, Apple, Google). |
| client_family | string | – | Filter results by client family (e.g., OS X, Chrome). |
| count | integer | yes | Number of open events to return per request, between 1 and 500. |
| country | string | – | Filter results by country where the message was opened (e.g., Denmark, Russia). |
| offset | integer | yes | Number of open events to skip before returning results, used for pagination. |
| os_family | string | – | Filter results by operating system family without version specificity (e.g., OS X, Windows). |
| platform | string | – | Filter results by platform type where the message was opened (e.g., webmail, desktop, mobile). |
| recipient | string | – | Filter results by recipient email address (To, Cc, or Bcc field). |
| tag | string | – | Filter results by message tag. |
No output schema declared.
No examples provided.
list_message_outbound_clicks List Message Outbound Clicks ~103
Retrieve click statistics for a specific outbound message, including details about each click event with pagination support.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | The number of click records to return per request, between 1 and 500 clicks. |
| messageid | string | yes | The unique identifier of the outbound message for which to retrieve click statistics. |
| offset | integer | yes | The number of click records to skip before returning results, used for pagination. Must be zero or greater. |
No output schema declared.
No examples provided.
list_outbound_click_stats_by_platform List Outbound Click Stats by Platform ~114
Retrieve outbound click statistics aggregated by browser platform. Use optional filters to narrow results by tag and date range.
| Name | Type | Req | Description |
|---|---|---|---|
| fromdate | string | – | Filter results to include only statistics from this date forward, specified in ISO 8601 format (YYYY-MM-DD). |
| tag | string | – | Filter results to include only clicks associated with a specific tag. |
| todate | string | – | Filter results to include only statistics up to and including this date, specified in ISO 8601 format (YYYY-MM-DD). |
No output schema declared.
No examples provided.
list_outbound_email_opens_by_client List Outbound Email Opens by Client ~122
Retrieve email client statistics for outbound message opens, optionally filtered by tag and date range. Use this to analyze which email clients your recipients use when opening messages.
| Name | Type | Req | Description |
|---|---|---|---|
| fromdate | string | – | Include opens starting from this date (inclusive). Specify in ISO 8601 date format (YYYY-MM-DD). |
| tag | string | – | Filter results to only include opens from messages tagged with this value. |
| todate | string | – | Include opens up to this date (inclusive). Specify in ISO 8601 date format (YYYY-MM-DD). |
No output schema declared.
No examples provided.
list_outbound_message_clicks List Outbound Message Clicks ~251
Retrieve click events from outbound messages with pagination and optional filtering by recipient, tags, client details, device information, and geographic location.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | Filter results by city or region name where the message was clicked. |
| client_company | string | – | Filter results by email client company name (e.g., Microsoft, Apple, Google). |
| client_family | string | – | Filter results by email client family or product line (e.g., OS X, Chrome). |
| count | integer | yes | Number of click records to return per request, up to a maximum of 500 results. |
| country | string | – | Filter results by country where the message was clicked. |
| offset | integer | yes | Number of click records to skip before returning results, used for pagination. |
| os_family | string | – | Filter results by operating system family without version specificity (e.g., OS X, Windows). |
| platform | string | – | Filter results by device platform type (e.g., webmail, desktop, mobile). |
| recipient | string | – | Filter results by recipient email address (To, Cc, or Bcc field). |
| tag | string | – | Filter results by message tag or label. |
No output schema declared.
No examples provided.
list_templates List Templates ~89
Retrieve a paginated list of email templates associated with this Postmark server. Use Count and Offset parameters to control pagination through your template collection.
| Name | Type | Req | Description |
|---|---|---|---|
| Count | integer | yes | The maximum number of templates to return in this request. Must be a positive integer. |
| Offset | integer | yes | The number of templates to skip before returning results, enabling pagination through your template collection. Must be a non-negative integer. |
No output schema declared.
No examples provided.
retry_inbound_message Retry Inbound Message ~67
Retry processing of a previously failed inbound message. Use this operation to reprocess a message that encountered an error during initial delivery or processing.
| Name | Type | Req | Description |
|---|---|---|---|
| messageid | string | yes | The unique identifier of the inbound message to retry. This should be the message ID returned from the inbound message service. |
No output schema declared.
No examples provided.
search_messages_inbound Search Inbound Messages ~241
Search and retrieve inbound messages with filtering by recipient, sender, subject, status, date range, and other metadata. Results are paginated using count and offset parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | Number of messages to return per request, between 1 and 500. |
| fromdate | string | – | Filter results to messages received on or after this date (format: YYYY-MM-DD). |
| fromemail | string | – | Filter results to messages sent from a specific email address. |
| mailboxhash | string | – | Filter results to messages associated with a specific mailbox hash identifier. |
| offset | integer | yes | Number of messages to skip from the beginning of results for pagination. |
| recipient | string | – | Filter results to messages received by a specific email address. |
| status | string | – | Filter results by message processing status: blocked, processed, queued, failed, or scheduled. |
| subject | string | – | Filter results to messages with a matching subject line. |
| tag | string | – | Filter results to messages with a specific tag label. |
| todate | string | – | Filter results to messages received on or before this date (format: YYYY-MM-DD). |
No output schema declared.
No examples provided.
search_messages_outbound Search Outbound Messages ~225
Search and retrieve outbound messages with filtering by recipient, sender, status, date range, and tags. Results are paginated using count and offset parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | Number of messages to return per request, between 1 and 500. |
| fromdate | string | – | Filter results to messages sent on or after this date (ISO 8601 format, e.g., 2014-02-01). |
| fromemail | string | – | Filter results to messages sent from a specific email address. |
| offset | integer | yes | Number of messages to skip from the beginning of results for pagination. |
| recipient | string | – | Filter results to messages received by a specific email address. |
| status | string | – | Filter results by message status: either queued (pending delivery) or sent (successfully delivered). |
| tag | string | – | Filter results to messages with a specific tag. |
| todate | string | – | Filter results to messages sent on or before this date (ISO 8601 format, e.g., 2014-02-01). |
No output schema declared.
No examples provided.
send_email Send Email ~329
Send a single email message through Postmark. Supports attachments, custom headers, link and open tracking, and email tagging for analytics.
| Name | Type | Req | Description |
|---|---|---|---|
| Attachments | array | – | Array of file attachments to include with the email. Each attachment should specify the file content, name, and MIME type. |
| From | string | – | Sender email address. Must correspond to a registered and confirmed Sender Signature in your Postmark account. |
| Headers | array | – | Array of custom email headers to include in the message. Each header should specify the name and value. |
| HtmlBody | string | – | If no TextBody specified HTML email message |
| ReplyTo | string | – | Email address to use for reply-to functionality. Overrides the default Reply To address configured in the sender signature. |
| Subject | string | – | Subject line for the email message. |
| Tag | string | – | Categorical tag for organizing and tracking email statistics. Useful for segmenting outgoing emails by type or campaign. |
| TextBody | string | – | If no HtmlBody specified Plain text email message |
| To | string | – | Recipient email address or addresses. Multiple recipients should be comma-separated. Maximum of 50 recipients per request. |
| TrackLinks | string | – | Link tracking mode for click analytics. Options are None (no tracking), HtmlAndText (track both HTML and plain text links), HtmlOnly (track HTML links only), or TextOnly (track plain text links only)… |
| TrackOpens | boolean | – | Enable open tracking for this email to measure when recipients open the message. |
No output schema declared.
No examples provided.
send_email_batch_with_templates Send Email Batch with Templates ~65
Send multiple emails in a single batch request using predefined email templates. This operation allows efficient bulk email delivery with template-based content.
| Name | Type | Req | Description |
|---|---|---|---|
| Messages | array | – | Array of email message objects to send, each containing template identifiers and recipient details. Order is preserved for batch processing. |
No output schema declared.
No examples provided.
send_email_with_template Send Email with Template ~425
Send an email to one or more recipients using a pre-defined email template. The template can be identified by either its numeric ID or string alias, and dynamic content is populated via the TemplateModel object.
| Name | Type | Req | Description |
|---|---|---|---|
| Attachments | array | – | Array of file attachments to include with the email. Each attachment should specify the file content, filename, and MIME type. |
| From | string | yes | Sender email address. Must be a valid email format and typically should be a verified sender on your Postmark account. |
| Headers | array | – | Array of custom email headers to add to the message. Each header should include the header name and value. |
| InlineCss | boolean | – | Whether to automatically inline CSS styles from the template's style tags into individual HTML elements. Defaults to true. |
| ReplyTo | string | – | Email address to set as the reply-to destination. Must be a valid email format if provided. |
| Tag | string | – | Arbitrary label or category tag to organize and filter this email in Postmark analytics and logs. |
| TemplateAlias | string | yes | Template identifier using a human-readable alias string. Either this or TemplateId must be provided to identify which template to use. |
| TemplateId | integer | yes | Template identifier using a numeric ID. Either this or TemplateAlias must be provided to identify which template to use. |
| TemplateModel | object | yes | Object containing key-value pairs that populate dynamic placeholders in the template. Structure should match the variables defined in your template. |
| To | string | yes | Recipient email address. Must be a valid email format. |
| TrackLinks | string | – | Enable click tracking by rewriting links in the email content. Options are: None (no tracking), HtmlAndText (track both HTML and plain text links), HtmlOnly (track HTML links only), or TextOnly (trac… |
| TrackOpens | boolean | – | Whether to track when this email is opened by the recipient. When enabled, Postmark injects a tracking pixel into the email. |
No output schema declared.
No examples provided.
send_emails_batch Send Emails Batch ~75
Send multiple emails in a single batch request to efficiently deliver messages through Postmark's email service.
| Name | Type | Req | Description |
|---|---|---|---|
| body | array | – | Array of email objects to send in this batch. Each object should contain the email details (recipient, subject, body, etc.) in Postmark's standard email format. Order is preserved for processing. |
No output schema declared.
No examples provided.
update_template Update Template ~132
Update an existing email template by its ID or alias. Modify the template's name, subject line, or alias identifier.
| Name | Type | Req | Description |
|---|---|---|---|
| Alias | string | – | Optional string identifier for the template using letters, numbers, and the characters '.', '-', '_'. Must start with a letter. |
| Name | string | – | Optional human-readable name for the template displayed in the UI. |
| Subject | string | – | Optional subject line template definition that supports variable substitution for dynamic email subjects. |
| templateIdOrAlias | string | yes | The unique identifier or alias of the template to update. Use either the numeric TemplateID or the string Alias value. |
No output schema declared.
No examples provided.
validate_template Validate Template ~139
Validate template content by testing subject lines, HTML, and text body rendering with optional CSS inlining and a test data model.
| Name | Type | Req | Description |
|---|---|---|---|
| InlineCssForHtmlTestRender | boolean | – | When validating HTML content, controls whether CSS style blocks are inlined as style attributes on matching elements. Defaults to true; set to false to disable CSS inlining. |
| Subject | string | – | The subject line template content to validate using Postmark's template language syntax. Required if neither HtmlBody nor TextBody is provided. |
| TestRenderModel | object | – | A data object used to render and test the template content, allowing validation of dynamic variable substitution and template logic. |
No output schema declared.
No examples provided.
What is the com.mcparmory/postmark MCP server?
com.mcparmory/postmark is an MCP server listed in the public MCP registry as com.mcparmory/postmark. Send, track, and manage transactional and bulk email delivery. This page covers its container image (ghcr.io/mcparmory/postmark:1.0.2).
Is the com.mcparmory/postmark MCP server safe to use?
com.mcparmory/postmark scores 49 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/postmark MCP server expose?
com.mcparmory/postmark exposes 39 tools: list_bounces, get_bounce_by_id, activate_bounce, get_bounce_dump, get_delivery_stats, and 34 more. Their descriptions and schemas cost roughly 4,966 tokens of context every time the server is loaded.
Is the com.mcparmory/postmark MCP server still maintained?
com.mcparmory/postmark 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.