Mail-MCP
NPM · @RIXTAY/MAIL-MCP
Personal Outlook.com / Hotmail inbox: read, search, file, delete, unsubscribe via Microsoft Graph.
Available components
Last scanned (19 hours ago)
Scores higher than 61% 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 Security99
- 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
- 12 of 46 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- 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 14 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1083 tokens (~120/item across 9 items; 9 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 Management50
- Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 +6
- Stability: unverified → 0.40 ▲ functional
- 2 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 1 Oct 26 57
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 16 Oct 2026 · Analysed npm/@rixtay/mail-mcp@0.1.2
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 46 packages
| Packages resolved | 46 |
|---|---|
| Stale | 12 |
| 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 →
mail_bulk_by_sender Bulk action by sender ~140
Move or delete EVERY message from a sender (exact address) in a folder (Inbox by default). Use `dryRun: true` first to learn how many messages match. Deletion goes to Deleted Items unless `permanent: true`.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | move = move to targetFolder; delete = delete |
| dryRun | boolean | – | true = count only, change nothing |
| folder | string | – | Source folder. Default: inbox |
| from | string | yes | Exact sender address |
| permanent | boolean | – | With action = delete: permanent deletion |
| targetFolder | string | – | Required when action = move |
| Name | Type | Req | Description |
|---|---|---|---|
| dryRun | boolean | yes | – |
| failed | array | yes | – |
| matched | number | yes | – |
| succeeded | number | yes | – |
No examples provided.
mail_create_folder Create folder ~98
Create an Outlook folder (at the root or under a parent). Idempotent: if a folder with the same name already exists it is returned without error. Example: { name: "Newsletters" } or { name: "2025", parent: "Invoices" }.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Name of the folder to create |
| parent | string | – | Parent folder (name, path or id). Root if omitted. |
| Name | Type | Req | Description |
|---|---|---|---|
| created | boolean | yes | – |
| folder | object | yes | – |
No examples provided.
mail_delete Delete messages ~100
Delete one or more messages (up to 500 ids). By default messages go to Deleted Items (recoverable with mail_search folder=deleteditems then mail_move; their id changes). `permanent: true` deletes irreversibly: only use it when the user explicitly asks for it.
| Name | Type | Req | Description |
|---|---|---|---|
| ids | array | yes | Message ids (1 to 500) |
| permanent | boolean | – | true = permanent deletion (irreversible). Default: Deleted Items. |
| Name | Type | Req | Description |
|---|---|---|---|
| failed | array | yes | – |
| moved | array | – | – |
| succeeded | number | yes | – |
No examples provided.
mail_get_message Read a message ~76
Return the full content of one message (body converted to text, recipients, attachment flag, web link) plus the unsubscribe options found in its headers (https, mailto, one-click). The body is truncated at 25,000 characters.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Message id (from mail_search or mail_senders_summary) |
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | – |
| hasAttachments | boolean | yes | – |
| message | object | yes | – |
| to | array | yes | – |
| truncated | boolean | yes | – |
| unsubscribe | object | yes | – |
| webLink | string | – | – |
No examples provided.
mail_list_folders List folders ~79
List every folder of the Outlook.com mailbox with its path, total message count and unread count. Call it before filing messages to learn which folders exist. Other tools accept a folder by display name ("Invoices"), by path ("Archive/2024"), by well-known name (inbox, deleteditems, junkemail, archive) or by id.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| folders | array | yes | – |
No examples provided.
mail_move Move messages ~96
Move one or more messages (up to 500 ids) to a folder (name, path or id). Used for filing. NOTE: Outlook assigns a new id to every moved message; the `moved` result maps old id → new id. To move every message from a sender, prefer mail_bulk_by_sender.
| Name | Type | Req | Description |
|---|---|---|---|
| folder | string | yes | Destination folder |
| ids | array | yes | Message ids (1 to 500) |
| Name | Type | Req | Description |
|---|---|---|---|
| failed | array | yes | – |
| moved | array | – | – |
| succeeded | number | yes | – |
No examples provided.
mail_search Search messages ~240
List messages of a folder (Inbox by default), newest first, with filters: exact sender, date range, unread only. `query` runs a full-text search (subject, body, sender) and cannot be combined with the other filters. Returns a compact summary (id, sender, subject, date, preview); use mail_get_message for the full content. To page, pass `cursor` back verbatim. For a whole-mailbox view by sender, prefer mail_senders_summary.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Page cursor returned by a previous call |
| folder | string | – | Folder (name, path, well-known name or id). Default: inbox |
| from | string | – | Exact sender address, e.g. news@example.com |
| limit | integer | – | Results per page (max 100) |
| query | string | – | Full-text search (simple KQL). Exclusive with from/since/until/unreadOnly. |
| since | string | – | Received on or after this date (ISO) |
| unreadOnly | boolean | – | Only unread messages |
| until | string | – | Received on or before this date (ISO) |
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | yes | – |
| items | array | yes | – |
| nextCursor | string | – | – |
No examples provided.
mail_senders_summary Summary by sender ~134
KEY TOOL FOR TRIAGE. Scans a whole folder (Inbox by default) and aggregates messages by sender: count, unread, latest message, and for the `top` senders the available unsubscribe method (oneClick / https / mailto). Sorted by volume. The scan is cached for the session. Follow up with mail_unsubscribe(lastMessageId) and mail_bulk_by_sender(address).
| Name | Type | Req | Description |
|---|---|---|---|
| folder | string | – | Folder to analyse. Default: inbox |
| since | string | – | Only count messages received since this date |
| top | integer | – | Number of senders to return (max 200) |
| Name | Type | Req | Description |
|---|---|---|---|
| scanned | number | yes | – |
| senders | array | yes | – |
| totalSenders | number | yes | – |
No examples provided.
mail_unsubscribe Unsubscribe ~120
Try to unsubscribe from the mailing list of a message, in order: (1) RFC 8058 one-click HTTPS POST, (2) automatic email to the List-Unsubscribe mailto address, (3) otherwise returns `method: "browser"` with the URL to open in a browser to finish manually, (4) `method: "none"` when no header exists. Deletes nothing. Preferably pass the `lastMessageId` returned by mail_senders_summary.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Id of a representative message of the newsletter |
| Name | Type | Req | Description |
|---|---|---|---|
| detail | string | yes | – |
| from | string | yes | – |
| mailto | string | – | – |
| method | string | yes | – |
| ok | boolean | yes | – |
| subject | string | yes | – |
| url | string | – | – |
No examples provided.
How do I install the Mail-MCP server?
Mail-MCP runs locally as an npm package, launched with npx -y @rixtay/mail-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 · @rixtay/mail-mcp
claude mcp add rixtayz-mail-mcp -- npx -y @rixtay/mail-mcp
What is the Mail-MCP server?
Mail-MCP is listed in the public MCP registry as io.github.Rixtayz/mail-mcp. Personal Outlook.com / Hotmail inbox: read, search, file, delete, unsubscribe via Microsoft Graph. This page covers its npm package (@rixtay/mail-mcp).
Is the Mail-MCP server safe to use?
Mail-MCP scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 16 October 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 Mail-MCP server expose?
Mail-MCP exposes 9 tools: mail_list_folders, mail_create_folder, mail_search, mail_get_message, mail_senders_summary, and 4 more. Their descriptions and schemas cost roughly 1,083 tokens of context every time the server is loaded.
Is the Mail-MCP server still maintained?
Mail-MCP is still listed as active in the MCP registry. We last reached this channel on 16 October 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 Mail-MCP server under?
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.