Outlook (hamzashahbaz) MCP Server
@hamzashahbaz/outlook-mcp
npm
v0.1.0
Published by @hamzashahbaz — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.
Outlook email MCP server for Claude — 19 tools for reading, sending, and managing email via Microsoft Graph API
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 4 = 96. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −3 | capability blast radius (moderate) — client exposure if the model is manipulated |
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 1
medium Untrusted input can drive an external actionMTC-FLOW-005
Untrusted-input tools ([outlook_mark_all_read]) co-exist with external-action tools ([outlook_send_email]). A prompt injection could cause unwanted external actions, though no direct sensitive-data leak path was found.
Evidence: untrusted [outlook_mark_all_read] → sinks [outlook_send_email]
Fix: Require confirmation for state-changing/egress actions triggered after processing untrusted content.
Location: flow outlook_mark_all_read → outlook_send_email
Tools 19
Each tool and what it can reach — statically extracted from the published source.
outlook_mark_all_readingests untrusted inputoutlook_send_emailnetwork egressoutlook_bulk_move_by_searchno sensitive capabilityoutlook_bulk_move_by_senderno sensitive capabilityoutlook_create_draftno sensitive capabilityoutlook_create_folderno sensitive capabilityoutlook_delete_draftno sensitive capabilityoutlook_delete_messageno sensitive capabilityoutlook_empty_folderno sensitive capabilityoutlook_forwardno sensitive capability
Show 9 more tools ↓
outlook_get_messageno sensitive capabilityoutlook_list_foldersno sensitive capabilityoutlook_list_messagesno sensitive capabilityoutlook_move_messageno sensitive capabilityoutlook_replyno sensitive capabilityoutlook_search_messagesno sensitive capabilityoutlook_send_draftno sensitive capabilityoutlook_update_draftno sensitive capabilityoutlook_update_messageno sensitive capability
Toxic flows 1
Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).
What this scan could not see
- Tools were statically extracted from the published source (19 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 1
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.1.0 latest |
A 96/100 | 1 | 1.13.0 | 2026-09-07 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan @hamzashahbaz/outlook-mcp --onlineOther implementations of Outlook 8
Independent packages implementing the same tool, scanned with the same engine. Compare all 9 side by side →
Servidor MCP oficial da Expert Integrado para Microsoft 365 (Outlook + Calendário + OneDrive). Autenticação via Device Code Flow com app pré-registrado — nenhuma configuração no Azure necessária.
MCP server for AI agents to parse and process Outlook email files
MCP Server to integrate with outlook
MCP server for Microsoft Outlook integration to manage emails, calendar events, and contacts
MCP server for Outlook — enables AI assistants to access email, contacts, and calendars via win32com
A Model Context Protocol server that integrates with Microsoft Outlook through Microsoft Graph API, allowing Claude and other LLMs to check calendar events, schedule new ones, read emails, and send messages.
More in API Development
Adapters for the FrontMCP framework
Transcend MCP Server — Admin tools.
Transcend MCP Server — Assessments tools.
MCP Server for Bling
MCP Server for Blogger API
Official MCP server for Brilliant Directories — manage members, posts, leads, reviews, and more.