Ext Ops Panel
Open dashboard
Comparison

dev.wraps/email vs Sendsets

dev.wraps/email is an MCP server published by wraps.dev. Marketplaces we read that list it: 1 (Official MCP Registry). Sendsets is an MCP server published by AddisonHoff. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-14. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplacedev.wraps/emailSendsets
Official MCP Registry Listed
Version: 0.8.2
Downloads/month (npm): 888
Downloads/week (npm): 59
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

dev.wraps/email vs Sendsets
Factdev.wraps/emailSendsets
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub)11
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)On your machine (@wraps.dev/mcp)Remote server (api.sendsetsapi.com/v1/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)7, secrets among them: 0Not published
Parts of the bundle (differs)Not a bundle4
Licence (differs)Not statedApache-2.0
Repository (differs)github.com/wraps-team/wraps-jsgithub.com/addisonhoff/sendsets
Changes in the last 7 days (differs)02
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checknot checked yet

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

dev.wraps/email

In its own words, on Official MCP Registry:

Send email through your own Amazon SES account, and check domains, suppressions and sandbox status.

Sendsets

In its own words, on Official MCP Registry:

Cold email API for AI agents: connect mailboxes, warm up, run campaigns and handle replies.

How to run each

dev.wraps/email As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio email -- npx -y @wraps.dev/mcp

Sendsets As a remote MCP server

Claude Code
claude mcp add --transport http sendsets https://api.sendsetsapi.com/v1/mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

The marketplaces of Sendsets publish no settings it asks for, so we do not compare settings.

What it can do: dev.wraps/email · What it can do: Sendsets · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built