Is Gemini Cloud Assist MCP safe to use?

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

What is the trust score for Gemini Cloud Assist MCP?

Gemini Cloud Assist MCP scores 55.9/100 on HVTracker's evidence-weighted HVTrust scale. It has 67 GitHub stars and is categorized under MCP Servers.

Gemini Cloud Assist MCP

GoogleCloudPlatform/gemini-cloud-assist-mcp

An MCP Server for Gemini Cloud Assist; provides tools to assist with your tasks on GCP

MCP Servers Listed Apache-2.0

Is Gemini Cloud Assist MCP safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 4.6 / 10

Provenance None

Signed commits 28%

Last push 9d ago

Compare Gemini Cloud Assist MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Gemini Cloud Assist MCP scores 55.9/100 (Grade C), ranked #757 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 4.6/10; 28% of recent commits are signed; last pushed 2026-09-18. Every point is earned from checkable signals — never paid placement. How scoring works →

How Gemini Cloud Assist MCP compares in MCP Servers

#420 Webull OpenAPI 56.0 +0.1
#421 Maven Tools MCP 55.9 ±0
#422 Gemini Cloud Assist MCP 55.9 this agent
#423 Paparats – Local Semantic Code Search MCP 55.8 −0.1
#424 Awesome Copilot MCP Server 55.7 −0.2

Bars show each HVTrust score; the tick marks Gemini Cloud Assist MCP’s 55.9.

Where the 55.9 comes from

HVTrust dimensions vs the MCP Servers average

55.9 / 100 · 100.0% confidence

Gemini Cloud Assist MCP MCP Servers average (775 agents)

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

7.2 / 25

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

in line with avg 12.2

Maintenance60% last-push freshness · 40% commit activity

12.6 / 20

0.6 above avg 12.0

AdoptionLog-scaled stars · package downloads

6.9 / 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-27

Rank Moved

Rank rose 17 spots (#774 → #757)

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Grade Changed

Trust grade D → C

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 4.6/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 Gemini Cloud Assist MCP View MCP Servers Report missing data

44.9

Activity sub-score · out of 100

#422

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

Activity & Reach

Stars

Forks

Last Push

2026-09-18

9 days ago

Commits (4 wk)

Downloads (7d)

npm

HN mentions (30d)

—

Open Issues

Rank Change

▲17

was #774

Analysis

Activity Inputs

44.9 / 100

StarsRepository reach

11.0 / 30

FreshnessLast push recency

23.8 / 25

ActivityRecent commits

3.8 / 25

CommunityFork signal

6.2 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

4.6 / 10

OpenSSF Scorecard · scanned Sep 25, 2026

Signed Commits

28%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 6

CI-Tests -1

CII-Best-Practices 0

Code-Review 0

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 0

Packaging -1

Pinned-Dependencies 4

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions 7

Vulnerabilities 10

Common questions about Gemini Cloud Assist MCP

Gemini Cloud Assist 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 Gemini Cloud Assist MCP publish package provenance?

No published build provenance is currently detected for Gemini Cloud Assist MCP. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does Gemini Cloud Assist MCP have an OpenSSF Scorecard?

Gemini Cloud Assist MCP has an OpenSSF Scorecard score of 4.6/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 Gemini Cloud Assist MCP actively maintained?

Maintained. Last push was 9 days ago.

What license does Gemini Cloud Assist MCP use?

Gemini Cloud Assist MCP ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Gemini Cloud Assist MCP's commits signed?

28% of the last 100 commits to Gemini Cloud Assist 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

Gemini Cloud Assist 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 Gemini Cloud Assist 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-20

Provider Removed

Runtime surface shrank — no longer detected: Google Gemini

2026-09-18

Activity Resumed

Activity resumed

2026-08-18

Activity Went Stale

No commits for 90 days

Maintain Gemini Cloud Assist MCP?

For maintainers

HVTrust scores Gemini Cloud Assist 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-27

Rank Moved

Rank rose 17 spots (#774 → #757)

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 220 spots (#987 → #767)

2026-09-23

HVTrust Changed

HVTrust up 30.2pts (25.2 → 55.4)

2026-09-22

Newly Listed

First tracked at rank #987

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-20

Provider Removed

Runtime surface shrank — no longer detected: Google Gemini

2026-09-19

Rank Moved

Rank dropped 22 spots (#727 → #749)

2026-09-18

Activity Resumed

Activity resumed

2026-09-18

Grade Changed

Trust grade D → C

2026-09-18

Rank Moved

Rank rose 281 spots (#1008 → #727)

2026-09-18

HVTrust Changed

HVTrust up 9.2pts (47.1 → 56.3)

2026-09-18

Activity Score Changed

Activity score up 20pts (25 → 46)

2026-09-17

Rank Moved

Rank dropped 11 spots (#997 → #1008)

2026-09-16

Rank Moved

Rank rose 10 spots (#1007 → #997)

2026-09-11

Rank Moved

Rank dropped 13 spots (#976 → #989)

2026-09-09

Rank Moved

Rank dropped 12 spots (#964 → #976)

2026-09-08

Rank Moved

Rank dropped 15 spots (#949 → #964)

2026-09-07

Rank Moved

Rank dropped 47 spots (#902 → #949)

2026-09-06

Rank Moved

Rank dropped 15 spots (#887 → #902)

2026-09-05

Rank Moved

Rank dropped 58 spots (#829 → #887)

2026-09-04

Rank Moved

Rank dropped 32 spots (#797 → #829)

2026-09-03

Rank Moved

Rank dropped 50 spots (#747 → #797)

2026-09-02

Rank Moved

Rank rose 342 spots (#1089 → #747)

2026-09-02

HVTrust Changed

HVTrust up 15.8pts (32.6 → 48.4)

2026-09-01

Rank Moved

Rank dropped 40 spots (#1049 → #1089)

2026-08-31

Rank Moved

Rank dropped 33 spots (#1016 → #1049)

2026-08-30

Rank Moved

Rank dropped 53 spots (#963 → #1016)

2026-08-29

Rank Moved

Rank dropped 47 spots (#916 → #963)

2026-08-28

Rank Moved

Rank dropped 35 spots (#881 → #916)

2026-08-27

Rank Moved

Rank dropped 28 spots (#853 → #881)

2026-08-26

Scorecard Added

OSSF Scorecard: 4.6/10

2026-08-26

Rank Moved

Rank rose 314 spots (#1167 → #853)

2026-08-26

HVTrust Changed

HVTrust up 14.7pts (18.2 → 32.9)

2026-08-18

Activity Went Stale

No commits for 90 days

2026-08-16

Rank Moved

Rank dropped 24 spots (#1137 → #1161)

2026-08-10

Rank Moved

Rank dropped 69 spots (#1064 → #1133)

2026-08-08

Newly Listed

First tracked at rank #1062

GitHub → npm: @google-cloud/gemini-cloud-assist-mcp

Embed Badge Badge guide for maintainers →

For maintainers

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