Is MCP Sap Docs safe to use?

MCP Sap Docs has an HVTrust score of 53.0/100 (Grade C), ranked #852 of 1325 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for MCP Sap Docs?

MCP Sap Docs scores 53.0/100 on HVTracker's evidence-weighted HVTrust scale. It has 232 GitHub stars and is categorized under MCP Servers.

MCP Sap Docs

marianfoo/mcp-sap-docs

MCP Servers TypeScript Listed Apache-2.0

Is MCP Sap Docs safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 4.2 / 10

Provenance None

Signed commits 43%

Last push 3d ago

Compare MCP Sap Docs

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: MCP Sap Docs scores 53.0/100 (Grade C), ranked #852 of 1325 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 4.2/10; 43% of recent commits are signed; last pushed 2026-09-23. Every point is earned from checkable signals — never paid placement. How scoring works →

How MCP Sap Docs compares in MCP Servers

#480 Elasticsearch MCP Server 53.1 +0.1
#481 NotebookLM MCP (PleasePrompto) 53.1 +0.1
#482 MCP Sap Docs 53.0 this agent
#483 Cucumberstudio MCP 53.0 ±0
#484 p6xer MCP Server 53.0 ±0

Bars show each HVTrust score; the tick marks MCP Sap Docs’s 53.0.

Where the 53.0 comes from

HVTrust dimensions vs the MCP Servers average

53.0 / 100 · 100.0% confidence

MCP Sap Docs MCP Servers average (775 agents)

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

7.4 / 25

2.9 below avg 10.3

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.6 below avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

12.1 / 17

in line with avg 12.2

Maintenance60% last-push freshness · 40% commit activity

16.0 / 20

3.9 above avg 12.1

AdoptionLog-scaled stars · package downloads

5.7 / 20

1.5 below avg 7.2

Quick Trust Read

What Would Improve It

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

Recent Changes

2026-09-25

Grade Changed

Trust grade D → C

2026-09-25

Rank Moved

Rank rose 376 spots (#1231 → #855)

2026-09-25

HVTrust Changed

HVTrust up 17.3pts (35.7 → 53.0)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 4.2/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 MCP Sap Docs View MCP Servers Report missing data

59.8

Activity sub-score · out of 100

#482

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 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 →

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars

232

Forks

Last Push

2026-09-23

3 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▲3

was #855

Analysis

Activity Inputs

59.8 / 100

StarsRepository reach

14.2 / 30

FreshnessLast push recency

24.6 / 25

ActivityRecent commits

13.0 / 25

CommunityFork signal

7.9 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

4.2 / 10

OpenSSF Scorecard · scanned Sep 24, 2026

Signed Commits

43%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 7

CII-Best-Practices 0

Code-Review 2

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 2

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 2

Common questions about MCP Sap Docs

Public trust evidence for MCP Sap Docs 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 MCP Sap Docs publish package provenance?

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

Does MCP Sap Docs have an OpenSSF Scorecard?

MCP Sap Docs has an OpenSSF Scorecard score of 4.2/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 MCP Sap Docs actively maintained?

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

What license does MCP Sap Docs use?

MCP Sap Docs ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are MCP Sap Docs's commits signed?

43% of the last 100 commits to MCP Sap Docs 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

MCP Sap Docs appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

low confidence

None detected

No clear third-party provider dependency detected.

Credential signal: API keys or service config markers documented.

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 MCP Sap Docs'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 MCP Sap Docs?

For maintainers

HVTrust scores MCP Sap Docs 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-25

Grade Changed

Trust grade D → C

2026-09-25

Rank Moved

Rank rose 376 spots (#1231 → #855)

2026-09-25

HVTrust Changed

HVTrust up 17.3pts (35.7 → 53.0)

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Rank Moved

Rank dropped 318 spots (#911 → #1229)

2026-09-23

HVTrust Changed

HVTrust up 9.1pts (26.6 → 35.7)

2026-09-22

Newly Listed

First tracked at rank #911

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-08

Rank Moved

Rank dropped 10 spots (#1238 → #1248)

2026-09-07

Rank Moved

Rank dropped 11 spots (#1227 → #1238)

2026-09-06

Rank Moved

Rank dropped 29 spots (#1198 → #1227)

2026-09-05

Rank Moved

Rank dropped 15 spots (#1183 → #1198)

2026-09-05

Activity Score Changed

Activity score up 5pts (50 → 56)

2026-09-04

Rank Moved

Rank dropped 19 spots (#1164 → #1183)

2026-09-03

Rank Moved

Rank dropped 32 spots (#1132 → #1164)

2026-09-02

Rank Moved

Rank dropped 40 spots (#1092 → #1132)

2026-09-01

Scorecard Added

OSSF Scorecard: 3.8/10

2026-09-01

Rank Moved

Rank rose 193 spots (#1285 → #1092)

2026-09-01

HVTrust Changed

HVTrust up 15.7pts (16.6 → 32.3)

2026-08-30

Rank Moved

Rank dropped 10 spots (#1271 → #1281)

2026-08-29

Rank Moved

Rank dropped 10 spots (#1261 → #1271)

2026-08-27

Rank Moved

Rank dropped 11 spots (#1241 → #1252)

2026-08-26

Rank Moved

Rank dropped 28 spots (#1213 → #1241)

2026-08-18

Rank Moved

Rank rose 14 spots (#1219 → #1205)

2026-08-16

Rank Moved

Rank dropped 26 spots (#1190 → #1216)

2026-08-10

Rank Moved

Rank dropped 70 spots (#1122 → #1192)

2026-08-08

Newly Listed

First tracked at rank #1108

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

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