Spacemail by NWD
NPM · SPACEMAIL-MCP · 2 COMPONENTS
Check, search, read and draft replies to Spacemail (Spaceship) emails, across several mailboxes.
Available components
Last scanned (13 hours ago)
Scores higher than 39% of npm servers
Category Communication
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 2 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability70
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1489 tokens (~148/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 2 Nov 26 55
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/spacemail-mcp@1.0.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_inbox Check inbox ~150
Quick look at what's arrived: lists recent inbox messages across all mailboxes (or one), newest first, with a short preview. Best tool for "has anything come in today?" or "any new emails in the support inbox?".
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | Mailbox to check. Leave out (or use "all") to check every mailbox. |
| limit | integer | – | Maximum messages per mailbox. Defaults to 15. |
| since | string | – | Only messages received on or after this date: "today", "yesterday", "7d" or a date like 2026-11-01. |
| unread_only | boolean | – | Only show unread messages. Defaults to true. |
No output schema declared.
No examples provided.
create_draft Create draft ~183
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.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | Which mailbox to use, by its name or email address. Configured: none configured yet. Required when more than one is set up. |
| bcc | array | – | Bcc email addresses, e.g. ["Jane Smith <jane@example.com>"]. |
| body | string | yes | The message, as plain text. Include a sign-off if appropriate. |
| cc | array | – | Cc email addresses, e.g. ["Jane Smith <jane@example.com>"]. |
| subject | string | yes | Subject line. |
| to | array | yes | Recipient email addresses, e.g. ["Jane Smith <jane@example.com>"]. |
No output schema declared.
No examples provided.
draft_reply Draft a reply ~173
Writes a reply to a message and saves it to Drafts, correctly threaded (Re: subject, quoted original, reply headers). Nothing is sent.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | Which mailbox to use, by its name or email address. Configured: none configured yet. Required when more than one is set up. |
| body | string | yes | Your reply, as plain text. The original message is quoted underneath automatically. |
| folder | string | – | 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. |
| reply_all | boolean | – | Also include everyone else who was on the original email. |
No output schema declared.
No examples provided.
list_folders List folders ~55
Lists the folders in a mailbox with message and unread counts.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | Which mailbox to use, by its name or email address. Configured: none configured yet. Required when more than one is set up. |
No output schema declared.
No examples provided.
list_mailboxes List Spacemail mailboxes ~33
Shows which Spacemail mailboxes are connected and what this extension is allowed to do. Doesn't contact the mail server.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
move_emails Move emails ~152
Moves messages to another folder, e.g. "archive", "trash", "spam", "inbox" or a named folder. Deleting means moving to Trash; this extension never permanently deletes anything.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | Which mailbox to use, by its name or email address. Configured: none configured yet. Required when more than one is set up. |
| destination | string | yes | Where to move them: "archive", "trash", "spam", "inbox" or an exact folder name. |
| folder | string | – | 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. |
No output schema declared.
No examples provided.
read_email Read email ~164
Opens one message and returns its full text, sender, recipients, date and attachment names. Doesn't mark it as read unless asked.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | Which mailbox to use, by its name or email address. Configured: none configured yet. Required when more than one is set up. |
| folder | string | – | 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 | – | Also mark the message as read. Defaults to false so the user still sees it as new. |
No output schema declared.
No examples provided.
search_emails Search emails ~275
Searches one mailbox folder by sender, recipient, subject, words in the message, date range or read status. Results are newest first.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | Which mailbox to use, by its name or email address. Configured: none configured yet. Required when more than one is set up. |
| before | string | – | Before this date (same formats as since). |
| flagged_only | boolean | – | Only flagged/starred messages. |
| folder | string | – | 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 | – | Sender name or address contains this text. |
| include_previews | boolean | – | Include a short preview of each message. Turn off for faster large searches. |
| limit | integer | – | Maximum results. Defaults to 20. |
| since | string | – | On or after this date: "today", "yesterday", "30d" or 2026-10-01. |
| subject | string | – | Subject contains this text. |
| text | string | – | Message body contains this text. |
| to | string | – | Recipient address contains this text. |
| unread_only | boolean | – | Only unread messages. |
No output schema declared.
No examples provided.
test_connection Test Spacemail connection ~53
Logs in to each configured mailbox to check the settings work, and reports inbox counts. Use when setting up or when something fails.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | Mailbox to test. Leave out to test all of them. |
No output schema declared.
No examples provided.
update_emails Mark or flag emails ~137
Marks messages as read or unread, or flags/unflags them.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | Which mailbox to use, by its name or email address. Configured: none configured yet. Required when more than one is set up. |
| action | string | yes | What to do to the messages. |
| folder | string | – | 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. |
No output schema declared.
No examples provided.
How do I install the Spacemail by NWD MCP server?
Spacemail by NWD runs locally as an npm package, launched with npx -y spacemail-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · spacemail-mcp
claude mcp add design-norwichwebsite-spacemail -- npx -y spacemail-mcp
What is the Spacemail by NWD MCP server?
Spacemail by NWD is an MCP server listed in the public MCP registry as design.norwichwebsite/spacemail. Check, search, read and draft replies to Spacemail (Spaceship) emails, across several mailboxes. This page covers its npm package (spacemail-mcp).
Is the Spacemail by NWD MCP server safe to use?
Spacemail by NWD scores 70 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Spacemail by NWD MCP server expose?
Spacemail by NWD exposes 10 tools: list_mailboxes, test_connection, check_inbox, search_emails, read_email, and 5 more. Their descriptions and schemas cost roughly 1,375 tokens of context every time the server is loaded.
Is the Spacemail by NWD MCP server still maintained?
Spacemail by NWD is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Spacemail by NWD MCP server under?
Spacemail by NWD declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the Spacemail by NWD MCP server?
VerifyMCP ran 15 checks on Spacemail by NWD, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about Spacemail by NWD: Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.