updated 2026-09-26 06:32 UTC

SharePoint MCP Server

ravikant1918/sharepoint-mcp

Production-grade MCP Server for Microsoft SharePoint — give your AI agent (Claude, Cursor, Continue) live access to read, write, and manage SharePoint files and folders.

MCP Servers Python Listed MIT

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

OSSF Scorecard 3.6 / 10
Provenance Attested
Signed commits 26%
Last push 195d ago
Compare SharePoint MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: SharePoint MCP Server scores 54.0/100 (Grade C), ranked #821 of 1325 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 3.6/10; 26% of recent commits are signed; last pushed 2026-03-15. Every point is earned from checkable signals — never paid placement. How scoring works →

How SharePoint MCP Server compares in MCP Servers

  1. #460 SeedanceMCP 54.0 ±0
  2. #461 Stealth Browser MCP 54.0 ±0
  3. #462 SharePoint MCP Server 54.0 this agent
  4. #463 Genieacs MCP 53.9 −0.1
  5. #464 tdmcp — TouchDesigner MCP server 53.9 −0.1

Bars show each HVTrust score; the tick marks SharePoint MCP Server’s 54.0.

Where the 54.0 comes from

HVTrust dimensions vs the MCP Servers average

54.0 / 100 · 100.0% confidence

SharePoint MCP Server MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
13.3 / 25
3.0 above avg 10.3
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.6 above avg 13.4
Transparency50% declared license · 50% OSSF Scorecard
11.6 / 17
0.6 below avg 12.2
Maintenance60% last-push freshness · 40% commit activity
0 / 20
12.1 below avg 12.1
AdoptionLog-scaled stars · package downloads
5.1 / 20
2.1 below avg 7.2

Quick Trust Read

What Would Improve It
Increase the share of verified signed commits for clearer maintainer identity.
Recent Changes
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Provenance Added
Package provenance attestation detected
2026-09-23
Grade Changed
Trust grade D → C
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.6/10. Tighten the weakest checks to improve public safety evidence.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Refresh maintenance signals The repo was last pushed 195 days ago. Fresh activity helps separate stable projects from stale ones.
Compare with another agent Get email alerts for SharePoint MCP Server View MCP Servers Report missing data
10.0
Activity sub-score · out of 100
#462
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-09-26 06:32 UTC · Repo last pushed 195 days ago — may be stale

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars
12
Forks
4
Last Push
2026-03-15
195 days ago
Commits (4 wk)
0
Downloads (7d)
61
pypi
HN mentions (30d)
—
Open Issues
1
Rank Change
▲4
was #825

Analysis

Activity Inputs

10.0 / 100
StarsRepository reach
6.7 / 30
FreshnessLast push recency
0.0 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
3.3 / 20

Supply Chain Trust

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

Common questions about SharePoint MCP Server

Public trust evidence for SharePoint 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 SharePoint MCP Server publish package provenance?
Yes. SharePoint MCP Server's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does SharePoint MCP Server have an OpenSSF Scorecard?
SharePoint MCP Server has an OpenSSF Scorecard score of 3.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 SharePoint MCP Server actively maintained?
Stale. The repository has not been pushed to in 195 days. Consider whether the project is still being maintained.
What license does SharePoint MCP Server use?
SharePoint MCP Server ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are SharePoint MCP Server's commits signed?
26% of the last 100 commits to SharePoint 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
medium confidence
Implemented
SharePoint 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
How this surface has changed

Detected changes to SharePoint MCP Server'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-23
Provenance Added
Package provenance attestation detected

Maintain SharePoint MCP Server?

For maintainers

HVTrust scores SharePoint 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 23Listed 2HVTrust 2Grade 2Scorecard 1Delisted 1Provenance 1MCP 1
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Provenance Added
Package provenance attestation detected
2026-09-23
Grade Changed
Trust grade D → C
2026-09-23
Rank Moved
Rank rose 458 spots (#1276 → #818)
2026-09-23
HVTrust Changed
HVTrust up 39.9pts (14.1 → 54.0)
2026-09-22
Newly Listed
First tracked at rank #1276
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-13
Rank Moved
Rank dropped 12 spots (#806 → #818)
2026-09-11
Rank Moved
Rank dropped 15 spots (#784 → #799)
2026-09-09
Rank Moved
Rank dropped 15 spots (#765 → #780)
2026-09-07
Rank Moved
Rank dropped 39 spots (#717 → #756)
2026-09-06
Rank Moved
Rank dropped 28 spots (#689 → #717)
2026-09-05
Rank Moved
Rank dropped 79 spots (#610 → #689)
2026-09-04
Rank Moved
Rank dropped 17 spots (#593 → #610)
2026-09-03
Rank Moved
Rank dropped 39 spots (#554 → #593)
2026-09-02
Rank Moved
Rank dropped 19 spots (#535 → #554)
2026-09-01
Rank Moved
Rank dropped 10 spots (#525 → #535)
2026-08-31
Rank Moved
Rank dropped 32 spots (#493 → #525)
2026-08-29
Rank Moved
Rank dropped 23 spots (#475 → #498)
2026-08-27
Rank Moved
Rank dropped 13 spots (#454 → #467)
2026-08-26
Scorecard Added
OSSF Scorecard: 3.6/10
2026-08-26
Grade Changed
Trust grade D → C
2026-08-26
Rank Moved
Rank rose 29 spots (#483 → #454)
2026-08-26
HVTrust Changed
HVTrust up 7.6pts (48.2 → 55.8)
2026-08-24
Rank Moved
Rank dropped 16 spots (#467 → #483)
2026-08-22
Rank Moved
Rank rose 13 spots (#482 → #469)
2026-08-19
Rank Moved
Rank dropped 12 spots (#470 → #482)
2026-08-17
Rank Moved
Rank rose 12 spots (#482 → #470)
2026-08-16
Rank Moved
Rank dropped 10 spots (#472 → #482)
2026-08-13
Rank Moved
Rank dropped 15 spots (#455 → #470)
2026-08-12
Rank Moved
Rank rose 13 spots (#468 → #455)
2026-08-10
Rank Moved
Rank dropped 16 spots (#452 → #468)
2026-08-08
Newly Listed
First tracked at rank #447
GitHub → PyPI: sharepoint-mcp

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 54.0 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/sharepoint-mcp-server.svg)](https://hvtracker.net/agents/sharepoint-mcp-server)
HTML:
<a href="https://hvtracker.net/agents/sharepoint-mcp-server"><img src="https://hvtracker.net/badge/sharepoint-mcp-server.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.3 · Raw JSON