Assistant Mail MCP
NPM · @ASSISTANTMAIL/ASSISTANTMAIL-MCP
Agent email with allowlist and consent via AssistantMail.
Available components
Last scanned (18 hours ago)
Scores higher than 83% 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 Security98
- 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
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to AssistantMail/assistantmail-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 57 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability62
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 868 tokens (~39/item across 22 items; 22 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
- Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 5 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "assistantmail_delete_mailbox" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 22 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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
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.
- 7 Nov 26 −3
- Stability: pass → 0.83 functional
- 1 Nov 26 +1
- Stability: 0.97 → pass security
- 30 Oct 26 −1
- Stability: pass → 0.93 functional
- 24 Oct 26 +1
- Stability: 0.97 → pass security
- 23 Oct 26 −1
- Stability: pass → 0.97 functional
- 17 Oct 26 +1
- Stability: 0.97 → pass security
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 +1
- Security disclosure: unverified → fail ▼ functional
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 7 Nov 2026 · Analysed npm/@assistantmail/assistantmail-mcp@1.3.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | AssistantMail/assistantmail-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/AssistantMail/assistantmail-mcp/.github/workflows/release.yml@refs/tags/v1.3.1 |
| Rekor log index | 2692895491 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:6be1353d45f0322c2577ac25987b7dfdf7654997e00e276e9c16d16d2dd26f0480e147a61fdd50829017e99219034bdd542aabac0c21f9e70515aec0c |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| 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 →
assistantmail_add_recipient ~37
Adds a recipient and sends a consent invitation when required.
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | – | – |
| string | yes | – |
No output schema declared.
No examples provided.
assistantmail_create_mailbox ~42
Creates a mailbox for the authenticated account.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | – |
| apiKey | string | – | – |
| displayName | string | – | – |
No output schema declared.
No examples provided.
assistantmail_delete_mailbox ~35
Deletes a mailbox and all associated messages.
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | – | – |
| mailboxId | string | yes | – |
No output schema declared.
No examples provided.
assistantmail_delete_messages ~54
Deletes messages from a mailbox by IDs or deletes all messages.
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | – | – |
| deleteAll | boolean | – | – |
| mailboxId | string | yes | – |
| messageIds | array | – | – |
No output schema declared.
No examples provided.
assistantmail_get_inbound_policy ~30
Gets inbound email policy settings for the authenticated account.
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | – | – |
No output schema declared.
No examples provided.
assistantmail_get_mailbox ~35
Gets mailbox metadata for a mailbox ID.
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | – | – |
| mailboxId | string | yes | – |
No output schema declared.
No examples provided.
assistantmail_get_me ~29
Gets account profile and tier metadata for the authenticated account.
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | – | – |
No output schema declared.
No examples provided.
assistantmail_get_message ~50
Gets a specific message for a mailbox, including hydrated text/html bodies when available.
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | – | – |
| mailboxId | string | yes | – |
| messageId | string | yes | – |
No output schema declared.
No examples provided.
assistantmail_get_message_reference ~44
Provides the AssistantMail REST endpoint for fetching a single message including its full body content.
| Name | Type | Req | Description |
|---|---|---|---|
| mailboxId | string | yes | – |
| messageId | string | yes | – |
No output schema declared.
No examples provided.
assistantmail_get_usage ~37
Gets daily and monthly send quota usage for a mailbox.
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | – | – |
| mailboxId | string | yes | – |
No output schema declared.
No examples provided.
assistantmail_get_usage_reference ~34
Provides the AssistantMail REST endpoint for checking send quota usage for a mailbox.
| Name | Type | Req | Description |
|---|---|---|---|
| mailboxId | string | yes | – |
No output schema declared.
No examples provided.
assistantmail_health ~19
Returns AssistantMail MCP server and API endpoint metadata.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
assistantmail_list_mailboxes ~28
Lists mailboxes accessible to the authenticated account.
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | – | – |
No output schema declared.
No examples provided.
assistantmail_list_messages ~49
Lists inbound and outbound messages for a mailbox.
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | – | – |
| limit | integer | – | – |
| mailboxId | string | yes | – |
| since | string | – | – |
No output schema declared.
No examples provided.
assistantmail_list_messages_reference ~38
Provides the AssistantMail REST endpoint for listing messages (inbound and outbound) in a mailbox.
| Name | Type | Req | Description |
|---|---|---|---|
| mailboxId | string | yes | – |
No output schema declared.
No examples provided.
assistantmail_list_recipients ~30
Lists approved/pending recipients for the authenticated account.
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | – | – |
No output schema declared.
No examples provided.
assistantmail_remove_recipient ~35
Removes a recipient from the allowed recipient list.
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | – | – |
| string | yes | – |
No output schema declared.
No examples provided.
assistantmail_reply_message ~58
Replies to an existing message in a mailbox thread.
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | – | – |
| html | string | – | – |
| mailboxId | string | yes | – |
| messageId | string | yes | – |
| text | string | – | – |
No output schema declared.
No examples provided.
assistantmail_send_email ~63
Queues an outbound email for a mailbox.
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | – | – |
| html | string | – | – |
| mailboxId | string | yes | – |
| subject | string | yes | – |
| text | string | – | – |
| to | string | yes | – |
No output schema declared.
No examples provided.
assistantmail_send_email_reference ~33
Provides the AssistantMail REST endpoint and required headers for email send requests.
| Name | Type | Req | Description |
|---|---|---|---|
| mailboxId | string | yes | – |
No output schema declared.
No examples provided.
assistantmail_update_inbound_policy ~45
Updates inbound email policy for the authenticated account.
| Name | Type | Req | Description |
|---|---|---|---|
| allowedSenders | array | – | – |
| apiKey | string | – | – |
| policy | string | yes | – |
No output schema declared.
No examples provided.
assistantmail_update_mailbox ~43
Updates mailbox metadata (currently display name).
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | – | – |
| displayName | string | yes | – |
| mailboxId | string | yes | – |
No output schema declared.
No examples provided.
How do I install the Assistant Mail MCP server?
Assistant Mail MCP runs locally as an npm package, launched with npx -y @assistantmail/assistantmail-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 · @assistantmail/assistantmail-mcp
claude mcp add assistantmail-assistantmail-mcp -- npx -y @assistantmail/assistantmail-mcp
What is the Assistant Mail MCP server?
Assistant Mail MCP is listed in the public MCP registry as io.github.AssistantMail/assistantmail-mcp. Agent email with allowlist and consent via AssistantMail. This page covers its npm package (@assistantmail/assistantmail-mcp).
Is the Assistant Mail MCP server safe to use?
Assistant Mail MCP scores 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 7 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Assistant Mail MCP server expose?
Assistant Mail MCP exposes 22 tools: assistantmail_health, assistantmail_get_me, assistantmail_get_inbound_policy, assistantmail_update_inbound_policy, assistantmail_create_mailbox, and 17 more. Their descriptions and schemas cost roughly 868 tokens of context every time the server is loaded.
Is the Assistant Mail MCP server still maintained?
Assistant Mail MCP is still listed as active in the MCP registry. We last reached this channel on 7 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 Assistant Mail MCP server under?
Assistant Mail MCP 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 Assistant Mail MCP server?
VerifyMCP ran 16 checks on Assistant Mail MCP, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. 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.