Is Cli Microsoft365 MCP Server safe to use?

Cli Microsoft365 MCP Server has an HVTrust score of 67.1/100 (Grade B), ranked #370 of 1328 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Cli Microsoft365 MCP Server?

Cli Microsoft365 MCP Server scores 67.1/100 on HVTracker's evidence-weighted HVTrust scale. It has 129 GitHub stars and is categorized under MCP Servers.

Cli Microsoft365 MCP Server

pnp/cli-microsoft365-mcp-server

Manage Microsoft 365 using MCP server

MCP Servers TypeScript Grade B Listed MIT

67.1/100

Rank #370 of 1328

Compare Cli Microsoft365 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 B · 3/5 signals

Last push

2026-09-07 · 1d ago

Recent change

Rank +7

Is Cli Microsoft365 MCP Server safe? Cli Microsoft365 MCP Server scores 67.1/100 (Grade B), ranked #370 of 1328 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 6.6/10; 100% of recent commits are signed; last pushed 2026-09-07. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#205 Jshookmcp — 67.4 (B) → #206 Terraform MCP Server — 67.1 (B) → #208 MCP Server for WinDbg Crash Analysis — 67.1 (B) → #209 MindsHub — 66.9 (B) →

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-09-06

Rank Moved

Rank dropped 20 spots (#337 → #357)

2026-09-05

Rank Moved

Rank dropped 66 spots (#271 → #337)

2026-09-04

Rank Moved

Rank dropped 11 spots (#260 → #271)

Maintainer Checklist

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

Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.

Compare with another agent Get email alerts for Cli Microsoft365 MCP Server View MCP Servers Report missing data

54.9

Activity sub-score · out of 100

#207

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 →

Rank Trend

2026-08-11 2026-09-08

Activity & Reach

Stars

129

Forks

Last Push

2026-09-07

yesterday

Commits (4 wk)

Downloads (7d)

1,768

npm

HN mentions (30d)

—

Open Issues

Rank Change

▼4

was #366

Analysis

HVTrust Dimensions vs MCP Servers

67.1 / 100 · 100.0% confidence

Cli Microsoft365 MCP Server MCP Servers average (778 agents)

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

13.2 / 25

3.3 above avg 9.9

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.6 below avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

14.1 / 17

2.1 above avg 12.0

Maintenance60% last-push freshness · 40% commit activity

13.6 / 20

1.4 above avg 12.2

AdoptionLog-scaled stars · package downloads

9.4 / 20

2.5 above avg 6.9

Activity Inputs

54.9 / 100

StarsRepository reach

12.7 / 30

FreshnessLast push recency

24.9 / 25

ActivityRecent commits

10.5 / 25

CommunityFork signal

6.7 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

6.6 / 10

OpenSSF Scorecard · scanned Sep 6, 2026

Signed Commits

100%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 6

CI-Tests 2

CII-Best-Practices 0

Code-Review 0

Contributors 3

Dangerous-Workflow -1

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging -1

Pinned-Dependencies -1

SAST 10

Security-Policy 10

Signed-Releases -1

Token-Permissions -1

Vulnerabilities 7

Is Cli Microsoft365 MCP Server safe?

Cli Microsoft365 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 Cli Microsoft365 MCP Server publish package provenance?

No published build provenance is currently detected for Cli Microsoft365 MCP Server. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does Cli Microsoft365 MCP Server have an OpenSSF Scorecard?

Cli Microsoft365 MCP Server has an OpenSSF Scorecard score of 6.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 Cli Microsoft365 MCP Server actively maintained?

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

What license does Cli Microsoft365 MCP Server use?

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

Are Cli Microsoft365 MCP Server's commits signed?

100% of the last 100 commits to Cli Microsoft365 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

Cli Microsoft365 MCP Server appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

None detected

No clear third-party provider dependency detected.

Credential signal: No explicit API-key/config marker detected.

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 Cli Microsoft365 MCP Server?

For maintainers

HVTrust scores Cli Microsoft365 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-06

Rank Moved

Rank dropped 20 spots (#337 → #357)

2026-09-05

Rank Moved

Rank dropped 66 spots (#271 → #337)

2026-09-04

Rank Moved

Rank dropped 11 spots (#260 → #271)

2026-09-03

Grade Changed

Trust grade D → B

2026-09-03

Rank Moved

Rank rose 579 spots (#839 → #260)

2026-09-03

HVTrust Changed

HVTrust up 21.9pts (45.3 → 67.2)

2026-09-02

Rank Moved

Rank dropped 43 spots (#796 → #839)

2026-09-01

Rank Moved

Rank dropped 32 spots (#764 → #796)

2026-08-31

Rank Moved

Rank dropped 34 spots (#730 → #764)

2026-08-30

Rank Moved

Rank rose 29 spots (#759 → #730)

2026-08-29

Rank Moved

Rank dropped 50 spots (#709 → #759)

2026-08-28

Rank Moved

Rank rose 32 spots (#741 → #709)

2026-08-28

Activity Score Changed

Activity score up 12pts (43 → 55)

2026-08-27

Rank Moved

Rank dropped 24 spots (#717 → #741)

2026-08-26

Scorecard Added

OSSF Scorecard: 5.3/10

2026-08-26

Rank Moved

Rank rose 248 spots (#965 → #717)

2026-08-26

HVTrust Changed

HVTrust up 18.3pts (22.3 → 40.6)

2026-08-24

Rank Moved

Rank dropped 19 spots (#948 → #967)

2026-08-21

Rank Moved

Rank rose 12 spots (#972 → #960)

2026-08-17

Rank Moved

Rank rose 27 spots (#985 → #958)

2026-08-16

Rank Moved

Rank dropped 28 spots (#957 → #985)

2026-08-13

Rank Moved

Rank dropped 10 spots (#948 → #958)

2026-08-12

Rank Moved

Rank dropped 22 spots (#926 → #948)

2026-08-12

Activity Score Changed

Activity score down 11pts (54 → 43)

2026-08-10

Rank Moved

Rank dropped 54 spots (#869 → #923)

2026-08-08

Newly Listed

First tracked at rank #859

GitHub → npm: @pnp/cli-microsoft365-mcp-server

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/cli-microsoft365-mcp-server.svg)](https://hvtracker.net/agents/cli-microsoft365-mcp-server)
            
HTML:
            <a href="https://hvtracker.net/agents/cli-microsoft365-mcp-server"><img src="https://hvtracker.net/badge/cli-microsoft365-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