io.github.0xka13b/microsoft-outlook-mcp
NPM · MICROSOFT-OUTLOOK-MCP
Microsoft Outlook (mail) MCP server — read, search, and send email through Microsoft Graph.
Available components
Last scanned (22 hours ago)
Scores higher than 58% 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 Security80
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects @azure/msal-node 5.6.0, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 40 of 108 dependencies flagged as unhealthy. View diagnostics → Partial
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 148 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 992 tokens (~70/item across 14 items; 14 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 14 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
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 −1
- Stability: pass → 0.90 functional
- 28 Oct 26 0
- Stability: 0.97 → pass security
- 27 Oct 26 0
- Stability: pass → 0.97 functional
- 24 Oct 26 −6
- CVE-2026-109461 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 21 Oct 26 +1
- Stability: 0.97 → pass security
- 20 Oct 26 −1
- Stability: pass → 0.97 functional
- 17 Oct 26 +3
- Stability: 0.83 → pass security
- 15 Oct 26 −3
- Stability: pass → 0.80 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 4 Nov 2026 · Analysed npm/microsoft-outlook-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 →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-xcx6-jx8p-x3h5 | CVE-2026-109461 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 108 packages
| Packages resolved | 108 |
|---|---|
| Stale | 40 |
| 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 →
create_email_draft ~123
Create a new, standalone draft email that can be edited and sent later. Use this only for starting a fresh message — to draft a reply within an existing conversation thread, use create_reply_draft instead.
| Name | Type | Req | Description |
|---|---|---|---|
| attachments | array | – | File attachments |
| bcc | array | – | BCC recipients |
| body | string | yes | Email body |
| body_type | string | – | Body content type. Defaults to text. |
| cc | array | – | CC recipients |
| subject | string | yes | Email subject |
| to | array | yes | Recipient email addresses |
No output schema declared.
No examples provided.
create_reply_draft ~155
Draft a reply to an existing email, kept inside the original conversation thread. Produces an editable draft (in Drafts) that inherits the conversation, the 'RE:' subject, threading headers, and quoted history — review and send it later with send_email or via Outlook. Use this instead of create_email_draft whenever responding to a message.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | Your reply text, inserted above the quoted original message |
| cc | array | – | Additional CC recipients to add to the reply |
| email_id | string | yes | Message ID being replied to |
| reply_all | boolean | – | Reply to all recipients of the original (sender + to + cc) instead of just the sender. Defaults to false. |
No output schema declared.
No examples provided.
delete_email ~27
Permanently delete an email message.
| Name | Type | Req | Description |
|---|---|---|---|
| email_id | string | yes | Message ID to delete |
No output schema declared.
No examples provided.
get_attachment ~43
Get an email attachment's content (returned as base64 in contentBytes).
| Name | Type | Req | Description |
|---|---|---|---|
| attachment_id | string | yes | Attachment ID |
| email_id | string | yes | Message ID |
No output schema declared.
No examples provided.
get_email ~84
Get a single email message by ID with full body and headers.
| Name | Type | Req | Description |
|---|---|---|---|
| body_max_length | integer | – | Max characters of body content to return. Defaults to 50000. |
| email_id | string | yes | Message ID |
| include_attachments | boolean | – | Include attachment metadata. Defaults to true. |
| include_body | boolean | – | Include message body. Defaults to true. |
No output schema declared.
No examples provided.
list_emails ~86
List emails from a mailbox folder ordered by date descending.
| Name | Type | Req | Description |
|---|---|---|---|
| folder | string | – | Folder name: inbox, sent, drafts, deleted, junk, archive, or a folder ID. Defaults to inbox. |
| include_body | boolean | – | Include message body. Defaults to true. |
| limit | integer | – | Number of messages to return (1–100). Defaults to 10. |
No output schema declared.
No examples provided.
me ~21
Get the signed-in user's profile (id, displayName, mail).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
move_email ~56
Move an email to a different folder.
| Name | Type | Req | Description |
|---|---|---|---|
| destination_folder | string | yes | Destination folder name (inbox, sent, drafts, deleted, junk, archive) or folder ID |
| email_id | string | yes | Message ID to move |
No output schema declared.
No examples provided.
reply_all_email ~55
Reply to all recipients of an email.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | Reply body |
| body_type | string | – | Body content type. Defaults to text. |
| email_id | string | yes | Message ID to reply-all to |
No output schema declared.
No examples provided.
reply_to_email ~54
Reply to an email (sender only).
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | Reply body |
| body_type | string | – | Body content type. Defaults to text. |
| email_id | string | yes | Message ID to reply to |
No output schema declared.
No examples provided.
search_emails ~70
Search emails by keyword across all folders or within a specific folder (KQL syntax supported).
| Name | Type | Req | Description |
|---|---|---|---|
| folder | string | – | Limit search to this folder (inbox, sent, etc.) |
| limit | integer | – | Max results. Defaults to 50. |
| query | string | yes | Search query string |
No output schema declared.
No examples provided.
send_email ~85
Send an email immediately.
| Name | Type | Req | Description |
|---|---|---|---|
| attachments | array | – | File attachments |
| bcc | array | – | BCC recipients |
| body | string | yes | Email body |
| body_type | string | – | Body content type. Defaults to text. |
| cc | array | – | CC recipients |
| subject | string | yes | Email subject |
| to | array | yes | Recipient email addresses |
No output schema declared.
No examples provided.
unified_search ~75
Search across multiple Microsoft 365 content types (email, calendar events, files) in one query.
| Name | Type | Req | Description |
|---|---|---|---|
| entity_types | array | – | Entity types to search. Defaults to [message, event, driveItem]. |
| limit | integer | – | Max total results. Defaults to 50. |
| query | string | yes | Search query string |
No output schema declared.
No examples provided.
update_email ~58
Update email properties such as read status, categories, or flag.
| Name | Type | Req | Description |
|---|---|---|---|
| email_id | string | yes | Message ID to update |
| updates | object | yes | Properties to update, e.g. {"isRead": true, "categories": ["work"]} |
No output schema declared.
No examples provided.
How do I install the io.github.0xka13b/microsoft-outlook-mcp server?
io.github.0xka13b/microsoft-outlook-mcp runs locally as an npm package, launched with npx -y microsoft-outlook-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 · microsoft-outlook-mcp
claude mcp add 0xka13b-microsoft-outlook-mcp -- npx -y microsoft-outlook-mcp
What is the io.github.0xka13b/microsoft-outlook-mcp server?
io.github.0xka13b/microsoft-outlook-mcp is listed in the public MCP registry as io.github.0xka13b/microsoft-outlook-mcp. Microsoft Outlook (mail) MCP server, read, search, and send email through Microsoft Graph. This page covers its npm package (microsoft-outlook-mcp).
Is the io.github.0xka13b/microsoft-outlook-mcp server safe to use?
io.github.0xka13b/microsoft-outlook-mcp scores 78 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 4 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 io.github.0xka13b/microsoft-outlook-mcp server expose?
io.github.0xka13b/microsoft-outlook-mcp exposes 14 tools: me, list_emails, get_email, create_email_draft, create_reply_draft, and 9 more. Their descriptions and schemas cost roughly 992 tokens of context every time the server is loaded.
Is the io.github.0xka13b/microsoft-outlook-mcp server still maintained?
io.github.0xka13b/microsoft-outlook-mcp is still listed as active in the MCP registry. We last reached this channel on 4 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 io.github.0xka13b/microsoft-outlook-mcp server under?
io.github.0xka13b/microsoft-outlook-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.