io.github.zwebso/postlane
NPM · POSTLANE-MCP
Send transactional email and read send activity through the Postlane API.
Available components
Last scanned (3 hours ago)
Scores higher than 44% 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 & Transparency45
- 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
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 19 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 210 tokens (~70/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management67
- Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage86
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 58% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 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 → Fail
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
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.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +4
- Stability: unverified → 0.33 ▲ functional
- 12 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 11 Oct 26 0
- Security disclosure: fail → unverified ▼ 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 24 Oct 2026 · Analysed npm/postlane-mcp@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
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 →
get_email ~33
Read one Postlane send and its events by id.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Send id, such as em_… |
No output schema declared.
No examples provided.
list_emails ~26
List recent Postlane sends for this API key. Requires Read activity or Full access.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
send_email ~151
Send one transactional email through Postlane POST /v1/emails. The from domain must already be verified.
| Name | Type | Req | Description |
|---|---|---|---|
| bcc | – | – | Optional Bcc |
| cc | – | – | Optional Cc |
| from | string | yes | Verified sender, such as hello@send.example.com |
| html | string | – | – |
| idempotency_key | string | yes | Stable key for this logical send. Reuse it on retry. |
| reply_to | string | – | – |
| subject | string | – | – |
| template | string | – | Saved template name, such as Reset your password |
| text | string | – | – |
| to | – | yes | Recipient email, or an array of emails |
| variables | object | – | – |
No output schema declared.
No examples provided.
How do I install the io.github.zwebso/postlane MCP server?
io.github.zwebso/postlane runs locally as an npm package, launched with npx -y postlane-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · postlane-mcp
claude mcp add zwebso-postlane -- npx -y postlane-mcp
What is the io.github.zwebso/postlane MCP server?
io.github.zwebso/postlane is an MCP server listed in the public MCP registry as io.github.zwebso/postlane. Send transactional email and read send activity through the Postlane API. This page covers its npm package (postlane-mcp).
Is the io.github.zwebso/postlane MCP server safe to use?
io.github.zwebso/postlane scores 73 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 24 October 2026. It declares no install or post-install scripts. 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 io.github.zwebso/postlane MCP server expose?
io.github.zwebso/postlane exposes 3 tools: send_email, get_email, list_emails. Their descriptions and schemas cost roughly 210 tokens of context every time the server is loaded.
Is the io.github.zwebso/postlane MCP server still maintained?
io.github.zwebso/postlane is still listed as active in the MCP registry. We last reached this channel on 24 October 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 io.github.zwebso/postlane MCP server under?
io.github.zwebso/postlane declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.