dev.wraps/email
NPM · @WRAPS.DEV/MCP
Send email through your own Amazon SES account, and check domains, suppressions and sandbox status.
Available components
Last scanned (1 hour ago)
Scores higher than 98% 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 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
- 31 of 136 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 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability76
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 962 tokens (~137/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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
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.
- 3 Nov 26 0
- Package version: 0.11.0 → 0.11.1 functional
- 1 Nov 26 +16
- Stability: 0.97 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Malware scan: unverified → pass ▲ security
- Stability: 0.97 → pass security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ 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.10.0 → 0.11.0 functional
- 31 Oct 26 −16
- Malware scan: pass → unverified ▼ security
- Stability: pass → 0.97 functional
- Package version: 0.9.0 → 0.10.0 functional
- 24 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 23 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- Package version: 0.8.2 → 0.9.0 functional
- 22 Oct 26 +1
- Stability: 0.97 → pass security
- 20 Oct 26 −1
- Stability: pass → 0.93 functional
- 17 Oct 26 +3
- Stability: 0.80 → pass security
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/@wraps.dev/mcp@0.11.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 | 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.11.1 |
| Rekor log index | 3660995405 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:ce8569c37eefe234dd9f4c08b41c2275b103259dd0a124e51ed6be3332e2b5b9b9273813bcbe31022fd1395db8ee0e3fcf2e596b5dc3f5a8bfde32f3a |
Background: How many MCP packages publish verified provenance →
Dependencies 136 packages
| Packages resolved | 136 |
|---|---|
| Stale | 31 |
| 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 →
estimate_cost ~225
Estimate the monthly cost of sending email with Wraps + AWS: the flat Wraps plan fee 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.
| Name | Type | Req | Description |
|---|---|---|---|
| billing | string | – | Wraps billing interval |
| dedicatedIp | boolean | – | Include a dedicated sending IP |
| emails | integer | yes | Emails sent per month |
| 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. The fee is flat per plan and does not change with volume. |
| tracking | boolean | – | 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.
| Name | Type | Req | Description |
|---|---|---|---|
| messageId | string | yes | SES message id, as returned by send_email or list_recent_sends. |
| Name | Type | Req | Description |
|---|---|---|---|
| events | array | – | SES events in recorded order: Send, Delivery, Bounce, Complaint, Open, Click. |
| found | boolean | yes | False when no events are recorded yet for this messageId. |
| from | string | – | – |
| messageId | string | yes | – |
| sentAt | string | – | ISO 8601. |
| status | string | – | – |
| subject | string | – | – |
| to | array | – | – |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| enforcementStatus | string | yes | SES account enforcement state, e.g. HEALTHY. |
| fromEmailConfigured | boolean | yes | Whether WRAPS_FROM_EMAIL is set. |
| maxSend24Hour | number | yes | SES daily send quota. |
| nextAction | string | yes | The single next step that unblocks sending. |
| region | string | yes | – |
| sandbox | boolean | yes | True while the account can only send to verified recipients. |
| sentLast24Hours | number | yes | – |
| writeEnabled | boolean | yes | Whether 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).
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| hasMore | boolean | yes | True when more sends exist beyond this page. |
| sends | array | yes | – |
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).
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| complete | boolean | yes | False when SES reported more pages than were read; absence proves nothing. |
| entries | array | yes | – |
| mode | string | yes | lookup = exact single-address check; list = paged enumeration. |
| suppressed | boolean | – | Only present for mode=lookup. Authoritative for that address. |
No examples provided.
send_email ~167
Send a transactional email via your AWS SES account. Requires WRAPS_WRITE_ENABLED=true. The `from` address must be a verified SES identity (an address or domain) in this account and region. The `to` field accepts a single address or an array of addresses.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Subject line. |
| text | string | – | Plain-text body. Provide `html`, `text`, or both; at least one is required. |
| to | – | yes | Recipient address, or an array of up to 1000 addresses. |
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | yes | – |
| messageId | string | yes | SES message id; pass to get_email_event_log for delivery events. |
| to | array | yes | Recipients 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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain to check, e.g. example.com. SES identities are per-region. |
| Name | Type | Req | Description |
|---|---|---|---|
| dkimStatus | string | yes | SES DKIM status, e.g. SUCCESS, PENDING, FAILED. |
| dkimTokens | array | yes | CNAME tokens to publish in DNS. |
| domain | string | yes | – |
| region | string | yes | SES identities are per-region; this is the region checked. |
| verified | boolean | yes | True when SES will accept sends from this domain. |
No examples provided.
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
claude mcp add dev-wraps-email -- npx -y @wraps.dev/mcp
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. Send email through your own Amazon SES account, and check domains, suppressions and sandbox status. This page covers its npm package (@wraps.dev/mcp).
Is the dev.wraps/email MCP server safe to use?
dev.wraps/email scores 95 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 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 962 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 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 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.