MCP.Market

Dropscan MCP server

by bitterdev·io.github.bitterdev/dropscan-mcp·v0.1.1

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

B78/100grade B
What users say
No reviews yet
Be the first
Safety scan
B78/100

full report

Adoption
New

0 stars19 downloads/wk

Reviews

Write one

Nobody has reviewed Dropscan yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Dropscan tools (21, 6 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • cancel_mailing_actionwrite action

    Cancel a pending action request on a mailing.

  • create_forwarding_addresswrite action

    Create a forwarding address (used as a forward target).

  • create_recipientwrite action

    Create a recipient on a scanbox.

  • create_webhook_rulewrite action

    Create a webhook rule.

  • delete_webhook_rulewrite action

    Delete a webhook rule.

  • get_forwarding_address

    Get a forwarding address by id. Read-only.

  • get_mailing

    Get one mailing with its details/extracted content. Read-only.

  • get_mailing_envelope

    Download a mailing's envelope image (JPEG) and save it. Read-only.

  • get_mailing_pdf

    Download a mailing's scanned PDF and save it to disk. Read-only.

  • get_mailing_plaintext

    Get OCR plaintext of a mailing (first 5 documents). Read-only.

  • get_mailing_zip

    Download a mailing's ZIP (individual PDFs) and save it. Read-only.

  • get_recipient

    Get one recipient of a scanbox. Read-only.

  • get_shipment

    Get a shipment (physical forwarding batch) by id. Read-only.

  • get_webhook_rule

    Get one webhook rule by id. Read-only.

  • list_mailings

    List mailings in a scanbox (GET /scanboxes/{id}/mailings). Read-only.

  • list_recipients

    List recipients configured for a scanbox. Read-only.

  • list_scanboxes

    List all scanboxes on the account (GET /scanboxes). Read-only.

  • list_webhook_rules

    List all webhook rules on the account. Read-only.

  • request_mailing_action

    Request a physical action on a mailing (scan / forward / destroy).

  • set_mailing_recipient

    Assign a recipient to a mailing.

  • update_webhook_rulewrite action

    Update a webhook rule.

Public scan report

scanner v0.1.9 · 2026-09-24 · same rubric, same numbers if you re-run it

no findings
  • Code scan5 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 59 days ago12/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 78/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Dropscan compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
78/100
higher than 57% of 48,255 servers
Tools
21
the typical server has 7
Tools that change things
29%
typical: 0%. Fewer write tools means less an agent can break
Downloads a week
19
more than 6% of 12,191 servers with a package

What its tools let an agent do: 14 read · 3 create · 2 change · 2 delete

Install Dropscan in Claude Code, Cursor or VS Code

claude mcp add dropscan-mcp -- uvx dropscan-mcp
Add to Cursor

What the publisher says

From the Dropscan repository's README, as published. We do not edit it. Read it on GitHub

dropscan-mcp

MCP (Model Context Protocol) server for the Dropscan postal-mail-to-email API. Dropscan receives your physical letters at a scanbox; this server lets your MCP client list mailings, download the scans (PDF / ZIP / envelope image / OCR text), and, when explicitly enabled, request actions (scan / forward / destroy) and manage recipients, forwarding addresses and webhook rules.

mcp-name: io.github.bitterdev/dropscan-mcp

Safety first: Dropscan has no sandbox

Every request hits the real production account. Actions are irreversible: a destroyed letter is physically shredded and gone, a forward physically mails the letter and costs money.

Because of that, all write/action tools are gated twice:

  1. DROPSCANALLOWWRITES environment flag. Unless it is set to 1/true/yes, every non-GET tool refuses to run. It is disabled by default.
  2. confirm: true parameter. Each write/action tool takes an explicit confirm argument (default false) and refuses unless it is true.

Read-only GET tools are always available and never change state.

Tools

Read-only (always available)

The download tools save the asset to disk (default ~/Downloads, override with savepath or the DROPSCANDOWNLOAD_DIR env var) and return the saved path, byte size and content type.

Write / action (double-gated: DROPSCANALLOWWRITES=1 and confirm=true)

actiontype is one of scan, forward, destroy (exact enum from the API). For forward, both forwardingaddressid and forwardingdate (ISO YYYY-MM-DD) are required.

Webhook events: mailingreceived, scanrequested, mailingscanned, mailingarchived, mailingtrashed, mailingshredded, mailingaddedtoshipment, mailingremovedfromshipment, shipmentsent, packagetracking_updated.

Requirements

  • Python >= 3.10
  • A Dropscan personal access token

Installation

From a local clone:

python3 -m venv .venv
./.venv/bin/pip install .

Configuration

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Dropscan: common questions

Is Dropscan MCP server safe?
Mostly: it is graded B (78/100). Read the Dropscan safety report
How do I install Dropscan?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Dropscan need an API key?
Yes. The registry entry asks for DROPSCAN_API_TOKEN.
Is Dropscan maintained?
The last commit was 100 days ago (2026-07-27). The latest release is v0.1.1.
How does Dropscan compare with other MCP servers?
safety score 78/100 (higher than 57% of 48,255 servers); tools 21 (the typical server has 7); tools that change things 29% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

More from bitterdev →