io.github.bitterdev/dropscan-mcp vs io.github.shipmail-to/shipmail-mcp
io.github.bitterdev/dropscan-mcp is an MCP server published by bitterdev. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.shipmail-to/shipmail-mcp is an MCP server published by shipmail-to. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-23. 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
| Marketplace |  io.github.bitterdev/dropscan-mcp |  io.github.shipmail-to/shipmail-mcp |
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.1 Downloads/month (PyPI): 70 Downloads/week (PyPI): 19 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Listed Version: 0.9.6 Downloads/month (npm): 1 732 Downloads/week (npm): 156 Forks (GitHub): 2 Stars (GitHub): 1 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 0.9.6 Downloads/month (npm): 1 732 Downloads/week (npm): 156 Forks (GitHub): 2 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
| Fact | io.github.bitterdev/dropscan-mcp | io.github.shipmail-to/shipmail-mcp |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) | 1 | 1 |
| Forks (GitHub) (differs) | 0 (worse) | 2 (better) |
| Last release (differs) | Not published | 2026-10-15 |
| Where it runs (differs) | On your machine (dropscan-mcp) | Remote server or your machine |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 1 | 1, secrets among them: 1 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/bitterdev/dropscan-mcp | github.com/shipmail-to/shipmail-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 44 h ago |
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
io.github.bitterdev/dropscan-mcp
MCP server for the Dropscan postal mail scanning API: read scanned letters, act on mailings.
io.github.shipmail-to/shipmail-mcp
Shipmail MCP server. Modern email for your business, with an API for your agents.
How to run each
io.github.bitterdev/dropscan-mcp As a local MCP server: PyPI package
claude mcp add --env "DROPSCAN_API_TOKEN=<YOUR_DROPSCAN_API_TOKEN>" --transport stdio dropscan-mcp -- uvx dropscan-mcpRequires: DROPSCAN_API_TOKEN (secret)
io.github.shipmail-to/shipmail-mcp As a remote MCP server
claude mcp add --transport http shipmail-mcp https://shipmail.to/api/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: SHIPMAIL_API_KEY (secret), Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only io.github.shipmail-to/shipmail-mcp has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Only io.github.bitterdev/dropscan-mcp asks for
DROPSCAN_ALLOW_WRITESDROPSCAN_API_TOKEN (secret)
Only io.github.shipmail-to/shipmail-mcp asks for
SHIPMAIL_API_KEY (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: io.github.bitterdev/dropscan-mcp · What it can do: io.github.shipmail-to/shipmail-mcp · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.