# dev.wraps/email (npm · @wraps.dev/mcp)

Query SES send history, delivery events, domains and suppressions, and send from your AWS account.

- Trust score: 81/100 (high trust)
- Change this week: +32
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- npm · `@wraps.dev/mcp`: 81/100 (this document), [markdown](https://verifymcp.io/servers/dev-wraps-email/wraps-dev-mcp.md), [page](https://verifymcp.io/servers/dev-wraps-email/wraps-dev-mcp)

## Channel facts

- Registry: `npm`
- Package: `@wraps.dev/mcp`
- Version: `0.8.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-09-20.

- **Supply Chain Security**: 99/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.
  - 32 of 139 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to wraps-team/wraps-js).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 5 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 75/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 970 tokens (~138/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (86% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

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

## Install

### How do I install the dev.wraps/email MCP server?

dev.wraps/email runs locally as an npm package, launched with npx -y @wraps.dev/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 dev-wraps-email -- npx -y @wraps.dev/mcp
```

### Cursor

```json
{
  "mcpServers": {
    "dev-wraps-email": {
      "command": "npx",
      "args": [
        "-y",
        "@wraps.dev/mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-wraps-email": {
      "command": "npx",
      "args": [
        "-y",
        "@wraps.dev/mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add dev-wraps-email -- npx -y @wraps.dev/mcp
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add dev-wraps-email --command npx --arg -y --arg @wraps.dev/mcp
```

### Hermes

```yaml
mcp_servers:
  dev-wraps-email:
    command: "npx"
    args: ["-y", "@wraps.dev/mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "dev-wraps-email": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@wraps.dev/mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-wraps-email -t stdio -c npx -a -y @wraps.dev/mcp
```

### Other

```json
{
  "mcpServers": {
    "dev-wraps-email": {
      "command": "npx",
      "args": [
        "-y",
        "@wraps.dev/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-09-18 (score 81, 0)

- [functional] Package version: 0.7.1 → 0.8.0

### 2026-09-15 (score 81, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-09-14 (score 66, +17)

- [security regression] Malware scan: pass → unverified
- [security improvement] Injection markers: unverified → pass
- [security] First check of Judged manipulation: pass
- [security] Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window).
- [security] Tool safety: Tool safety not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet.
- [security] Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] MCP protocol: unverified → pass
- [functional] First check of Schema quality: fail
- [functional] First check of Schema quality: excellent
- [functional] First check of Schema quality: fail
- [functional] First check of Tool coverage: 86
- [functional] First check of Destructive annotations: 100
- [functional] First check of Tool coverage: 100
- [functional] Capabilities: Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet.
- [functional] Tool coverage: Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet.
- [functional] Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [functional] Package version: 0.7.1 → 0.8.0

### 2026-09-09 (score 49)

First indexed and scored.

## MCP tools (7)

### `send_email` (~157 tokens)

Send a transactional email via your AWS SES account. Requires WRAPS_WRITE_ENABLED=true. The `from` address must be a verified Wraps domain. The `to` field accepts a single address or an array of addresses.

Input parameters:

- `from` (string): Sender address. Must be a verified SES identity in this account. Defaults to WRAPS_FROM_EMAIL.
- `html` (string): HTML body. Provide `html`, `text`, or both; at least one is required.
- `subject` (string, required): Subject line.
- `text` (string): Plain-text body. Provide `html`, `text`, or both; at least one is required.
- `to` (required): Recipient address, or an array of up to 1000 addresses.

Output parameters:

- `from` (string)
- `messageId` (string): SES message id; pass to get_email_event_log for delivery events.
- `to` (array): Recipients the message was accepted for.

### `list_recent_sends` (~148 tokens)

List recently sent emails from your Wraps email history, newest first, at most `limit` messages. The timestamp shown is the send time and is stable across calls. Returns send status, subject, recipient, timestamp, and messageId for each send. Use the messageId with get_email_event_log for full delivery details. The `since` parameter accepts a full ISO 8601 datetime string (e.g., 2024-01-01T00:00:00Z).

Input parameters:

- `limit` (integer): Maximum number of messages to return, newest first (default 20).
- `since` (string): Only messages with activity at or after this ISO 8601 datetime.

Output parameters:

- `hasMore` (boolean): True when more sends exist beyond this page.
- `sends` (array)

### `get_email_event_log` (~64 tokens)

Get the full delivery event log for a specific email by its messageId. Returns all SES events: Send, Delivery, Bounce, Complaint, Open, Click.

Input parameters:

- `messageId` (string, required): SES message id, as returned by send_email or list_recent_sends.

Output parameters:

- `events` (array): SES events in recorded order: Send, Delivery, Bounce, Complaint, Open, Click.
- `found` (boolean): False when no events are recorded yet for this messageId.
- `from` (string)
- `messageId` (string)
- `sentAt` (string): ISO 8601.
- `status` (string)
- `subject` (string)
- `to` (array)

### `verify_domain_status` (~63 tokens)

Check the verification and DKIM status of a sending domain in your AWS SES account. Returns whether the domain is verified for sending and its DKIM configuration status.

Input parameters:

- `domain` (string, required): Domain to check, e.g. example.com. SES identities are per-region.

Output parameters:

- `dkimStatus` (string): SES DKIM status, e.g. SUCCESS, PENDING, FAILED.
- `dkimTokens` (array): CNAME tokens to publish in DNS.
- `domain` (string)
- `region` (string): SES identities are per-region; this is the region checked.
- `verified` (boolean): True when SES will accept sends from this domain.

### `list_suppressions` (~254 tokens)

List addresses on your AWS SES account-level suppression list, or check a single address with `email`. SES silently drops mail to suppressed addresses, and sending to them damages your sending reputation, so check before sending to an address you have not sent to recently. To determine whether one specific address is suppressed, always pass `email` — that is an exact lookup. The listing is paginated and states explicitly when it is truncated; a truncated listing is never proof that an address is unsuppressed. Optionally filter the listing by reason (BOUNCE or COMPLAINT).

Input parameters:

- `email` (string): Check this ONE address against SES and report whether it is suppressed. Use this for any "is <address> suppressed?" question: it is an exact lookup. Do NOT answer that question from the listing inste…
- `limit` (integer): Maximum number of addresses to list (default 20, max 100). The response always states whether the listing was truncated.
- `reason` (string): Only list addresses suppressed for this reason.

Output parameters:

- `complete` (boolean): False when SES reported more pages than were read; absence proves nothing.
- `entries` (array)
- `mode` (string): lookup = exact single-address check; list = paged enumeration.
- `suppressed` (boolean): Only present for mode=lookup. Authoritative for that address.

### `get_setup_status` (~41 tokens)

Check this AWS SES account's sandbox status and get a recommended next action for getting a first send out. Read-only — makes no changes to your AWS account.

Output parameters:

- `enforcementStatus` (string): SES account enforcement state, e.g. HEALTHY.
- `fromEmailConfigured` (boolean): Whether WRAPS_FROM_EMAIL is set.
- `maxSend24Hour` (number): SES daily send quota.
- `nextAction` (string): The single next step that unblocks sending.
- `region` (string)
- `sandbox` (boolean): True while the account can only send to verified recipients.
- `sentLast24Hours` (number)
- `writeEnabled` (boolean): Whether WRAPS_WRITE_ENABLED permits sending.

### `estimate_cost` (~243 tokens)

Estimate the monthly cost of sending email with Wraps + AWS: the Wraps platform fee, tracked-event overage, and an itemized AWS bill (SES, EventBridge, SQS, Lambda, DynamoDB, dedicated IP, WAF). Use this instead of calculating by hand — the cost model has several interacting variables, including which SES pricing plan the AWS account is on. Requires no AWS credentials.

Input parameters:

- `billing` (string): Wraps billing interval
- `dedicatedIp` (boolean): Include a dedicated sending IP
- `emails` (integer, required): Emails sent per month
- `events` (integer): Wraps tracked events per month (sends, opens, clicks, bounces, custom events)
- `retention` (string): Email event history retention
- `sesPlan` (string): AWS SES pricing plan for this account and Region. AWS defaults new accounts to 'essentials' ($0.16/1K); 'alacarte' is $0.10/1K. Defaults to alacarte.
- `tier` (string): Wraps plan
- `tracking` (boolean): Whether the event tracking pipeline is deployed (default true)

## Diagnostics

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

## Score history

- 2026-09-20: 81
- 2026-09-19: 81
- 2026-09-18: 81
- 2026-09-17: 81
- 2026-09-16: 81
- 2026-09-15: 81
- 2026-09-14: 66
- 2026-09-13: 49
- 2026-09-12: 49
- 2026-09-11: 49
- 2026-09-10: 49
- 2026-09-09: 49

## Common questions

### What is the dev.wraps/email MCP server?

dev.wraps/email is an MCP server listed in the public MCP registry as dev.wraps/email. Query SES send history, delivery events, domains and suppressions, and send from your AWS account. This page covers its npm package (@wraps.dev/mcp).

### Is the dev.wraps/email MCP server safe to use?

dev.wraps/email scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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 dev.wraps/email MCP server expose?

dev.wraps/email exposes 7 tools: send_email, list_recent_sends, get_email_event_log, verify_domain_status, list_suppressions, and 2 more. Their descriptions and schemas cost roughly 970 tokens of context every time the server is loaded.

### Is the dev.wraps/email MCP server still maintained?

dev.wraps/email 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.

### What licence is the dev.wraps/email MCP server under?

dev.wraps/email 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/@wraps.dev/mcp
- Socket report: https://socket.dev/npm/package/@wraps.dev/mcp
- Repository: https://github.com/wraps-team/wraps-js
- Website: https://wraps.dev/
- Changelog RSS feed: https://verifymcp.io/servers/dev-wraps-email/wraps-dev-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-wraps-email/wraps-dev-mcp.json
- HTML version of this page: https://verifymcp.io/servers/dev-wraps-email/wraps-dev-mcp