Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

dev.wraps/email

NPM · @WRAPS.DEV/MCP · SCANNED SEP 20

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

Available components

npm · @wraps.dev/mcp 81
+32 this week 81 Trust /100
Trust breakdown (7 categories)

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 Security99
  • 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
  • 32 of 139 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to wraps-team/wraps-js). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 5 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 970 tokens (~138/item across 7 items; 7 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 Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
  • Structured output schemas are declared (86% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 7 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.

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.

npm · @wraps.dev/mcp

# add to Claude Code
claude mcp add dev-wraps-email -- npx -y @wraps.dev/mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "dev-wraps-email": {
      "command": "npx",
      "args": [
        "-y",
        "@wraps.dev/mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "dev-wraps-email": {
      "command": "npx",
      "args": [
        "-y",
        "@wraps.dev/mcp"
      ]
    }
  }
}
# add to Codex CLI
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
    }
  }
}
# add to OpenClaw
openclaw mcp add dev-wraps-email --command npx --arg -y --arg @wraps.dev/mcp
# ~/.hermes/config.yaml
mcp_servers:
  dev-wraps-email:
    command: "npx"
    args: ["-y", "@wraps.dev/mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "dev-wraps-email": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@wraps.dev/mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add dev-wraps-email -t stdio -c npx -a -y @wraps.dev/mcp
// mcp.json
{
  "mcpServers": {
    "dev-wraps-email": {
      "command": "npx",
      "args": [
        "-y",
        "@wraps.dev/mcp"
      ]
    }
  }
}
Changelog

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.

  • 18 Sept 26 0
    • Package version: 0.7.1 → 0.8.0 functional
  • 15 Sept 26 +15
    • Malware scan: unverified → pass ▲ security
  • 14 Sept 26 +17
    • Malware scan: pass → unverified ▼ security
    • 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. security
    • Tool coverage: unverified → 100 ▲ functional
    • 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 functional
  • 9 Sept 26 49

    First indexed and scored.

Diagnostics

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 npm/@wraps.dev/mcp@0.8.0

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 wraps-team/wraps-js
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/wraps-team/wraps-js/.github/workflows/publish.yml@refs/tags/mcp-v0.8.0
Rekor log index 2832317730
Predicate type https://slsa.dev/provenance/v1
Subject digest sha512:38d5c7e2ecc108ca9152221858b9917f519c832fb8f81840ab42f5a4bd0b2f73a548cb29eb4556c07ff31a66ea68a4f55dd0a53277190f26813be211b

Background: How many MCP packages publish verified provenance →

Dependencies 139 packages
Packages resolved 139
Stale 32
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 7 exposed · ~970 tokens

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 →

Tool Tokens
estimate_cost ~243

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.

NameTypeReqDescription
billingstring–Wraps billing interval
dedicatedIpboolean–Include a dedicated sending IP
emailsintegeryesEmails sent per month
eventsinteger–Wraps tracked events per month (sends, opens, clicks, bounces, custom events)
retentionstring–Email event history retention
sesPlanstring–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.
tierstring–Wraps plan
trackingboolean–Whether the event tracking pipeline is deployed (default true)

No output schema declared.

No examples provided.

get_email_event_log ~64

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

NameTypeReqDescription
messageIdstringyesSES message id, as returned by send_email or list_recent_sends.
NameTypeReqDescription
eventsarray–SES events in recorded order: Send, Delivery, Bounce, Complaint, Open, Click.
foundbooleanyesFalse when no events are recorded yet for this messageId.
fromstring––
messageIdstringyes–
sentAtstring–ISO 8601.
statusstring––
subjectstring––
toarray––

No examples provided.

get_setup_status ~41

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.

Input schema present but exposes no named parameters.

NameTypeReqDescription
enforcementStatusstringyesSES account enforcement state, e.g. HEALTHY.
fromEmailConfiguredbooleanyesWhether WRAPS_FROM_EMAIL is set.
maxSend24HournumberyesSES daily send quota.
nextActionstringyesThe single next step that unblocks sending.
regionstringyes–
sandboxbooleanyesTrue while the account can only send to verified recipients.
sentLast24Hoursnumberyes–
writeEnabledbooleanyesWhether WRAPS_WRITE_ENABLED permits sending.

No examples provided.

list_recent_sends ~148

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

NameTypeReqDescription
limitinteger–Maximum number of messages to return, newest first (default 20).
sincestring–Only messages with activity at or after this ISO 8601 datetime.
NameTypeReqDescription
hasMorebooleanyesTrue when more sends exist beyond this page.
sendsarrayyes–

No examples provided.

list_suppressions ~254

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

NameTypeReqDescription
emailstring–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…
limitinteger–Maximum number of addresses to list (default 20, max 100). The response always states whether the listing was truncated.
reasonstring–Only list addresses suppressed for this reason.
NameTypeReqDescription
completebooleanyesFalse when SES reported more pages than were read; absence proves nothing.
entriesarrayyes–
modestringyeslookup = exact single-address check; list = paged enumeration.
suppressedboolean–Only present for mode=lookup. Authoritative for that address.

No examples provided.

send_email ~157

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.

NameTypeReqDescription
fromstring–Sender address. Must be a verified SES identity in this account. Defaults to WRAPS_FROM_EMAIL.
htmlstring–HTML body. Provide `html`, `text`, or both; at least one is required.
subjectstringyesSubject line.
textstring–Plain-text body. Provide `html`, `text`, or both; at least one is required.
to–yesRecipient address, or an array of up to 1000 addresses.
NameTypeReqDescription
fromstringyes–
messageIdstringyesSES message id; pass to get_email_event_log for delivery events.
toarrayyesRecipients the message was accepted for.

No examples provided.

verify_domain_status ~63

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.

NameTypeReqDescription
domainstringyesDomain to check, e.g. example.com. SES identities are per-region.
NameTypeReqDescription
dkimStatusstringyesSES DKIM status, e.g. SUCCESS, PENDING, FAILED.
dkimTokensarrayyesCNAME tokens to publish in DNS.
domainstringyes–
regionstringyesSES identities are per-region; this is the region checked.
verifiedbooleanyesTrue when SES will accept sends from this domain.

No examples provided.

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.