Is MCP Cn Commerce safe to use?

MCP Cn Commerce has an HVTrust score of 61.8/100 (Grade C), ranked #580 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 Cn Commerce?

MCP Cn Commerce scores 61.8/100 on HVTracker's evidence-weighted HVTrust scale. It has 66 GitHub stars and is categorized under MCP Servers.

MCP Cn Commerce

TonyWang-hub/mcp-cn-commerce

中国电商 MCP 连接器：8 个平台、155 个已注册工具。开源标准版，含能力矩阵与实际工程验收记录；真实商家联调状态逐项公开。Chinese commerce MCP connectors with documented capabilities and validation status.

MCP Servers Python Listed MIT

Is MCP Cn Commerce safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 5.2 / 10

Provenance None

Signed commits 28%

Last push 5d ago

Compare MCP Cn Commerce

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: MCP Cn Commerce scores 61.8/100 (Grade C), ranked #580 of 1325 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 5.2/10; 28% of recent commits are signed; last pushed 2026-09-21. Every point is earned from checkable signals — never paid placement. How scoring works →

How MCP Cn Commerce compares in MCP Servers

#328 Bagel 61.8 ±0
#329 Studio MCP 61.8 ±0
#330 MCP Cn Commerce 61.8 this agent
#331 Arxiv MCP Server 61.8 ±0
#332 Persistent Project Context for xAI Grok 61.7 −0.1

Bars show each HVTrust score; the tick marks MCP Cn Commerce’s 61.8.

Where the 61.8 comes from

HVTrust dimensions vs the MCP Servers average

61.8 / 100 · 100.0% confidence

MCP Cn Commerce MCP Servers average (775 agents)

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

7.9 / 25

2.4 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.9 / 17

0.7 above avg 12.2

Maintenance60% last-push freshness · 40% commit activity

18.4 / 20

6.3 above avg 12.1

AdoptionLog-scaled stars · package downloads

6.8 / 20

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

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-24

Rank Moved

Rank rose 53 spots (#623 → #570)

2026-09-23

Grade Changed

Trust grade D → C

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 5.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 Cn Commerce View MCP Servers Report missing data

61.8

Activity sub-score · out of 100

#330

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

Activity & Reach

Stars

Forks

Last Push

2026-09-21

5 days ago

Commits (4 wk)

Downloads (7d)

pypi

HN mentions (30d)

—

Open Issues

Rank Change

▼9

was #571

Analysis

Activity Inputs

61.8 / 100

StarsRepository reach

11.0 / 30

FreshnessLast push recency

24.3 / 25

ActivityRecent commits

21.1 / 25

CommunityFork signal

5.3 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

5.2 / 10

OpenSSF Scorecard · scanned Sep 21, 2026

Signed Commits

28%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 3

CI-Tests 10

CII-Best-Practices 0

Code-Review 0

Contributors 0

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging -1

Pinned-Dependencies 0

SAST 0

Security-Policy 10

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 10

Common questions about MCP Cn Commerce

MCP Cn Commerce 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 MCP Cn Commerce publish package provenance?

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

MCP Cn Commerce has an OpenSSF Scorecard score of 5.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 Cn Commerce actively maintained?

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

What license does MCP Cn Commerce use?

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

Are MCP Cn Commerce's commits signed?

28% of the last 100 commits to MCP Cn Commerce 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

MCP Cn Commerce 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

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 Cn Commerce'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

Maintain MCP Cn Commerce?

For maintainers

HVTrust scores MCP Cn Commerce 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 53 spots (#623 → #570)

2026-09-23

Grade Changed

Trust grade D → C

2026-09-23

Rank Moved

Rank rose 134 spots (#757 → #623)

2026-09-23

HVTrust Changed

HVTrust up 30.3pts (29.8 → 60.1)

2026-09-22

Newly Listed

First tracked at rank #757

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-12

Rank Moved

Rank rose 47 spots (#600 → #553)

2026-09-11

Rank Moved

Rank rose 65 spots (#665 → #600)

2026-09-11

Activity Score Changed

Activity score up 7pts (54 → 61)

2026-09-10

Rank Moved

Rank rose 81 spots (#746 → #665)

2026-09-09

Rank Moved

Rank dropped 10 spots (#736 → #746)

2026-09-07

Rank Moved

Rank dropped 13 spots (#714 → #727)

2026-09-05

Rank Moved

Rank dropped 73 spots (#632 → #705)

2026-09-04

Rank Moved

Rank dropped 23 spots (#609 → #632)

2026-09-03

Rank Moved

Rank dropped 35 spots (#574 → #609)

2026-09-02

Rank Moved

Rank dropped 22 spots (#552 → #574)

2026-09-01

Rank Moved

Rank dropped 14 spots (#538 → #552)

2026-08-29

Rank Moved

Rank dropped 22 spots (#506 → #528)

2026-08-27

Rank Moved

Rank dropped 13 spots (#487 → #500)

2026-08-26

Scorecard Added

OSSF Scorecard: 4.5/10

2026-08-26

Grade Changed

Trust grade D → C

2026-08-26

Rank Moved

Rank rose 281 spots (#768 → #487)

2026-08-26

HVTrust Changed

HVTrust up 23.1pts (31.1 → 54.2)

2026-08-16

Rank Moved

Rank dropped 16 spots (#759 → #775)

2026-08-10

Rank Moved

Rank dropped 39 spots (#712 → #751)

2026-08-08

Newly Listed

First tracked at rank #711

GitHub → PyPI: mcp-cn-commerce

Embed Badge Badge guide for maintainers →

For maintainers

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