Ext Ops Panel
Open dashboard
Comparison

Resend vs io.github.bitterdev/dropscan-mcp

Resend is an MCP server published by resend. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.bitterdev/dropscan-mcp is an MCP server published by bitterdev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-13. 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
MarketplaceResendio.github.bitterdev/dropscan-mcp
Docker MCP Catalog Listed
Version: sha256:2a786579214e
Forks (GitHub): 91
Pulls (Docker Hub): 21 822
Stars (Docker Hub): 5
Stars (GitHub): 576
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.1
Downloads/month (PyPI): 70
Downloads/week (PyPI): 25
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

Resend vs io.github.bitterdev/dropscan-mcp
FactResendio.github.bitterdev/dropscan-mcp
Marketplaces that list it11
Stars (GitHub) (differs)576 (better)1 (worse)
Pulls (Docker Hub) (differs)21 822No figure on Docker Hub
Forks (GitHub) (differs)91 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/resend)On your machine (dropscan-mcp)
Transportstdiostdio
Tools it declares (differs)1Not published
Environment variables it asks for (differs)3, secrets among them: 12, secrets among them: 1
Licence (differs)MITNot stated
Repository (differs)github.com/resend/mcp-send-emailgithub.com/bitterdev/dropscan-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11

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

Resend

In its own words, on Docker MCP Catalog:

The official MCP server to send emails and interact with Resend.

io.github.bitterdev/dropscan-mcp

In its own words, on Official MCP Registry:

MCP server for the Dropscan postal mail scanning API: read scanned letters, act on mailings.

How to run each

Resend As a local MCP server: Docker image

Claude Code
claude mcp add --env "RESEND_API_KEY=<YOUR_RESEND_API_KEY>" --transport stdio resend -- docker run -i --rm -e RESEND_API_KEY mcp/resend

Requires: RESEND_API_KEY (secret)

io.github.bitterdev/dropscan-mcp As a local MCP server: PyPI package

Claude Code
claude mcp add --env "DROPSCAN_API_TOKEN=<YOUR_DROPSCAN_API_TOKEN>" --transport stdio dropscan-mcp -- uvx dropscan-mcp

Requires: DROPSCAN_API_TOKEN (secret)

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

Tools each declares

The marketplaces of io.github.bitterdev/dropscan-mcp publish no list of tools, so we do not compare tools.

Settings each asks for

Only Resend asks for

  • REPLY_TO_EMAIL_ADDRESSES
  • RESEND_API_KEY (secret)
  • SENDER_EMAIL_ADDRESS

Only io.github.bitterdev/dropscan-mcp asks for

  • DROPSCAN_ALLOW_WRITES
  • DROPSCAN_API_TOKEN (secret)

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: Resend · What it can do: io.github.bitterdev/dropscan-mcp · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. 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