Postmark
NPM · @PIPEWORX/MCP-POSTMARK · 2 COMPONENTS
Postmark MCP.
Available components
Last scanned (7 hours ago)
Scores higher than 61% of npm servers
Category Communication
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-postmark). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 631 tokens (~63/item across 10 items; 10 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "send" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 11 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
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Nov 26 +2
- Tool safety: pass → unverified ▼ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Stability: unverified → 0.20 ▲ functional
- First check of Schema quality: unverified functional
- Package version: 0.2.0 → 0.2.1 functional
- 30 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 76
First indexed and scored.
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 npm/@pipeworx/mcp-postmark@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-postmark |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-postmark/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3691857224 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:3f56565bae76e439da02ed943617af48e3cb4151f192d9c5cb59204c285954194b5e453dd0e8b9ff6c0c413f66a3d3372542e8df09702f2bf9205fa1b |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
bounce ~42
Fetch full details for a single Postmark bounce record by numeric id, including bounce type, recipient email, description, and raw bounce content.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
bounce_activate ~22
Re-activate a bounced address.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
bounces ~45
List bounced email records from the Postmark server with optional filters (type, inactive, emailFilter, tag, fromdate, todate); returns bounce type, recipient, and timestamp.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
delivery_stats ~13
Server-level delivery stats.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
message_outbound_detail ~22
Single outbound detail.
| Name | Type | Req | Description |
|---|---|---|---|
| messageId | string | yes | – |
No output schema declared.
No examples provided.
message_outbound_dump ~45
Retrieve the raw MIME source (full email dump) for a sent outbound message by messageId; useful for debugging encoding or header issues.
| Name | Type | Req | Description |
|---|---|---|---|
| messageId | string | yes | – |
No output schema declared.
No examples provided.
messages_outbound ~44
List outbound messages sent through the Postmark server with optional filters (recipient, from, tag, status, fromdate, todate); returns message summaries with status and timestamps.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
send ~199
Send one transactional email through the Postmark delivery API (api.postmarkapp.com/email) using a Postmark server token. Takes from, to, subject, HTML and text bodies, cc, bcc, reply-to, custom headers, tag, open and link tracking flags, and message stream; returns the Postmark MessageID, submitted-at timestamp, recipient, and error code. Use it to deliver a receipt, password reset, alert, or notification message.
| Name | Type | Req | Description |
|---|---|---|---|
| bcc | string | – | – |
| cc | string | – | – |
| from | string | yes | – |
| headers | array | – | – |
| htmlbody | string | – | – |
| messagestream | string | – | – |
| replyto | string | – | – |
| subject | string | – | – |
| tag | string | – | – |
| textbody | string | – | – |
| to | string | yes | – |
| trackLinks | string | – | – |
| trackopens | boolean | – | – |
No output schema declared.
No examples provided.
send_batch ~111
Send a batch of up to 500 transactional emails in one call to the Postmark delivery API (api.postmarkapp.com/email/batch), passing an array of messages in Postmark field form (From, To, Subject, HtmlBody, TextBody, Tag, MessageStream) and a Postmark server token. Returns one result per message with its MessageID, recipient, and error code. Use it for bulk receipts, digests, or notification sends through Postmark.
| Name | Type | Req | Description |
|---|---|---|---|
| emails | array | yes | – |
No output schema declared.
No examples provided.
server ~36
Fetch configuration and metadata for the current Postmark server, including name, color, delivery settings, bounce/spam threshold, and message stream settings.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the Postmark MCP server?
Postmark runs locally as an npm package, launched with npx -y @pipeworx/mcp-postmark. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-postmark
claude mcp add pipeworx-io-postmark -- npx -y @pipeworx/mcp-postmark
What is the Postmark MCP server?
Postmark is an MCP server listed in the public MCP registry as io.github.pipeworx-io/postmark. Postmark MCP. This page covers its npm package (@pipeworx/mcp-postmark).
Is the Postmark MCP server safe to use?
Postmark scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Postmark MCP server expose?
Postmark exposes 10 tools: send, send_batch, delivery_stats, messages_outbound, message_outbound_detail, and 5 more. Their descriptions and schemas cost roughly 579 tokens of context every time the server is loaded.
Is the Postmark MCP server still maintained?
Postmark 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 licence is the Postmark MCP server under?
Postmark declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.