M365 (robin-collins) MCP Server
m365-mcp
PyPI
v0.2.1
Published by robin-collins — 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.
Microsoft 365 MCP server for Outlook, Calendar, and OneDrive with multi-account support
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
low Shell/command execution in packaging/dev tooling (tests/conftest.py)MTC-SRC-002
In a packaging/dev/install script (shipped, but not the server runtime) (`tests/conftest.py:191`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: check_result = subprocess.run( ["sudo", "netstat", "-tunlp"], capture_o
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server tests/conftest.py
Tools 56
Each tool and what it can reach — statically extracted from the published source.
file_getingests untrusted inputaccount_authenticateno sensitive capabilityaccount_complete_authno sensitive capabilityaccount_listno sensitive capabilitycache_get_statsno sensitive capabilitycache_invalidateno sensitive capabilitycache_task_get_statusno sensitive capabilitycache_task_listno sensitive capabilitycache_warming_statusno sensitive capabilitycalendar_check_availabilityno sensitive capability
Show 46 more tools ↓
calendar_create_eventno sensitive capabilitycalendar_delete_eventno sensitive capabilitycalendar_get_eventno sensitive capabilitycalendar_list_eventsno sensitive capabilitycalendar_respond_eventno sensitive capabilitycalendar_update_eventno sensitive capabilitycontact_createno sensitive capabilitycontact_deleteno sensitive capabilitycontact_getno sensitive capabilitycontact_listno sensitive capabilitycontact_updateno sensitive capabilityemail_create_draftno sensitive capabilityemail_deleteno sensitive capabilityemail_getno sensitive capabilityemail_get_attachmentno sensitive capabilityemail_listno sensitive capabilityemail_moveno sensitive capabilityemail_replyno sensitive capabilityemail_sendno sensitive capabilityemail_updateno sensitive capabilityemailfolders_getno sensitive capabilityemailfolders_get_treeno sensitive capabilityemailfolders_listno sensitive capabilityemailrules_createno sensitive capabilityemailrules_deleteno sensitive capabilityemailrules_getno sensitive capabilityemailrules_listno sensitive capabilityemailrules_move_bottomno sensitive capabilityemailrules_move_downno sensitive capabilityemailrules_move_topno sensitive capabilityemailrules_move_upno sensitive capabilityemailrules_updateno sensitive capabilityfile_createno sensitive capabilityfile_deleteno sensitive capabilityfile_listno sensitive capabilityfile_updateno sensitive capabilityfolder_getno sensitive capabilityfolder_get_treeno sensitive capabilityfolder_listno sensitive capabilityreply_all_emailno sensitive capabilitysearch_contactsno sensitive capabilitysearch_emailsno sensitive capabilitysearch_eventsno sensitive capabilitysearch_filesno sensitive capabilitysearch_unifiedno sensitive capabilityserver_get_versionno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (56 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.2.1 latest |
A 96/100 | 1 | 1.13.0 | 2026-08-25 |
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 m365-mcp --online --registry pypiOther implementations of M365 3
Independent packages implementing the same tool, scanned with the same engine. Compare all 4 side by side →
Production-grade Microsoft 365 MCP server — email, calendar, contacts, OneDrive, Teams, tasks, and users via delegated OAuth
Microsoft 365 MCP Server - Natural language interfaces for Outlook emails, contacts, and calendars
MCP server implementation for Microsoft 365 via Microsoft Graph API
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.