Is MCP Abap Adt safe to use?

MCP Abap Adt has an HVTrust score of 53.9/100 (Grade C), ranked #883 of 1378 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for MCP Abap Adt?

MCP Abap Adt scores 53.9/100 on HVTracker's evidence-weighted HVTrust scale. It has 200 GitHub stars and is categorized under MCP Servers.

MCP Abap Adt

Repository by mario-andreschak

MCP Servers TypeScript Listed MIT

Is MCP Abap Adt safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 3.8 / 10

Provenance None

Signed commits 37%

Last push 32d ago

Advisories None known

Compare MCP Abap Adt

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: MCP Abap Adt scores 53.9/100 (Grade C), ranked #883 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 3.8/10; 37% of recent commits are signed; no published advisory affects its latest release (mcp-abap-adt); last pushed 2026-09-16. Every point is earned from checkable signals — never paid placement. How scoring works →

How MCP Abap Adt 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.

Publish build provenance for its packagesnpm publish --provenance from CI +14.7 → 68.6 B · #231 of 781
Raise the OSSF Scorecard from 3.8 to 9.0lowest checks: Branch-Protection 0, CI-Tests 0, CII-Best-Practices 0 +10.9 → 64.8 C · #292 of 781
Sign every commit37% signed today +3.2 → 57.1 C · #417 of 781

Already done? Suggest a correction Add the trust badge

Chain of custody

Scanners check what the code says. This traces who ships MCP Abap Adt 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.

Source Partly signed

github.com/mario-andreschak/mcp-abap-adt, MIT, last pushed 2026-09-16. 37% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.
Review and release Weak

OpenSSF Scorecard rates the repository's practices 3.8/10 (scanned Oct 16, 2026). The checks that decide who can get a change released:
- Code Review0
- Branch Protection0
- Signed Releasesn/a
- Dangerous Workflow10
- Token Permissions10
- Pinned Dependencies2
All 18 Scorecard checks

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 0

CII-Best-Practices 0

Code-Review 0

Contributors 0

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 9

Packaging -1

Pinned-Dependencies 2

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions 10

Vulnerabilities 0
Published packages Linked, not attested
- npm mcp-abap-adt Source link points back to this repo No build attestation
Without a build attestation, nothing proves the published files were built from this repository.
What you install today No known advisories

Latest release checked: mcp-abap-adt 1.2.0. No published advisory affects it (OSV, checked 2026-10-17).

Changes to this chain

2026-08-28 OSSF Scorecard: 2.3/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 MCP Abap Adt’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 MCP Abap Adt compares in MCP Servers

Bars show each HVTrust score; the tick marks MCP Abap Adt’s 53.9.

Where the 53.9 comes from

HVTrust dimensions vs the MCP Servers average

53.9 / 100 · 100.0% confidence

MCP Abap Adt MCP Servers average (781 agents)

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

6.6 / 25

4.0 below avg 10.6

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.8 below avg 13.6

Transparency50% declared license · 50% OSSF Scorecard

11.7 / 17

0.6 below avg 12.3

Maintenance60% last-push freshness · 40% commit activity

9.9 / 20

2.3 below avg 12.2

AdoptionLog-scaled stars · package downloads

8.9 / 20

1.5 above 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-17

Rank Moved

Rank dropped 50 spots (#832 → #882)

2026-10-13

Rank Moved

Rank dropped 18 spots (#802 → #820)

2026-10-06

Rank Moved

Rank dropped 27 spots (#754 → #781)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 3.8/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.

Refresh maintenance signals The repo was last pushed 32 days ago. Fresh activity helps separate stable projects from stale ones.

Compare with another agent Get email alerts for MCP Abap Adt View MCP Servers Report missing data

43.2

Activity sub-score · out of 100

#489

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 →

Rank Trend

2026-09-29 2026-10-17

Activity & Reach

Stars

200

Forks

Last Push

2026-09-16

32 days ago

Commits (4 wk)

Downloads (7d)

314

npm

HN mentions (30d)

—

Open Issues

Rank Change

▼1

was #882

Analysis

Activity Inputs

43.2 / 100

StarsRepository reach

13.8 / 30

FreshnessLast push recency

20.6 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

8.7 / 20

Common questions about MCP Abap Adt

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

No published build provenance is currently detected for MCP Abap Adt. 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 Abap Adt have an OpenSSF Scorecard?

MCP Abap Adt has an OpenSSF Scorecard score of 3.8/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 Abap Adt actively maintained?

Slowing down. Last push was 32 days ago — keep an eye on whether activity resumes.

What license does MCP Abap Adt use?

MCP Abap Adt ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are MCP Abap Adt's commits signed?

37% of the last 100 commits to MCP Abap Adt 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 Abap Adt 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 MCP Abap Adt'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 Abap Adt?

For maintainers

HVTrust scores MCP Abap Adt 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-10-17

Rank Moved

Rank dropped 50 spots (#832 → #882)

2026-10-13

Rank Moved

Rank dropped 18 spots (#802 → #820)

2026-10-06

Rank Moved

Rank dropped 27 spots (#754 → #781)

2026-10-02

Rank Moved

Rank dropped 53 spots (#690 → #743)

2026-09-30

Rank Moved

Rank dropped 21 spots (#665 → #686)

2026-09-25

Rank Moved

Rank rose 48 spots (#712 → #664)

2026-09-24

Rank Moved

Rank rose 112 spots (#824 → #712)

2026-09-24

HVTrust Changed

HVTrust up 3.6pts (53.7 → 57.3)

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 210 spots (#1034 → #824)

2026-09-23

HVTrust Changed

HVTrust up 29.6pts (24.1 → 53.7)

2026-09-22

Newly Listed

First tracked at rank #1034

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-20

Rank Moved

Rank dropped 12 spots (#811 → #823)

2026-09-17

Rank Moved

Rank dropped 68 spots (#749 → #817)

2026-09-16

Rank Moved

Rank rose 55 spots (#804 → #749)

2026-09-12

Rank Moved

Rank dropped 11 spots (#784 → #795)

2026-09-11

Rank Moved

Rank rose 27 spots (#811 → #784)

2026-09-09

Rank Moved

Rank dropped 13 spots (#797 → #810)

2026-09-07

Rank Moved

Rank dropped 48 spots (#742 → #790)

2026-09-06

Rank Moved

Rank dropped 11 spots (#731 → #742)

2026-09-05

Rank Moved

Rank dropped 65 spots (#666 → #731)

2026-09-04

Rank Moved

Rank dropped 25 spots (#641 → #666)

2026-09-03

Grade Changed

Trust grade D → C

2026-09-03

Rank Moved

Rank rose 402 spots (#1043 → #641)

2026-09-03

HVTrust Changed

HVTrust up 16.8pts (37.1 → 53.9)

2026-09-02

Activity Score Changed

Activity score up 8pts (49 → 57)

2026-09-01

Rank Moved

Rank dropped 38 spots (#1001 → #1039)

2026-08-31

Rank Moved

Rank dropped 35 spots (#966 → #1001)

2026-08-30

Rank Moved

Rank dropped 47 spots (#919 → #966)

2026-08-29

Rank Moved

Rank dropped 50 spots (#869 → #919)

2026-08-28

Scorecard Added

OSSF Scorecard: 2.3/10

2026-08-28

Rank Moved

Rank rose 228 spots (#1097 → #869)

2026-08-28

HVTrust Changed

HVTrust up 13.7pts (21.6 → 35.3)

2026-08-27

Rank Moved

Rank dropped 16 spots (#1081 → #1097)

2026-08-26

Rank Moved

Rank dropped 79 spots (#1002 → #1081)

2026-08-24

Rank Moved

Rank dropped 14 spots (#987 → #1001)

2026-08-22

Rank Moved

Rank rose 11 spots (#998 → #987)

2026-08-20

Rank Moved

Rank dropped 25 spots (#977 → #1002)

2026-08-19

Rank Moved

Rank dropped 14 spots (#963 → #977)

2026-08-17

Rank Moved

Rank rose 11 spots (#974 → #963)

2026-08-16

Rank Moved

Rank rose 14 spots (#988 → #974)

2026-08-16

Activity Score Changed

Activity score up 5pts (49 → 54)

2026-08-13

Rank Moved

Rank dropped 10 spots (#977 → #987)

2026-08-12

Rank Moved

Rank rose 14 spots (#991 → #977)

2026-08-10

Rank Moved

Rank dropped 54 spots (#934 → #988)

2026-08-08

Newly Listed

First tracked at rank #917

GitHub → npm: mcp-abap-adt

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/mcp-abap-adt.svg)](https://hvtracker.net/agents/mcp-abap-adt)
            
HTML:
            <a href="https://hvtracker.net/agents/mcp-abap-adt"><img src="https://hvtracker.net/badge/mcp-abap-adt.svg" alt="HVTrust"></a>

Other agents in MCP Servers

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

MCP Abap Adt

How MCP Abap Adt could raise its score

Chain of custody

Source Partly signed

Review and release Weak

Published packages Linked, not attested

What you install today No known advisories

Changes to this chain

Evidence behind this score

Verify this score yourself

What this score doesn’t check

How MCP Abap Adt compares in MCP Servers

Where the 53.9 comes from

HVTrust dimensions vs the MCP Servers average

Quick Trust Read

Rank Trend

Activity & Reach

Analysis

Activity Inputs

Common questions about MCP Abap Adt

AI agent surface

Maintain MCP Abap Adt?

Reputation Timeline

Embed Badge Badge guide for maintainers →

Other agents in MCP Servers