Name: Spacemail by NWD
Author: norwichwebsite

Spacemail by NWD MCP

Check, search, read and draft replies to Spacemail (Spaceship) emails, across several mailboxes.

Grade A Local · stdio API key 12 tools v1.0.1 MIT

No reviews yet by norwichwebsitenpm Runs on your machine, nothing hosted

93/100

trust score

tools declared

local

runs on your machine

—

downloads a day

What it does

Check, search, read and draft replies to Spacemail (Spaceship) emails, across several mailboxes.

Quickstart

# 1 — add it to Claude Code
claude mcp add --scope user --env 'SPACEMAIL_EMAIL=${SPACEMAIL_EMAIL}' --env 'SPACEMAIL_PASSWORD=${SPACEMAIL_PASSWORD}' --transport stdio spacemail-by-nwd-mcp '--' npx -y spacemail-mcp

# 2 — ask your agent for something these tools do
#   list_mailboxes, test_connection, check_inbox and 9 more

It needs SPACEMAIL_EMAIL, SPACEMAIL_PASSWORD: this reads them from your environment, so export them first.

Spacemail by NWD costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.

Publishernot claimed

norwichwebsite1 server

1 category

All 1 server

Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.

Installation

Where are you running it?

Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Spacemail by NWD as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.

Claude Codedeclared by this listing

This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. Claude Code reads SPACEMAIL_EMAIL (Your Spacemail address. For more mailboxes use SPACEMAIL_1_EMAIL, SPACEMAIL_2_EMAIL and so on), SPACEMAIL_PASSWORD (The mailbox password (not your Spaceship account password)) from your environment each time it starts the server, so the value stays out of its config: export them in your shell profile (macOS, Linux), or run setx SPACEMAIL_EMAIL …, setx SPACEMAIL_PASSWORD … and open a new terminal (Windows). The '--' is in quotes so that PowerShell passes it on.

claude mcp add --scope user --env 'SPACEMAIL_EMAIL=${SPACEMAIL_EMAIL}' --env 'SPACEMAIL_PASSWORD=${SPACEMAIL_PASSWORD}' --transport stdio spacemail-by-nwd-mcp '--' npx -y spacemail-mcp

Reconnect, or start a new session, and the tools appear in the model’s tool list.

Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.

What it asks of you

It reaches a system of yours, so it needs your own credential rather than the publisher’s: SPACEMAIL_EMAIL — Your Spacemail address. For more mailboxes use SPACEMAIL_1_EMAIL, SPACEMAIL_2_EMAIL and so on.; SPACEMAIL_PASSWORD — The mailbox password (not your Spaceship account password).. You set them in your own client’s config, on your machine — this marketplace never holds it.

What it writes

One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.

What you approve

12 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.

Tool surface

What the model actually sees. Descriptions are diffed on every release — see version history.

Only tools that write or reach the network

Read from its source code. A server that builds its tool list when it starts can list more tools than this.

Shows which Spacemail mailboxes are connected and what this extension is allowed to do. Doesn't contact the mail server.

No parameter schema on file.

Logs in to each configured mailbox to check the settings work, and reports inbox counts. Use when setting up or when something fails.

Parameter	Type	Required	Notes
account	string	no	Mailbox to test. Leave out to test all of them.

Quick look at what's arrived: lists recent inbox messages across all mailboxes (or one), newest first, with a short preview.

Parameter	Type	Required	Notes
account	string	no	Mailbox to check. Leave out (or use "all") to check every mailbox.
unread_only	boolean	no	Only show unread messages. Defaults to true.
since	string	no	Only messages received on or after this date: "today", "yesterday", "7d" or a date like 2026-11-01.
limit	integer	no	Maximum messages per mailbox. Defaults to 15.

Searches one mailbox folder by sender, recipient, subject, words in the message, date range or read status. Results are newest first.

Parameter	Type	Required	Notes
account	string	no	—
folder	string	no	Folder to look in. Defaults to the inbox. Accepts "inbox", "sent", "drafts", "trash", "spam", "archive" or an exact folder name from list_folders.
from	string	no	Sender name or address contains this text.
to	string	no	Recipient address contains this text.
subject	string	no	Subject contains this text.
text	string	no	Message body contains this text.
since	string	no	On or after this date: "today", "yesterday", "30d" or 2026-10-01.
before	string	no	Before this date (same formats as since).
unread_only	boolean	no	Only unread messages.
flagged_only	boolean	no	Only flagged/starred messages.
limit	integer	no	Maximum results. Defaults to 20.
include_previews	boolean	no	Include a short preview of each message. Turn off for faster large searches.

Opens one message and returns its full text, sender, recipients, date and attachment names. Doesn't mark it as read unless asked.

Parameter	Type	Required	Notes
account	string	no	—
folder	string	no	Folder to look in. Defaults to the inbox. Accepts "inbox", "sent", "drafts", "trash", "spam", "archive" or an exact folder name from list_folders.
id	integer	yes	The message id shown in search or inbox results (unique within its folder).
mark_as_read	boolean	no	Also mark the message as read. Defaults to false so the user still sees it as new.

Lists the folders in a mailbox with message and unread counts.

Parameter	Type	Required	Notes
account	string	no	—

Writes a new email and saves it to the mailbox's Drafts folder. Nothing is sent: the user reviews and sends it from Spacemail webmail or their mail app.

Parameter	Type	Required	Notes
account	string	no	—
to		yes	—
cc		yes	—
bcc		yes	—
subject	string	yes	Subject line.
body	string	yes	The message, as plain text. Include a sign-off if appropriate.

Writes a reply to a message and saves it to Drafts, correctly threaded (Re: subject, quoted original, reply headers). Nothing is sent.

Parameter	Type	Required	Notes
account	string	no	—
folder	string	no	Folder to look in. Defaults to the inbox. Accepts "inbox", "sent", "drafts", "trash", "spam", "archive" or an exact folder name from list_folders.
id	integer	yes	Id of the message being replied to.
body	string	yes	Your reply, as plain text. The original message is quoted underneath automatically.
reply_all	boolean	no	Also include everyone else who was on the original email.

Marks messages as read or unread, or flags/unflags them.

Parameter	Type	Required	Notes
account	string	no	—
folder	string	no	Folder to look in. Defaults to the inbox. Accepts "inbox", "sent", "drafts", "trash", "spam", "archive" or an exact folder name from list_folders.
ids	array	yes	Message ids from search or inbox results, all from the same folder.
action	string	yes	What to do to the messages.

Moves messages to another folder, e.g. "archive", "trash", "spam", "inbox" or a named folder.

Parameter	Type	Required	Notes
account	string	no	—
folder	string	no	Folder the messages are in now. Defaults to the inbox.
ids	array	yes	Message ids from search or inbox results, all from the same folder.
destination	string	yes	Where to move them: "archive", "trash", "spam", "inbox" or an exact folder name.

Sends a new email immediately from a Spacemail mailbox. Only use this when the user has clearly asked for the email to be sent now; otherwise use create_draft.

Parameter	Type	Required	Notes
account	string	no	—
to		yes	—
cc		yes	—
bcc		yes	—
subject	string	yes	Subject line.
body	string	yes	The message, as plain text.

Sends a threaded reply immediately. Only use this when the user has clearly asked for it to be sent now; otherwise use draft_reply.

Parameter	Type	Required	Notes
account	string	no	—
folder	string	no	Folder to look in. Defaults to the inbox. Accepts "inbox", "sent", "drafts", "trash", "spam", "archive" or an exact folder name from list_folders.
id	integer	yes	Id of the message being replied to.
body	string	yes	Your reply, as plain text. The original is quoted underneath automatically.
reply_all	boolean	no	Also include everyone else who was on the original email.

Free

$0 forever

Every tool, no call limit
No card, and mcprush charges nothing for it
Source published under MIT
Runs on your machine — nothing of it reaches our gateway
Nothing to cap, because mcprush bills nothing

Nothing here is billable: mcprush charges nothing to install Spacemail by NWD or to call it, at any volume.

ATrust score 93 / 100

Release 1.0.1 · scanned 3 Nov 2026

Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.

Threat score100

Client score93

Findings2 threat · 0 capability

Capabilityhigh

Coveragesource

Verificationrepo

Surface digest1f712e69425de87eaed17cbe35d9640e1b1eceb57a0b4720b88d556a2e46a100

Score vectorthreat 100 → client 93

Term	Level	What it prices	Points
capability-exposure	high	capability blast radius (high) — client exposure if the model is manipulated	−6
verification-discount	repo	publisher verification (public source) — no provenance, but the source is public and inspectable	−1
coverage-honesty	source	inspection depth (source) — how much of the target the scan could see	−0

score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.

What the scan could actually read

A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.

Tool surfacenot available

Implementation sourceread

Package metadataread

Live transportnot available

No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".

Capability — what it could do if the model were manipulated

Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. high is the level these add up to.

Tool	Capability tags	Why the tag was assigned
No per-tool rows for this release — see the note below.

can execute shell commands or code

Toxic-flow graph

The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.

The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.

Supply chain and provenance

Integrityfirst-seen

Surface digest1f712e69425de87e

Scanned2026-11-03

This is the first scan of this surface here, so there is nothing yet to compare it against.

Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.