Back to MCP Trust Indexm8ven
F
Warning
6/100
6 days ago

ms-365-mcp-server

A Model Context Protocol server that enables interaction with Microsoft 365 services (Excel, Calendar, Mail, OneDrive, Teams, etc.) through the Graph API, allowing AI assistants to manage Microsoft 365 resources via natural language.

→ softeria/ms-365-mcp-server· listed on modelscope

Warning. Serious findings were identified. Review the full report before connecting. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

softeria

Source: modelscope · also listed on npm, mcp.so

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

modelscopenpmmcp.so

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
⚠️
Known vulnerabilities in dependencies: 2 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
⚠️
Tests do not pass
Either the test suite is broken or the code regressed. Either way the published behaviour can’t be verified by the publisher’s own tests.
✅
9 tools verified — handlers match their declared behaviour
3 read-only tools verified — handlers contain no write/delete/exec
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
✅
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 2 credentials: MS365_MCP_CLIENT_SECRET, MS365_MCP_OAUTH_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies2 high2 low

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

highjs-yaml@4.1.0GHSA-52cp-r559-cp3m

js-yaml: YAML merge-key chains can force quadratic CPU consumption

highjs-yaml@4.1.0GHSA-5p4m-2wfm-xmqj

JS-YAML: Quadratic CPU consumption in !!omap resolution (3.x and 4.x) — CVE-2026-59870 fix not backported

lowjs-yaml@4.1.0GHSA-h67p-54hq-rp68

JS-YAML: Quadratic-complexity DoS in merge key handling via repeated aliases

lowjs-yaml@4.1.0GHSA-mh29-5h37-fv8m

js-yaml has prototype pollution in merge (<<)

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configENABLED_TOOLSFilter tools using a regex pattern (alternative to --enabled-tools flag)
configLOG_LEVELSet logging level (default: 'info')
configMS365_MCP_ALLOWED_REDIRECT_URIS
configMS365_MCP_ALLOWED_SCOPES
configMS365_MCP_ALLOW_PAGINATION
configMS365_MCP_ALLOW_UNAUTHENTICATED_DISCOVERY
configMS365_MCP_AUDIT_LOG
configMS365_MCP_BASE_URL
configMS365_MCP_BODY_FORMAThtml: Return email bodies as HTML instead of plain text (default: text)
configMS365_MCP_CLIENT_IDyour-azure-ad-app-client-id-here
🔐 secretMS365_MCP_CLIENT_SECRETyour-secret-here # Optional for public apps
configMS365_MCP_CLOUD_TYPEare read from it. Every other variable listed above must be set in your shell
configMS365_MCP_CORS_ORIGIN
configMS365_MCP_DISABLE_DCR
configMS365_MCP_EXPECTED_HOME_ACCOUNT_IDCLI values (--expected-username, --expected-home-account-id) take precedence over MS365_MCP_EXPECTED_USERNAME and .
configMS365_MCP_EXPECTED_USERNAMEwork@company.com npx @softeria/ms-365-mcp-server --login
configMS365_MCP_EXTRA_SCOPES
configMS365_MCP_FORCE_WORK_SCOPEStrue1: Backwards compatibility for MS365_MCP_ORG_MODE
configMS365_MCP_GRAPH_CIRCUIT_DISABLED
configMS365_MCP_KEYVAULT_URLAzure Key Vault URL for secrets management (see Azure Key Vault section)
configMS365_MCP_LOG_DIR
configMS365_MCP_MAX_TOPn>: Hard cap for Graph $top / top on list requests (positive integer). When the model passes a larger value, the server clamps it to n so responses stay smaller. Example: MS365_MCP_MAX_TOP=15
configMS365_MCP_MESSAGE_SIGNOFF_PREFIXtext>: Signoff prepended to outgoing messages so recipients can tell they were agent-sent, e.g. 🤖. Default: none. CLI equivalent: --message-signoff-prefix <text> (see Message Signoff below)
configMS365_MCP_MESSAGE_SIGNOFF_SUFFIXtext>: Signoff appended to outgoing messages. Default: none. CLI equivalent: --message-signoff-suffix <text>. --no-message-signoff disables both (see Message Signoff below)
🔐 secretMS365_MCP_OAUTH_TOKENyour_oauth_token npx @softeria/ms-365-mcp-server
configMS365_MCP_OBO
configMS365_MCP_ORG_MODEtrue1: Enable organization/work mode (alternative to --org-mode flag)
configMS365_MCP_OUTPUT_FORMATtoon npx @softeria/ms-365-mcp-server
configMS365_MCP_PUBLIC_URL
configMS365_MCP_RATE_LIMIT_DISABLEDtrue1: Disable per-IP rate limiting in HTTP mode (default: enabled — 30 req/min on /authorize, /token, /register; 120 req/min on /mcp)
configMS365_MCP_REDACT_PII
configMS365_MCP_REQUIRE_CONFIRM
configMS365_MCP_SELECTED_ACCOUNT_PATHCustom file path for selected account metadata (see Token Storage below)
configMS365_MCP_TENANT_IDthat is. Only MS365_MCP_CLIENT_ID, MS365_MCP_CLIENT_SECRET, and
configMS365_MCP_TOKEN_CACHE_PATHCustom file path for MSAL token cache (see Token Storage below)
configMS365_MCP_TRUST_PROXY_AUTH
configMS365_MCP_TRUST_PROXY_HOPS
configREAD_ONLYtrue1: Alternative to --read-only flag
configSILENTtrue1: Disable console output
configVITEST
configXDG_CONFIG_HOMELinux $/ms-365-mcp-server/ (or ~/.config/ms-365-mcp-server/)
// quality suggestions

Tool annotations

4/9 tools have annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

9/9 tools missing one or more hints — login (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); logout (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); verify-login (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +6 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool inputs are validated

6/9 tool handlers declare input schemas (67%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tests pass

npm test failed — tests do not pass

Make sure npm test runs cleanly. Common cause: missing build step or missing env vars.

Shell command execution

3 child_process/subprocess calls in production code — runs shell commands (bin/modules/generate-mcp-tools.mjs:17, bin/modules/generate-mcp-tools.mjs:64, test-calendar-fix.js:14)

Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.

Production dependencies are patched

0 critical, 2 high severity in production deps — js-yaml@4.1.0 (high), js-yaml@4.1.0 (high)

Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 6 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Verified](https://m8ven.ai/badge/mcp/softeria-ms-365-mcp-server-sylav3?variant=verified)](https://m8ven.ai/mcp/softeria-ms-365-mcp-server-sylav3)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: c5ad4875b7fea7717452cc4020c98792cc945684
code hash: 9f300af482787c44b686b1cdffb46f7a6b69431fa5a2c6e2145a0ea9dfc6ef50
verified: 8/13/2026, 8:43:25 PM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client