Is Gmc MCP safe to use?

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

What is the trust score for Gmc MCP?

Gmc MCP scores 54.8/100 on HVTracker's evidence-weighted HVTrust scale. It has 15 GitHub stars and is categorized under MCP Servers.

Gmc MCP

kiwoongeom/gmc-mcp

The first free, open-source, self-hosted MCP server for Google Merchant Center (GMC). 126 tools over Merchant API v1 — products, inventory, reports, promotions, returns, account config, audit log + rollback, dry-run. Free alternative to paid SaaS (Adzviser, Catchr, Windsor.ai, Pipedream).

MCP Servers Python Listed MIT

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

OSSF Scorecard 3.4 / 10

Provenance Attested

Signed commits 0%

Last push 147d ago

Compare Gmc MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Gmc MCP scores 54.8/100 (Grade C), ranked #793 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.4/10; recent commits are unsigned; last pushed 2026-05-02. Every point is earned from checkable signals — never paid placement. How scoring works →

How Gmc MCP compares in MCP Servers

Bars show each HVTrust score; the tick marks Gmc MCP’s 54.8.

Where the 54.8 comes from

HVTrust dimensions vs the MCP Servers average

54.8 / 100 · 100.0% confidence

Gmc MCP MCP Servers average (775 agents)

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

11.8 / 25

1.5 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.4 / 17

0.8 below avg 12.2

Maintenance60% last-push freshness · 40% commit activity

2.2 / 20

9.9 below avg 12.1

AdoptionLog-scaled stars · package downloads

6.4 / 20

0.8 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.4/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 147 days ago. Fresh activity helps separate stable projects from stale ones.

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

14.7

Activity sub-score · out of 100

#441

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-05-02

147 days ago

Commits (4 wk)

Downloads (7d)

423

pypi

HN mentions (30d)

—

Open Issues

Rank Change

▼2

was #791

Analysis

Activity Inputs

14.7 / 100

StarsRepository reach

7.2 / 30

FreshnessLast push recency

4.6 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

2.8 / 20

Supply Chain Trust

Package Provenance

Verified

pypi attestation

OSSF Scorecard

3.4 / 10

OpenSSF Scorecard · scanned Sep 22, 2026

Signed Commits

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests -1

CII-Best-Practices 0

Code-Review 0

Contributors 0

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 0

Packaging 10

Pinned-Dependencies 0

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 10

Common questions about Gmc MCP

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

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

Does Gmc MCP have an OpenSSF Scorecard?

Gmc MCP has an OpenSSF Scorecard score of 3.4/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 Gmc MCP actively maintained?

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

What license does Gmc MCP use?

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

Are Gmc MCP's commits signed?

0% of the last 100 commits to Gmc 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

medium confidence

Implemented

Gmc MCP 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 Gmc 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-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

Maintain Gmc MCP?

For maintainers

HVTrust scores Gmc 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-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 475 spots (#1252 → #777)

2026-09-23

HVTrust Changed

HVTrust up 39.7pts (15.5 → 55.2)

2026-09-22

Newly Listed

First tracked at rank #1252

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-18

Rank Moved

Rank dropped 16 spots (#747 → #763)

2026-09-15

Rank Moved

Rank dropped 10 spots (#742 → #752)

2026-09-09

Rank Moved

Rank dropped 13 spots (#716 → #729)

2026-09-08

Rank Moved

Rank dropped 14 spots (#702 → #716)

2026-09-07

Rank Moved

Rank dropped 42 spots (#660 → #702)

2026-09-06

Rank Moved

Rank dropped 18 spots (#642 → #660)

2026-09-05

Rank Moved

Rank dropped 71 spots (#571 → #642)

2026-09-04

Rank Moved

Rank dropped 16 spots (#555 → #571)

2026-09-03

Rank Moved

Rank dropped 36 spots (#519 → #555)

2026-09-02

Rank Moved

Rank dropped 20 spots (#499 → #519)

2026-08-31

Rank Moved

Rank dropped 32 spots (#459 → #491)

2026-08-29

Scorecard Added

OSSF Scorecard: 3.4/10

2026-08-29

Grade Changed

Trust grade D → C

2026-08-29

Rank Moved

Rank rose 112 spots (#574 → #462)

2026-08-29

HVTrust Changed

HVTrust up 7.2pts (49.5 → 56.7)

2026-08-28

Rank Moved

Rank dropped 17 spots (#557 → #574)

2026-08-27

Rank Moved

Rank dropped 16 spots (#541 → #557)

2026-08-26

Rank Moved

Rank dropped 74 spots (#467 → #541)

2026-08-24

Rank Moved

Rank dropped 15 spots (#452 → #467)

2026-08-22

Rank Moved

Rank rose 14 spots (#467 → #453)

2026-08-21

Grade Changed

Trust grade C → D

2026-08-19

Rank Moved

Rank dropped 12 spots (#453 → #465)

2026-08-17

Rank Moved

Rank rose 11 spots (#464 → #453)

2026-08-13

Rank Moved

Rank dropped 15 spots (#437 → #452)

2026-08-12

Rank Moved

Rank rose 13 spots (#450 → #437)

2026-08-10

Rank Moved

Rank dropped 14 spots (#436 → #450)

2026-08-08

Newly Listed

First tracked at rank #431

GitHub → PyPI: gmc-mcp

Embed Badge Badge guide for maintainers →

For maintainers

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