Microsoft 365 Mail
NPM · @MINDSTONE/MCP-SERVER-MICROSOFT-MAIL · SCANNED AUG 4
Microsoft 365 Outlook mail via Graph: read, search, send, reply, forward, draft, move, delete.
Available components
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 →
Supply Chain Security83
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known medium-severity CVE affects hono 4.12.33, reached via @modelcontextprotocol/sdk > hono. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (105 of 109), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency84
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to mindstone/mcp-servers). View diagnostics → Pass
- License check failed: the license (FSL-1.1-MIT) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 5 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability45
- 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 949 tokens (~67/item across 14 items; 13 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @mindstone/mcp-server-microsoft-mail
claude mcp add mindstone-mcp-server-microsoft-mail -- npx -y @mindstone/mcp-server-microsoft-mail
codex mcp add mindstone-mcp-server-microsoft-mail -- npx -y @mindstone/mcp-server-microsoft-mail
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"mindstone-mcp-server-microsoft-mail": {
"type": "local",
"command": [
"npx",
"-y",
"@mindstone/mcp-server-microsoft-mail"
],
"enabled": true
}
}
} openclaw mcp add mindstone-mcp-server-microsoft-mail --command npx --arg -y --arg @mindstone/mcp-server-microsoft-mail
mcp_servers:
mindstone-mcp-server-microsoft-mail:
command: "npx"
args: ["-y", "@mindstone/mcp-server-microsoft-mail"] {
"mcpServers": {
"mindstone-mcp-server-microsoft-mail": {
"command": "npx",
"args": [
"-y",
"@mindstone/mcp-server-microsoft-mail"
]
}
}
} 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.
- 4 Aug 26 0
- CVE-2026-69207 affects this package: medium ▼ security
- Known CVEs: partial → fail ▼ security
- 2 Aug 26 +51
- Install scripts: unverified → pass ▲ security
- Provenance: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Malware scan: unverified → pass ▲ security
- The attested source repository moved: mindstone/mcp-servers security
- License: unverified → fail ▼ functional
- Dependency health: unverified → partial ▲ functional
- Stability: unverified → 0.20 ▲ functional
- Maintenance: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Schema quality: unverified → good ▲ functional
- Licence: FSL-1.1-MIT functional
- 1 Aug 26 +14
- Schema quality: 830 → 949 ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 0 ▲ functional
- Package version: 0.1.2 → 0.2.0 functional
- 31 Jul 26 −1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −40
- Malware scan: pass → unverified ▼ security
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- Package version: 0.1.2 → 0.2.0 functional
- 27 Jul 26 46
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 4 Aug 2026 · Analysed npm/@mindstone/[email protected]
Provenance verified
Ecosystem: npm · Outcome: verified
Reason: verified
- Source repo:
- mindstone/mcp-servers
- Certificate issuer:
- https://token.actions.githubusercontent.com
- Certificate SAN:
- https://github.com/mindstone/mcp-servers/.github/workflows/release.yml@refs/heads/main
- Rekor log index:
- 2284997606
- Predicate type:
- https://slsa.dev/provenance/v1
- Subject digest:
- sha512:0bd1f154b6a585dddef70c90f8f1da37f514b4cfcef1cd7f10896972638e7a06121a81e76d5e54d6e75367ad1aaef80374b01abd6200afc1db35cfb44
- Discovery method:
- attestation_endpoint
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-8j4g-w8fx-2239 | CVE-2026-69207 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L | yes |
Dependencies 105 packages
105 packages in the resolved dependency tree · 105 deprecated · 33 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
authenticate_microsoft_account ~94
Connect a Microsoft 365 account to enable email, calendar, files, and Teams access. Call this tool when: 1. Other Microsoft tools return authentication errors 2. The user asks to connect or set up Microsoft 365 This tool returns a structured auth_required response. The host will recognise it and dispatch the desktop OAuth flow. After the user completes sign-in, Microsoft 365 tools become available.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
compose_email ~114
Open an inline editable email compose form before sending. Use this when the user wants to write or send an email, so they can review and edit the draft first. Do NOT use when the user asks to save a draft (use create_draft). This tool does not send the email directly.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | Email body |
| cc | array | — | CC recipient(s) |
| subject | string | yes | Email subject |
| to | array | yes | Recipient email address(es), e.g. ["[email protected]"] |
No output schema declared.
No examples provided.
create_draft ~73
Create a new standalone draft email (saved but not sent). For replying to an existing thread, use create_reply_draft instead.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | — | Email body (HTML supported) |
| cc | — | — | CC recipient(s) |
| subject | string | — | Email subject |
| to | — | — | Recipient email address(es) |
No output schema declared.
No examples provided.
create_reply_draft ~92
Create a draft reply to an existing email, threaded in the same conversation. The draft is saved in Drafts and can be reviewed in Outlook before sending.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | — | Reply body (HTML supported). If omitted, creates a blank reply draft. |
| id | string | — | Original email message ID to reply to |
| replyAll | boolean | — | Reply to all recipients (default: false) |
No output schema declared.
No examples provided.
delete_email ~45
Delete or move an email to trash.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | — | Email message ID |
| permanent | boolean | — | Permanently delete (default: false, moves to Deleted Items) |
No output schema declared.
No examples provided.
forward_email ~49
Forward an email to other recipients.
| Name | Type | Req | Description |
|---|---|---|---|
| comment | string | — | Optional comment to add |
| id | string | — | Email message ID to forward |
| to | — | — | Recipient(s) to forward to |
No output schema declared.
No examples provided.
get_email ~28
Get full email content including body by message ID.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | — | Email message ID |
No output schema declared.
No examples provided.
list_emails ~122
List emails from inbox or a specific folder. Returns subject, sender, date, and preview.
| Name | Type | Req | Description |
|---|---|---|---|
| filter | string | — | OData filter expression (e.g., "isRead eq false") |
| folder | string | — | Well-known folder name (inbox, sentitems, drafts, deleteditems, junkemail, archive, outbox), display name (e.g. "Sent Items"), or folder ID from list_folders. Default: Inbox. |
| top | number | — | Number of emails to return (default: 25, max: 100) |
No output schema declared.
No examples provided.
list_folders ~52
List mail folders (Inbox, Sent, Drafts, etc.). Returns folder IDs that can be used with list_emails and move_email.
| Name | Type | Req | Description |
|---|---|---|---|
| includeHidden | boolean | — | Include hidden folders (default: false) |
No output schema declared.
No examples provided.
move_email ~68
Move an email to a different folder.
| Name | Type | Req | Description |
|---|---|---|---|
| destinationFolder | string | — | Well-known folder name (inbox, sentitems, drafts, deleteditems, junkemail, archive, outbox), display name, or folder ID from list_folders |
| id | string | — | Email message ID |
No output schema declared.
No examples provided.
reply_to_email ~54
Reply to an email message.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | — | Reply body (HTML supported) |
| id | string | — | Original email message ID |
| replyAll | boolean | — | Reply to all recipients (default: false) |
No output schema declared.
No examples provided.
search_emails ~52
Search emails using Microsoft Search query syntax.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | — | Search query (e.g., "from:john subject:meeting") |
| top | number | — | Number of results (default: 25) |
No output schema declared.
No examples provided.
send_email ~101
Send a new email message. "to" and "cc" accept a string or an array of strings. Prefer arrays for multiple recipients (e.g. ["[email protected]"]).
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | — | Email body (HTML supported) |
| cc | — | — | CC recipient(s) |
| importance | string | — | Email importance |
| subject | string | — | Email subject |
| to | — | — | Recipient email address(es). Use an array: ["[email protected]"] |
No output schema declared.
No examples provided.