Is Cli Microsoft365 MCP Server safe to use?

Cli Microsoft365 MCP Server has an HVTrust score of 23.0/100 (Grade D), ranked #926 of 1283 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 23.0/100 on HVTracker's evidence-weighted HVTrust scale. It has 124 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 D Listed MIT

23.0/100

Rank #926 of 1283

Compare Cli Microsoft365 MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade D · 1/5 signals

Last push

2026-08-03 · 9d ago

Recent change

Rank +1

Is Cli Microsoft365 MCP Server safe? Cli Microsoft365 MCP Server scores 23.0/100 (Grade D), ranked #926 of 1283 tracked open-source AI agent projects, on evidence coverage D (1 of 5 independent signal types). The public evidence: no package-provenance attestation found; no OSSF Scorecard result yet; 100% of recent commits are signed; last pushed 2026-08-03. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#463 ProductClank — 23.0 (D) → #464 XamlMcp — 23.0 (D) → #466 NotebookLM MCP — 23.0 (D) → #467 Prometheus MCP Server — 22.9 (D) →

Quick Trust Read

What Would Improve It

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

Recent Changes

2026-08-10

Rank Moved

Rank dropped 54 spots (#869 → #923)

2026-08-08

Newly Listed

First tracked at rank #859

Maintainer Checklist

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

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

53.7

Activity sub-score · out of 100

#465

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 D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage D is separate — it grades how many independent signal types back the score (1 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-08-11 2026-08-12

Activity & Reach

Stars

124

Forks

Last Push

2026-08-03

9 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

was #926

Analysis

HVTrust Dimensions vs MCP Servers

23.0 / 100 · 40.0% confidence

Cli Microsoft365 MCP Server MCP Servers average (761 agents)

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

5.0 / 25

in line with avg 5.0

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.5 below 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

13.1 / 20

0.7 above avg 12.4

AdoptionLog-scaled stars · package downloads

5.0 / 20

0.8 below avg 5.8

Activity Inputs

53.7 / 100

StarsRepository reach

12.6 / 30

FreshnessLast push recency

23.8 / 25

ActivityRecent commits

10.5 / 25

CommunityFork signal

6.7 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

—

Not available

Signed Commits

100%

of last 100 commits verified

Is Cli Microsoft365 MCP Server safe?

Public trust evidence for Cli Microsoft365 MCP Server is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.

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?

No OpenSSF Scorecard data is currently published for Cli Microsoft365 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 Cli Microsoft365 MCP Server actively maintained?

Maintained. Last push was 9 days ago.

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