updated 2026-09-04 22:32 UTC

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 C Listed MIT
55.6/100
Rank #594 of 1320
Compare Microsoft 365 MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade C · 2/5 signals
Last push
2026-09-04 · 0d ago
Recent change
Rank +7

Is Microsoft 365 MCP Server safe? Microsoft 365 MCP Server scores 55.6/100 (Grade C), ranked #594 of 1320 tracked open-source AI agent projects, on evidence coverage C (2 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; last pushed 2026-09-04. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#277 Miro — 55.7 (C) → #278 MCPfinder - MCP Server Discovery — 55.7 (C) → #280 MaverickMCP — 55.5 (C) → #281 ArcGIS MCP Bridge — 55.5 (C) →

Quick Trust Read

What Would Improve It
Expose more independent signals, such as package metadata, provenance, or public usage evidence.
Recent Changes
2026-09-04
Rank Moved
Rank dropped 13 spots (#581 → #594)
2026-09-03
Grade Changed
Trust grade A → C
2026-09-03
Rank Moved
Rank dropped 539 spots (#42 → #581)
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.4
Activity sub-score · out of 100
#279
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 C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-09-04 22:32 UTC · Repo last pushed today

Rank Trend

2026-08-16 2026-09-04

Activity & Reach

Stars
950
Forks
365
Last Push
2026-09-04
today
Commits (4 wk)
30
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
2
Rank Change
▼13
was #581

Analysis

HVTrust Dimensions vs MCP Servers

55.6 / 100 · 67.0% confidence

Microsoft 365 MCP Server MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
19.5 / 25
9.9 above avg 9.6
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.5 above avg 11.8
Maintenance60% last-push freshness · 40% commit activity
18.0 / 20
5.8 above avg 12.2
AdoptionLog-scaled stars · package downloads
7.1 / 20
0.8 above avg 6.3

Activity Inputs

73.4 / 100
StarsRepository reach
17.9 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
18.6 / 25
CommunityFork signal
11.9 / 20

Supply Chain Trust

Package Provenance
Verified
npm attestation
OSSF Scorecard
5.6 / 10
OpenSSF Scorecard · scanned Aug 29, 2026
Signed Commits
100%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 3
CI-Tests 10
CII-Best-Practices 0
Code-Review 5
Contributors 10
Dangerous-Workflow 10
Dependency-Update-Tool 10
Fuzzing 0
License 10
Maintained 10
Packaging 10
Pinned-Dependencies 3
SAST 0
Security-Policy 4
Signed-Releases -1
Token-Permissions 0
Vulnerabilities 0

Is Microsoft 365 MCP Server safe?

Microsoft 365 MCP Server has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
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.
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
Rank 4HVTrust 2Grade 2Listed 1Scorecard 1
2026-09-04
Rank Moved
Rank dropped 13 spots (#581 → #594)
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
HVTrust 55.6 Grade C
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.3 · Raw JSON