← Index

dev.wraps/email

dev.wraps/emailv0.7.1AWS

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

The current version, v0.7.1, was published to the official MCP registry on 2026-09-09. It is distributed as @wraps.dev/mcp on npm, filed under AWS by this index, and declares 7 environment variables. Removals and unreachable sources are measured across every server this index tracks, contract drift across the servers that answer in consecutive snapshots; the index's current counts put this record in context.

In-path gate · all MCP tools

Using dev.wraps/email in Claude, Cursor, Gemini CLI, Cline, or Zed?

MCP tool contracts can change remotely with no version bump. The mcpindex gate pins each contract and HOLDs the call when it drifts-before your agent acts. Zero credentials. This is not the package install for this server itself (use Install this server for that).

Install the mcpindex gate (one command)

Rewrites your MCP host config so each server launches behind the gate. Inspect first: curl -fsSL https://mcpindex.ai/install.sh | less

uv tool install mcpindex-gate && mcpindex-config-wire
Trust verdict · v1 advisory · method
NOT YET SCREENEDno verdict on file

Verdict not yet evaluated for this tool. The semantic screen takes adversarial cases first; coverage rolls out as the corpus expands (15/150 labels to graduation). The deterministic conformance probe is built but has not yet run on the public corpus, so a recorded verdict here is REVIEW or UNVERIFIED, never a clearing ALLOW. Until a verdict is recorded, an agent should treat this tool as not-yet-cleared and fall back to its own checks. Method: the eval, four-state verdict, honest limits.

Own this server? Screen its description →

That verdict was true at screening time (snapshot 2026-09-10).

Contracts can change after screening, with no version bump. The gate pins dev.wraps/email’s tool contracts on first sight and holds any silent change before your agent acts - the check that keeps being true on Tuesday.

See your first HOLD in 2 minutes →

Related: how to trust an MCP server · screen before install · silent contract drift

Environment variables
AWS_REGION

Region your Wraps stack is deployed in. Optional only if your active AWS profile supplies one — SES identities are per-region.

AWS_PROFILE

AWS profile to use. Credentials are read locally and never leave the machine.

WRAPS_WRITE_ENABLED

Set to true to enable the send_email tool. Read-only by default.

WRAPS_FROM_EMAIL

Default from address for send_email. Must be a domain verified in your SES account.

WRAPS_ALLOWED_RECIPIENTS

Comma-separated addresses the agent may send to. Restricts send_email when write mode is on.

WRAPS_ALLOWED_RECIPIENT_DOMAINS

Comma-separated domains the agent may send to. Matching is exact; list subdomains explicitly.

WRAPS_HISTORY_TABLE_NAME

DynamoDB table holding email history. Defaults to wraps-email-history.

MCP quality score · maturity, not trust · methodology
freshness
25
completeness
15
installability
25
documentation
15
stability
5
Alternatives in AWS