Is Microsoft 365 MCP Server safe to use?

Microsoft 365 MCP Server has an HVTrust score of 75.6/100 (Grade B), ranked #89 of 1308 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 75.6/100 on HVTracker's evidence-weighted HVTrust scale. It has 913 GitHub stars and is categorized under MCP Servers.

Microsoft 365 MCP Server

Softeria/ms-365-mcp-server

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

MCP Servers TypeScript Grade B Listed MIT

75.6/100

Rank #89 of 1308

Compare Microsoft 365 MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Strong public trust posture, backed by multiple independent signals.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade B · 3/5 signals

Last push

2026-08-13 · 4d ago

Recent change

New

Is Microsoft 365 MCP Server safe? Microsoft 365 MCP Server scores 75.6/100 (Grade B), ranked #89 of 1308 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; no OSSF Scorecard result yet; 100% of recent commits are signed; last pushed 2026-08-13. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#11 Ha MCP — 76.5 (B) → #12 Containers Kubernetes MCP Server — 75.9 (B) → #14 Polymarket Agent MCP — 75.0 (B) → #15 Bright Data MCP — 74.6 (B) →

Quick Trust Read

What Would Improve It

Add or improve OSSF Scorecard coverage so safety checks are easier to verify.

Recent Changes

2026-08-16

Newly Listed

First tracked at rank #90

Maintainer Checklist

Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.

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

74.7

Activity sub-score · out of 100

#13

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 B 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 →

Activity & Reach

Stars

913

Forks

355

Last Push

2026-08-13

4 days ago

Commits (4 wk)

Downloads (7d)

45,068

npm

HN mentions (30d)

—

Open Issues

Rank Change

▲1

was #90

Analysis

HVTrust Dimensions vs MCP Servers

75.6 / 100 · 100.0% confidence

Microsoft 365 MCP Server MCP Servers average (775 agents)

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

12.5 / 25

7.5 above avg 5.0

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

4.7 above avg 13.3

Transparency50% declared license · 50% OSSF Scorecard

8.5 / 17

in line with avg 8.8

Maintenance60% last-push freshness · 40% commit activity

18.3 / 20

5.9 above avg 12.4

AdoptionLog-scaled stars · package downloads

13.3 / 20

7.5 above avg 5.8

Activity Inputs

74.7 / 100

StarsRepository reach

17.8 / 30

FreshnessLast push recency

24.4 / 25

ActivityRecent commits

20.4 / 25

CommunityFork signal

11.9 / 20

Supply Chain Trust

Package Provenance

Verified

npm attestation

OSSF Scorecard

—

Not available

Signed Commits

100%

of last 100 commits verified

Is Microsoft 365 MCP Server safe?

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?

No OpenSSF Scorecard data is currently published for Microsoft 365 MCP Server. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.

Is Microsoft 365 MCP Server actively maintained?

Actively maintained. The repository was pushed to within the last 4 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

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-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)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON