# io.github.zwebso/postlane (npm · postlane-mcp)

Send transactional email and read send activity through the Postlane API.

- Trust score: 73/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-24

## Components

- npm · `postlane-mcp`: 73/100 (this document), [markdown](https://verifymcp.io/servers/zwebso-postlane/postlane-mcp.md), [page](https://verifymcp.io/servers/zwebso-postlane/postlane-mcp)

## Channel facts

- Registry: `npm`
- Package: `postlane-mcp`
- Version: `0.1.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-24.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 19 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 210 tokens (~70/item across 3 items; 3 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 67/100
  - Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 86/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 58% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 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.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add zwebso-postlane -- npx -y postlane-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "zwebso-postlane": {
      "command": "npx",
      "args": [
        "-y",
        "postlane-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "zwebso-postlane": {
      "command": "npx",
      "args": [
        "-y",
        "postlane-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add zwebso-postlane -- npx -y postlane-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "zwebso-postlane": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "postlane-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add zwebso-postlane --command npx --arg -y --arg postlane-mcp
```

### Hermes

```yaml
mcp_servers:
  zwebso-postlane:
    command: "npx"
    args: ["-y", "postlane-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "zwebso-postlane": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "postlane-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add zwebso-postlane -t stdio -c npx -a -y postlane-mcp
```

### Other

```json
{
  "mcpServers": {
    "zwebso-postlane": {
      "command": "npx",
      "args": [
        "-y",
        "postlane-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-24 (score 73, +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.

### 2026-10-21 (score 72, +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.

### 2026-10-19 (score 71, +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.

### 2026-10-17 (score 70, +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.

### 2026-10-15 (score 69, +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.

### 2026-10-14 (score 68, +4)

- [functional improvement] Stability: unverified → 0.33

### 2026-10-12 (score 64, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-10-11 (score 64, 0)

- [functional regression] Security disclosure: fail → unverified

## MCP tools (3)

### `send_email` (~151 tokens)

Send one transactional email through Postlane POST /v1/emails. The from domain must already be verified.

Input parameters:

- `bcc`: Optional Bcc
- `cc`: Optional Cc
- `from` (string, required): Verified sender, such as hello@send.example.com
- `html` (string)
- `idempotency_key` (string, required): 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` (required): Recipient email, or an array of emails
- `variables` (object)

### `get_email` (~33 tokens)

Read one Postlane send and its events by id.

Input parameters:

- `id` (string, required): Send id, such as em_…

### `list_emails` (~26 tokens)

List recent Postlane sends for this API key. Requires Read activity or Full access.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/zwebso-postlane/postlane-mcp#diagnostics

## Score history

- 2026-10-24: 73
- 2026-10-23: 72
- 2026-10-22: 72
- 2026-10-21: 72
- 2026-10-20: 71
- 2026-10-19: 71
- 2026-10-18: 70
- 2026-10-17: 70
- 2026-10-16: 69
- 2026-10-15: 69
- 2026-10-14: 68
- 2026-10-13: 64
- 2026-10-12: 64
- 2026-10-11: 64
- 2026-10-05: 64
- 2026-10-04: 64

## Common questions

### 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.

## Links

- npm package: https://www.npmjs.com/package/postlane-mcp
- Socket report: https://socket.dev/npm/package/postlane-mcp
- Repository: https://github.com/zwebso/postlane
- Website: https://www.postlane.email/docs
- Changelog RSS feed: https://verifymcp.io/servers/zwebso-postlane/postlane-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/zwebso-postlane/postlane-mcp.json
- HTML version of this page: https://verifymcp.io/servers/zwebso-postlane/postlane-mcp