updated 2026-10-16 20:06 UTC

Microsoft MCP Server for Enterprise

Repository by microsoft
MCP Servers Listed CC-BY-4.0

Is Microsoft MCP Server for Enterprise safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 5.0 / 10
Provenance None
Signed commits 50%
Last push 134d ago
Compare Microsoft MCP Server for Enterprise

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Microsoft MCP Server for Enterprise scores 41.8/100 (Grade D), ranked #1177 of 1378 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 5.0/10; 50% of recent commits are signed; last pushed 2026-06-04. Every point is earned from checkable signals — never paid placement. How scoring works →

How Microsoft MCP Server for Enterprise 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 Microsoft MCP Server for Enterprise and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Partly signed

    github.com/microsoft/EnterpriseMCP, CC-BY-4.0, last pushed 2026-06-04. 50% 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.0/10 (scanned Oct 16, 2026). The checks that decide who can get a change released:

    • Code Review9
    • Branch Protection6
    • Signed Releasesn/a
    • Dangerous Workflown/a
    • Token Permissionsn/a
    • Pinned Dependenciesn/a
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 6
    CI-Tests 0
    CII-Best-Practices 0
    Code-Review 9
    Contributors 6
    Dangerous-Workflow -1
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 0
    Packaging -1
    Pinned-Dependencies -1
    SAST 0
    Security-Policy 10
    Signed-Releases -1
    Token-Permissions -1
    Vulnerabilities 10

  3. Published packages None

    No registry package. Microsoft MCP Server for Enterprise is used from its repository, so what you run is whatever you check out: pin a release tag or commit.

Changes to this chain

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

Evidence behind this score

Coverage C: 2 of 5 independent evidence types found.

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

Verify this score yourself

Every build re-issues Microsoft MCP Server for Enterprise’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 Microsoft MCP Server for Enterprise compares in MCP Servers

  1. #677 Devcontainer MCP 42.1 +0.3
  2. #678 JobGPT - Job Search Automation & Auto Apply 41.9 +0.1
  3. #679 Microsoft MCP Server for Enterprise 41.8 this agent
  4. #680 Propresenter MCP 41.8 ±0
  5. #681 Nslookup MCP 41.6 −0.2

Bars show each HVTrust score; the tick marks Microsoft MCP Server for Enterprise’s 41.8.

Where the 41.8 comes from

HVTrust dimensions vs the MCP Servers average

41.8 / 100 · 100.0% confidence

Microsoft MCP Server for Enterprise MCP Servers average (781 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
8.8 / 25
1.7 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
3.1 / 20
9.2 below avg 12.3
AdoptionLog-scaled stars · package downloads
4.3 / 20
3.1 below 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-09
Rank Moved
Rank dropped 12 spots (#1134 → #1146)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Rank Moved
Rank dropped 358 spots (#736 → #1094)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.0/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.
Refresh maintenance signals The repo was last pushed 134 days ago. Fresh activity helps separate stable projects from stale ones.
Compare with another agent Get email alerts for Microsoft MCP Server for Enterprise View MCP Servers Report missing data
22.7
Activity sub-score · out of 100
#679
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 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-10-16 20:06 UTC · Repo last pushed 134 days ago

Rank Trend

2026-09-29 2026-10-16

Activity & Reach

Stars
58
Forks
15
Last Push
2026-06-04
134 days ago
Commits (4 wk)
0
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
3
Rank Change
▼1
was #1176

Analysis

Activity Inputs

22.7 / 100
StarsRepository reach
10.6 / 30
FreshnessLast push recency
6.4 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
5.6 / 20

Common questions about Microsoft MCP Server for Enterprise

Public trust evidence for Microsoft MCP Server for Enterprise 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 Microsoft MCP Server for Enterprise publish package provenance?
No published build provenance is currently detected for Microsoft MCP Server for Enterprise. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Microsoft MCP Server for Enterprise have an OpenSSF Scorecard?
Microsoft MCP Server for Enterprise has an OpenSSF Scorecard score of 5.0/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 MCP Server for Enterprise actively maintained?
Slowing down. Last push was 134 days ago — keep an eye on whether activity resumes.
What license does Microsoft MCP Server for Enterprise use?
Microsoft MCP Server for Enterprise ships under CC-BY-4.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Microsoft MCP Server for Enterprise's commits signed?
50% of the last 100 commits to Microsoft MCP Server for Enterprise 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
Microsoft MCP Server for Enterprise 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
N/A
No package source configured
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 Microsoft MCP Server for Enterprise'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
2026-09-02
Activity Went Stale
No commits for 90 days

Maintain Microsoft MCP Server for Enterprise?

For maintainers

HVTrust scores Microsoft MCP Server for Enterprise 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 20Listed 2HVTrust 2Scorecard 1Stale 1Delisted 1MCP 1
2026-10-09
Rank Moved
Rank dropped 12 spots (#1134 → #1146)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Rank Moved
Rank dropped 358 spots (#736 → #1094)
2026-09-23
HVTrust Changed
HVTrust up 13.1pts (30.1 → 43.2)
2026-09-22
Newly Listed
First tracked at rank #736
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-12
Rank Moved
Rank dropped 14 spots (#1064 → #1078)
2026-09-09
Rank Moved
Rank dropped 13 spots (#1045 → #1058)
2026-09-08
Rank Moved
Rank dropped 11 spots (#1034 → #1045)
2026-09-07
Rank Moved
Rank dropped 33 spots (#1001 → #1034)
2026-09-06
Rank Moved
Rank dropped 17 spots (#984 → #1001)
2026-09-05
Rank Moved
Rank dropped 51 spots (#933 → #984)
2026-09-04
Rank Moved
Rank dropped 30 spots (#903 → #933)
2026-09-03
Rank Moved
Rank dropped 48 spots (#855 → #903)
2026-09-02
Activity Went Stale
No commits for 90 days
2026-09-02
Rank Moved
Rank dropped 43 spots (#812 → #855)
2026-09-01
Rank Moved
Rank dropped 29 spots (#783 → #812)
2026-08-31
Rank Moved
Rank dropped 38 spots (#745 → #783)
2026-08-30
Rank Moved
Rank dropped 25 spots (#720 → #745)
2026-08-29
Rank Moved
Rank dropped 49 spots (#671 → #720)
2026-08-28
Scorecard Added
OSSF Scorecard: 5.0/10
2026-08-28
Rank Moved
Rank rose 545 spots (#1216 → #671)
2026-08-28
HVTrust Changed
HVTrust up 26.6pts (18.2 → 44.8)
2026-08-27
Rank Moved
Rank dropped 10 spots (#1206 → #1216)
2026-08-26
Rank Moved
Rank dropped 40 spots (#1166 → #1206)
2026-08-16
Rank Moved
Rank dropped 27 spots (#1135 → #1162)
2026-08-10
Rank Moved
Rank dropped 68 spots (#1063 → #1131)
2026-08-08
Newly Listed
First tracked at rank #1057
GitHub →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 41.8 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/microsoft-mcp-server-for-enterprise.svg)](https://hvtracker.net/agents/microsoft-mcp-server-for-enterprise)
HTML:
<a href="https://hvtracker.net/agents/microsoft-mcp-server-for-enterprise"><img src="https://hvtracker.net/badge/microsoft-mcp-server-for-enterprise.svg" alt="HVTrust"></a>

Other agents in MCP Servers

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