Is Gmc MCP safe to use?

Gmc MCP has an HVTrust score of 50.5/100 (Grade C), ranked #451 of 1283 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 50.5/100 on HVTracker's evidence-weighted HVTrust scale. It has 12 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 — p

MCP Servers Python Grade C Listed MIT

50.5/100

Rank #451 of 1283

Compare Gmc MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade B · 3/5 signals

Last push

2026-05-02 · 102d ago

Recent change

Rank +1

Is Gmc MCP safe? Gmc MCP scores 50.5/100 (Grade C), ranked #451 of 1283 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; no OSSF Scorecard result yet; recent commits are unsigned; last pushed 2026-05-02. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#151 Komodo MCP Server — 50.8 (C) → #152 Browserbase MCP Server — 50.7 (C) → #154 Claude Context — 50.4 (C) → #155 FAOSTAT MCP — 50.4 (C) →

Quick Trust Read

What Would Improve It

Add or improve OSSF Scorecard coverage so safety checks are easier to verify.

Recent Changes

2026-08-10

Rank Moved

Rank dropped 14 spots (#436 → #450)

2026-08-08

Newly Listed

First tracked at rank #431

Maintainer Checklist

Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.

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

19.9

Activity sub-score · out of 100

#153

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-08-12

Activity & Reach

Stars

Forks

Last Push

2026-05-02

102 days ago

Commits (4 wk)

Downloads (7d)

499

pypi

HN mentions (30d)

—

Open Issues

Rank Change

▼1

was #450

Analysis

HVTrust Dimensions vs MCP Servers

50.5 / 100 · 100.0% confidence

Gmc MCP MCP Servers average (761 agents)

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

7.5 / 25

2.5 above avg 5.0

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

4.7 above avg 13.3

Transparency50% declared license · 50% OSSF Scorecard

8.5 / 17

in line with avg 8.8

Maintenance60% last-push freshness · 40% commit activity

5.2 / 20

7.2 below avg 12.4

AdoptionLog-scaled stars · package downloads

6.3 / 20

0.5 above avg 5.8

Activity Inputs

19.9 / 100

StarsRepository reach

6.7 / 30

FreshnessLast push recency

10.8 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

2.2 / 20

Supply Chain Trust

Package Provenance

Verified

pypi attestation

OSSF Scorecard

—

Not available

Signed Commits

of last 100 commits verified

Is Gmc MCP safe?

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?

No OpenSSF Scorecard data is currently published for Gmc MCP. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.

Is Gmc MCP actively maintained?

Slowing down. Last push was 102 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

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-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)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON