Is Microsoft 365 MCP Server safe to use?

Microsoft 365 MCP Server has an HVTrust score of 86.5/100 (Grade A), ranked #60 of 1343 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Microsoft 365 MCP Server?

Microsoft 365 MCP Server scores 86.5/100 on HVTracker's evidence-weighted HVTrust scale. It has 1.0k GitHub stars and is categorized under MCP Servers.

Microsoft 365 MCP Server

Repository

A Model Context Protocol (MCP) server for interacting with Microsoft 365 and Microsoft Office services through the Graph API

MCP Servers TypeScript Listed MIT

Is Microsoft 365 MCP Server safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 5.6 / 10

Provenance Attested

Signed commits 100%

Last push yesterday

Advisories None known

Compare Microsoft 365 MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Microsoft 365 MCP Server scores 86.5/100 (Grade A), ranked #60 of 1343 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 5.6/10; 100% of recent commits are signed; no published advisory affects its latest release (@softeria/ms-365-mcp-server); last pushed 2026-09-30. Every point is earned from checkable signals — never paid placement. How scoring works →

How Microsoft 365 MCP Server could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Raise the OSSF Scorecard from 5.6 to 9.0lowest checks: CII-Best-Practices 0, Fuzzing 0, SAST 0 +5.0 → 91.5 A · #4 of 778

Already done? Suggest a correction Add the trust badge

How Microsoft 365 MCP Server compares in MCP Servers

#18 KiCad MCP Pro 86.8 +0.3
#19 DaVinci Resolve MCP 86.5 ±0
#20 Microsoft 365 MCP Server 86.5 this agent
#21 UI5 MCP Server 86.3 −0.2
#22 Easyeda MCP Pro 86.2 −0.3

Bars show each HVTrust score; the tick marks Microsoft 365 MCP Server’s 86.5.

Where the 86.5 comes from

HVTrust dimensions vs the MCP Servers average

86.5 / 100 · 100.0% confidence

Microsoft 365 MCP Server MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

19.5 / 25

9.2 above avg 10.3

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

4.6 above avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

13.3 / 17

1.1 above avg 12.2

Maintenance60% last-push freshness · 40% commit activity

18.0 / 20

5.8 above avg 12.2

AdoptionLog-scaled stars · package downloads

13.4 / 20

6.1 above avg 7.3

Quick Trust Read

What Would Improve It

Improve adoption to lift the weakest part of the trust profile.

Recent Changes

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependency: OpenAI

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 5.6/10. Tighten the weakest checks to improve public safety evidence.

Compare with another agent Get email alerts for Microsoft 365 MCP Server View MCP Servers Report missing data

73.9

Activity sub-score · out of 100

#20

In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade A reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-09-29 2026-10-01

Activity & Reach

Stars

1.0k

Forks

387

Last Push

2026-09-30

yesterday

Commits (4 wk)

Downloads (7d)

46,935

npm

HN mentions (30d)

—

Open Issues

Rank Change

▼1

was #59

Analysis

Activity Inputs

73.9 / 100

StarsRepository reach

18.0 / 30

FreshnessLast push recency

24.9 / 25

ActivityRecent commits

18.9 / 25

CommunityFork signal

12.0 / 20

Supply Chain Trust

Package Provenance

Verified

npm attestation

OSSF Scorecard

5.6 / 10

OpenSSF Scorecard · scanned Sep 30, 2026

Signed Commits

100%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 3

CI-Tests 10

CII-Best-Practices 0

Code-Review 6

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 2

SAST 0

Security-Policy 4

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 0

Common questions about Microsoft 365 MCP Server

Public supply-chain signals for Microsoft 365 MCP Server are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Microsoft 365 MCP Server carries less obvious unverified-evidence risk than projects with thin signals.

Does Microsoft 365 MCP Server publish package provenance?

Yes. Microsoft 365 MCP Server's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.

Does Microsoft 365 MCP Server have an OpenSSF Scorecard?

Microsoft 365 MCP Server has an OpenSSF Scorecard score of 5.6/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.

Is Microsoft 365 MCP Server actively maintained?

Actively maintained. The repository was pushed to within the last 1 day(s).

What license does Microsoft 365 MCP Server use?

Microsoft 365 MCP Server ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Microsoft 365 MCP Server's commits signed?

100% of the last 100 commits to Microsoft 365 MCP Server are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface

Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support

high confidence

Implemented

Microsoft 365 MCP Server appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

1 detected

Public provider/service dependencies detected.

OpenAI

Credential signal: API keys or service config markers documented.

Tool / Plugin Surface

None detected

No clear plugin system or broad tool surface detected.

Detailed evidence is not shown in the public view.

Package Provenance Drift

high confidence

Match

Published package metadata matches the tracked repo

Detailed evidence is not shown in the public view.

MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live

How this surface has changed

Detected changes to Microsoft 365 MCP Server's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependency: OpenAI

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

Maintain Microsoft 365 MCP Server?

For maintainers

HVTrust scores Microsoft 365 MCP Server from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependency: OpenAI

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

2026-09-23

Grade Changed

Trust grade D → A

2026-09-23

Rank Moved

Rank rose 593 spots (#661 → #68)

2026-09-23

HVTrust Changed

HVTrust up 54.3pts (31.8 → 86.1)

2026-09-22

Newly Listed

First tracked at rank #661

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-05

Grade Changed

Trust grade C → A

2026-09-05

Rank Moved

Rank rose 548 spots (#599 → #51)

2026-09-05

HVTrust Changed

HVTrust up 30.9pts (55.6 → 86.5)

2026-09-04

Rank Moved

Rank dropped 18 spots (#581 → #599)

2026-09-03

Grade Changed

Trust grade A → C

2026-09-03

Rank Moved

Rank dropped 539 spots (#42 → #581)

2026-09-03

HVTrust Changed

HVTrust down 30.8pts (86.4 → 55.6)

2026-08-29

Scorecard Added

OSSF Scorecard: 5.6/10

2026-08-29

Grade Changed

Trust grade B → A

2026-08-29

Rank Moved

Rank rose 71 spots (#118 → #47)

2026-08-29

HVTrust Changed

HVTrust up 11.4pts (74.9 → 86.3)

2026-08-26

Rank Moved

Rank dropped 12 spots (#93 → #105)

2026-08-16

Newly Listed

First tracked at rank #90

GitHub → npm: @softeria/ms-365-mcp-server

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/microsoft-365-mcp-server.svg)](https://hvtracker.net/agents/microsoft-365-mcp-server)
            
HTML:
            <a href="https://hvtracker.net/agents/microsoft-365-mcp-server"><img src="https://hvtracker.net/badge/microsoft-365-mcp-server.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON