updated 2026-10-16 16:07 UTC

Outlook MCP

Repository

MCP server for Microsoft Outlook personal accounts via Microsoft Graph API. 68 tools across 13 categories — mail, calendar, contacts, tasks, drafts, attachments, delta queries, digest, bulk read. Community project, not affiliated with Microsoft.

MCP Servers Python Listed MIT

Is Outlook MCP safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 5.1 / 10
Provenance None
Signed commits 47%
Last push yesterday
Advisories None known
Compare Outlook MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Outlook MCP scores 64.0/100 (Grade C), ranked #546 of 1378 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 5.1/10; 47% of recent commits are signed; no published advisory affects its latest release (outlook-graph-mcp); last pushed 2026-10-15. Every point is earned from checkable signals — never paid placement. How scoring works →

How Outlook MCP 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.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Outlook MCP and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Partly signed

    github.com/mpalermiti/outlook-mcp, MIT, last pushed 2026-10-15. 47% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 5.1/10 (scanned Oct 15, 2026). The checks that decide who can get a change released:

    • Code Review4
    • Branch Protection1
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies0
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 1
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 4
    Contributors 3
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 10
    Packaging -1
    Pinned-Dependencies 0
    SAST 0
    Security-Policy 10
    Signed-Releases -1
    Token-Permissions 0
    Vulnerabilities 10

  3. Published packages Linked, not attested

    Without a build attestation, nothing proves the published files were built from this repository.

  4. What you install today No known advisories

    Latest release checked: outlook-graph-mcp 1.25.1. No published advisory affects it (OSV, checked 2026-10-15).

Changes to this chain

  • 2026-08-28 OSSF Scorecard: 3.9/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues Outlook MCP’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How Outlook MCP compares in MCP Servers

  1. #305 IvanMurzak Unity MCP 64.2 +0.2
  2. #306 Sub Agents MCP 64.0 ±0
  3. #307 Outlook MCP 64.0 this agent
  4. #308 Maya MCP 64.0 ±0
  5. #309 Parallel Browser MCP 64.0 ±0

Bars show each HVTrust score; the tick marks Outlook MCP’s 64.0.

Where the 64.0 comes from

HVTrust dimensions vs the MCP Servers average

64.0 / 100 · 100.0% confidence

Outlook MCP MCP Servers average (781 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
8.7 / 25
1.8 below avg 10.5
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.7 below avg 13.5
Transparency50% declared license · 50% OSSF Scorecard
12.8 / 17
0.5 above avg 12.3
Maintenance60% last-push freshness · 40% commit activity
18.3 / 20
6.0 above avg 12.3
AdoptionLog-scaled stars · package downloads
7.4 / 20
in line with avg 7.4

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-15
Rank Moved
Rank rose 39 spots (#585 → #546)
2026-10-14
Rank Moved
Rank dropped 15 spots (#570 → #585)
2026-10-12
Rank Moved
Rank dropped 28 spots (#551 → #579)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.1/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.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Compare with another agent Get email alerts for Outlook MCP View MCP Servers Report missing data
59.4
Activity sub-score · out of 100
#307
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 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 →

Signals refreshed 2026-10-16 16:07 UTC · Repo last pushed yesterday

Rank Trend

2026-09-29 2026-10-16

Activity & Reach

Stars
40
Forks
11
Last Push
2026-10-15
yesterday
Commits (4 wk)
38
Downloads (7d)
427
pypi
HN mentions (30d)
—
Open Issues
9
Rank Change
=
was #546

Analysis

Activity Inputs

59.4 / 100
StarsRepository reach
9.7 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
19.8 / 25
CommunityFork signal
5.0 / 20

Common questions about Outlook MCP

Outlook MCP 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 Outlook MCP publish package provenance?
No published build provenance is currently detected for Outlook MCP. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Outlook MCP have an OpenSSF Scorecard?
Outlook MCP has an OpenSSF Scorecard score of 5.1/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 Outlook MCP actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Outlook MCP use?
Outlook MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Outlook MCP's commits signed?
47% of the last 100 commits to Outlook MCP 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
medium confidence
Implemented
Outlook MCP 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
How this surface has changed

Detected changes to Outlook MCP'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
Mcp Status Changed
Detected MCP server support changed: none → implemented

Maintain Outlook MCP?

For maintainers

HVTrust scores Outlook MCP 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 33Score 3HVTrust 3Listed 2Grade 2Scorecard 1Delisted 1MCP 1
2026-10-15
Rank Moved
Rank rose 39 spots (#585 → #546)
2026-10-14
Rank Moved
Rank dropped 15 spots (#570 → #585)
2026-10-12
Rank Moved
Rank dropped 28 spots (#551 → #579)
2026-10-11
Rank Moved
Rank dropped 18 spots (#533 → #551)
2026-10-09
Rank Moved
Rank dropped 23 spots (#513 → #536)
2026-10-06
Rank Moved
Rank rose 25 spots (#531 → #506)
2026-10-04
Rank Moved
Rank dropped 12 spots (#527 → #539)
2026-10-03
Rank Moved
Rank rose 37 spots (#564 → #527)
2026-10-02
Rank Moved
Rank dropped 15 spots (#549 → #564)
2026-10-01
Rank Moved
Rank rose 22 spots (#571 → #549)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Grade Changed
Trust grade D → C
2026-09-23
Rank Moved
Rank rose 248 spots (#818 → #570)
2026-09-23
HVTrust Changed
HVTrust up 33.5pts (28.5 → 62.0)
2026-09-22
Newly Listed
First tracked at rank #818
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-20
Rank Moved
Rank rose 39 spots (#607 → #568)
2026-09-19
Rank Moved
Rank dropped 15 spots (#592 → #607)
2026-09-17
Rank Moved
Rank rose 18 spots (#605 → #587)
2026-09-12
Rank Moved
Rank rose 13 spots (#611 → #598)
2026-09-10
Rank Moved
Rank rose 24 spots (#627 → #603)
2026-09-08
Rank Moved
Rank rose 31 spots (#650 → #619)
2026-09-07
Rank Moved
Rank dropped 19 spots (#631 → #650)
2026-09-06
Rank Moved
Rank dropped 17 spots (#614 → #631)
2026-09-05
Rank Moved
Rank rose 27 spots (#641 → #614)
2026-09-04
Rank Moved
Rank rose 51 spots (#692 → #641)
2026-09-04
Activity Score Changed
Activity score up 13pts (37 → 50)
2026-09-03
Grade Changed
Trust grade D → C
2026-09-03
Rank Moved
Rank rose 33 spots (#725 → #692)
2026-09-03
HVTrust Changed
HVTrust up 3.0pts (49.4 → 52.4)
2026-09-03
Activity Score Changed
Activity score up 6pts (31 → 37)
2026-09-02
Rank Moved
Rank dropped 34 spots (#691 → #725)
2026-09-01
Rank Moved
Rank dropped 23 spots (#668 → #691)
2026-08-31
Rank Moved
Rank dropped 43 spots (#625 → #668)
2026-08-30
Rank Moved
Rank dropped 14 spots (#611 → #625)
2026-08-29
Rank Moved
Rank dropped 40 spots (#571 → #611)
2026-08-28
Scorecard Added
OSSF Scorecard: 3.9/10
2026-08-28
Rank Moved
Rank rose 351 spots (#922 → #571)
2026-08-28
HVTrust Changed
HVTrust up 20.0pts (29.7 → 49.7)
2026-08-27
Rank Moved
Rank dropped 28 spots (#894 → #922)
2026-08-26
Rank Moved
Rank dropped 108 spots (#786 → #894)
2026-08-18
Rank Moved
Rank dropped 30 spots (#748 → #778)
2026-08-18
Activity Score Changed
Activity score down 10pts (42 → 32)
2026-08-16
Rank Moved
Rank dropped 15 spots (#726 → #741)
2026-08-10
Rank Moved
Rank dropped 39 spots (#686 → #725)
2026-08-08
Newly Listed
First tracked at rank #685
GitHub → PyPI: outlook-graph-mcp

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 64.0 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/outlook-mcp.svg)](https://hvtracker.net/agents/outlook-mcp)
HTML:
<a href="https://hvtracker.net/agents/outlook-mcp"><img src="https://hvtracker.net/badge/outlook-mcp.svg" alt="HVTrust"></a>

Other agents in MCP Servers

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