Is Sfcc Dev MCP safe to use?

Sfcc Dev MCP has an HVTrust score of 67.5/100 (Grade B), ranked #387 of 1325 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Sfcc Dev MCP?

Sfcc Dev MCP scores 67.5/100 on HVTracker's evidence-weighted HVTrust scale. It has 28 GitHub stars and is categorized under MCP Servers.

Sfcc Dev MCP

taurgis/sfcc-dev-mcp

Supercharge your Salesforce B2C Commerce Cloud development with AI-powered documentation access, real-time log analysis, and intelligent best practices guidance

MCP Servers TypeScript Listed MIT

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

OSSF Scorecard 3.7 / 10

Provenance Attested

Signed commits 17%

Last push 6d ago

Compare Sfcc Dev MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Sfcc Dev MCP scores 67.5/100 (Grade B), ranked #387 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.7/10; 17% of recent commits are signed; last pushed 2026-09-20. Every point is earned from checkable signals — never paid placement. How scoring works →

How Sfcc Dev MCP compares in MCP Servers

Bars show each HVTrust score; the tick marks Sfcc Dev MCP’s 67.5.

Where the 67.5 comes from

HVTrust dimensions vs the MCP Servers average

67.5 / 100 · 100.0% confidence

Sfcc Dev MCP MCP Servers average (775 agents)

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

13.0 / 25

2.7 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

11.6 / 20

in line with avg 12.1

AdoptionLog-scaled stars · package downloads

7.3 / 20

in line with 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-24

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-24

Rank Moved

Rank rose 63 spots (#448 → #385)

2026-09-23

Provenance Added

Package provenance attestation detected

Maintainer Checklist

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

Compare with another agent Get email alerts for Sfcc Dev MCP View MCP Servers Report missing data

37.8

Activity sub-score · out of 100

#229

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 B 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-08-11 2026-09-26

Activity & Reach

Stars

Forks

Last Push

2026-09-20

6 days ago

Commits (4 wk)

Downloads (7d)

731

npm

HN mentions (30d)

—

Open Issues

Rank Change

▲1

was #388

Analysis

Activity Inputs

37.8 / 100

StarsRepository reach

8.8 / 30

FreshnessLast push recency

24.2 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

4.8 / 20

Supply Chain Trust

Package Provenance

Verified

npm attestation

OSSF Scorecard

3.7 / 10

OpenSSF Scorecard · scanned Sep 21, 2026

Signed Commits

17%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 0

CII-Best-Practices 0

Code-Review 0

Contributors 3

Dangerous-Workflow 0

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 0

Packaging 10

Pinned-Dependencies 3

SAST 0

Security-Policy 10

Signed-Releases -1

Token-Permissions 9

Vulnerabilities 0

Common questions about Sfcc Dev MCP

Sfcc Dev 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 Sfcc Dev MCP publish package provenance?

Yes. Sfcc Dev MCP's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.

Does Sfcc Dev MCP have an OpenSSF Scorecard?

Sfcc Dev MCP has an OpenSSF Scorecard score of 3.7/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 Sfcc Dev MCP actively maintained?

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

What license does Sfcc Dev MCP use?

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

Are Sfcc Dev MCP's commits signed?

17% of the last 100 commits to Sfcc Dev 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

high confidence

Implemented

Sfcc Dev 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 Sfcc Dev 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-24

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

Maintain Sfcc Dev MCP?

For maintainers

HVTrust scores Sfcc Dev 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

2026-09-24

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-24

Rank Moved

Rank rose 63 spots (#448 → #385)

2026-09-23

Provenance Added

Package provenance attestation detected

2026-09-23

Grade Changed

Trust grade D → B

2026-09-23

Rank Moved

Rank rose 635 spots (#1083 → #448)

2026-09-23

HVTrust Changed

HVTrust up 43.1pts (22.6 → 65.7)

2026-09-22

Newly Listed

First tracked at rank #1083

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-20

Rank Moved

Rank rose 19 spots (#395 → #376)

2026-09-10

Rank Moved

Rank dropped 17 spots (#362 → #379)

2026-09-07

Rank Moved

Rank dropped 37 spots (#318 → #355)

2026-09-05

Rank Moved

Rank dropped 64 spots (#255 → #319)

2026-09-04

Rank Moved

Rank dropped 10 spots (#245 → #255)

2026-09-03

Grade Changed

Trust grade D → B

2026-09-03

Rank Moved

Rank rose 608 spots (#853 → #245)

2026-09-03

HVTrust Changed

HVTrust up 23.6pts (44.6 → 68.2)

2026-09-02

Rank Moved

Rank dropped 43 spots (#810 → #853)

2026-09-01

Rank Moved

Rank dropped 29 spots (#781 → #810)

2026-08-31

Rank Moved

Rank dropped 33 spots (#748 → #781)

2026-08-30

Rank Moved

Rank dropped 17 spots (#731 → #748)

2026-08-29

Rank Moved

Rank dropped 48 spots (#683 → #731)

2026-08-28

Scorecard Added

OSSF Scorecard: 3.7/10

2026-08-28

Rank Moved

Rank rose 92 spots (#775 → #683)

2026-08-28

HVTrust Changed

HVTrust up 5.2pts (39.3 → 44.5)

2026-08-27

Rank Moved

Rank dropped 25 spots (#750 → #775)

2026-08-26

Rank Moved

Rank dropped 100 spots (#650 → #750)

2026-08-16

Rank Moved

Rank dropped 11 spots (#640 → #651)

2026-08-10

Rank Moved

Rank dropped 22 spots (#608 → #630)

2026-08-08

Newly Listed

First tracked at rank #612

GitHub → npm: sfcc-dev-mcp

Embed Badge Badge guide for maintainers →

For maintainers

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