updated 2026-11-15 04:07 UTC

Gemini Cloud Assist MCP

Repository Website

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

MCP Servers Python Listed Apache-2.0

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

OSSF Scorecard 4.7 / 10
Provenance None
Signed commits 19%
Last push 2d ago
Advisories None known
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 60.1/100 (Grade C), ranked #711 of 1387 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.7/10; 19% of recent commits are signed; no published advisory affects its latest release (@google-cloud/gemini-cloud-assist-mcp); last pushed 2026-11-13. Every point is earned from checkable signals — never paid placement. How scoring works →

How Gemini Cloud Assist MCP could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Gemini Cloud Assist MCP and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Partly signed

    github.com/GoogleCloudPlatform/gemini-cloud-assist-mcp, Apache-2.0, last pushed 2026-11-13. 19% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 4.7/10 (scanned Nov 13, 2026). The checks that decide who can get a change released:

    • Code Review0
    • Branch Protection6
    • Signed Releasesn/a
    • Dangerous Workflown/a
    • Token Permissionsn/a
    • Pinned Dependenciesn/a
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 6
    CI-Tests -1
    CII-Best-Practices 0
    Code-Review 0
    Contributors 10
    Dangerous-Workflow -1
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 10
    Packaging -1
    Pinned-Dependencies -1
    SAST 0
    Security-Policy 0
    Signed-Releases -1
    Token-Permissions -1
    Vulnerabilities 10

  3. Published packages Linked, not attested

    Without a build attestation, nothing proves the published files were built from this repository.

  4. What you install today No known advisories

    Latest release checked: @google-cloud/gemini-cloud-assist-mcp 0.2.0. No published advisory affects it (OSV, checked 2026-11-15).

Changes to this chain

  • 2026-08-26 OSSF Scorecard: 4.6/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues Gemini Cloud Assist MCP’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How Gemini Cloud Assist MCP compares in MCP Servers

  1. #384 IDA Pro MCP 60.2 +0.1
  2. #385 Cloudflare MCP Server 60.1 ±0
  3. #386 Gemini Cloud Assist MCP 60.1 this agent
  4. #387 Word MCP Live 60.1 ±0
  5. #388 MCP ZAP Server 60.0 −0.1

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

Where the 60.1 comes from

HVTrust dimensions vs the MCP Servers average

60.1 / 100 · 100.0% confidence

Gemini Cloud Assist MCP MCP Servers average (779 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
6.8 / 25
4.1 below avg 10.9
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.9 below avg 13.7
Transparency50% declared license · 50% OSSF Scorecard
12.5 / 17
in line with avg 12.3
Maintenance60% last-push freshness · 40% commit activity
17.3 / 20
5.1 above avg 12.2
AdoptionLog-scaled stars · package downloads
7.5 / 20
in line with avg 7.6

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-11-13
Rank Moved
Rank dropped 52 spots (#651 → #703)
2026-11-11
Provider Added
Runtime surface grew — new detected provider dependency: Google Gemini
2026-11-11
Rank Moved
Rank dropped 20 spots (#634 → #654)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.7/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
View MCP Servers Report missing data
59.5
Activity sub-score · out of 100
#386
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 →

Signals refreshed 2026-11-15 04:07 UTC · Repo last pushed 2 days ago

Rank Trend

2026-09-29 2026-11-15

Activity & Reach

Stars
72
Forks
23
Last Push
2026-11-13
2 days ago
Commits (4 wk)
22
Downloads (7d)
185
npm
HN mentions (30d)
—
Open Issues
0
Rank Change
▼2
was #709

Analysis

Activity Inputs

59.5 / 100
StarsRepository reach
11.2 / 30
FreshnessLast push recency
24.7 / 25
ActivityRecent commits
17.0 / 25
CommunityFork signal
6.4 / 20

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.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 Gemini Cloud Assist MCP actively maintained?
Actively maintained. The repository was pushed to within the last 2 day(s).
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?
19% 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
high confidence
Implemented
Gemini Cloud Assist MCP appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
2 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration 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-11-11
Provider Added
Runtime surface grew — new detected provider dependency: Google Gemini
2026-10-18
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-10-18
Provider Added
Runtime surface grew — new detected provider dependency: Anthropic
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
Rank 36HVTrust 4Grade 2Surface 2Stale 1Scorecard 1Score 1Fresh 1Surface 1Delisted 1Listed 1MCP 1Surface 1
2026-11-13
Rank Moved
Rank dropped 52 spots (#651 → #703)
2026-11-11
Provider Added
Runtime surface grew — new detected provider dependency: Google Gemini
2026-11-11
Rank Moved
Rank dropped 20 spots (#634 → #654)
2026-11-01
Rank Moved
Rank rose 10 spots (#652 → #642)
2026-10-31
Rank Moved
Rank rose 67 spots (#719 → #652)
2026-10-30
Rank Moved
Rank rose 67 spots (#786 → #719)
2026-10-28
Rank Moved
Rank dropped 83 spots (#709 → #792)
2026-10-27
Rank Moved
Rank rose 41 spots (#750 → #709)
2026-10-25
Rank Moved
Rank rose 61 spots (#803 → #742)
2026-10-18
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-10-18
Provider Added
Runtime surface grew — new detected provider dependency: Anthropic
2026-10-18
Rank Moved
Rank dropped 22 spots (#750 → #772)
2026-10-09
Rank Moved
Rank dropped 14 spots (#746 → #760)
2026-10-08
Rank Moved
Rank rose 30 spots (#776 → #746)
2026-10-04
Rank Moved
Rank dropped 14 spots (#753 → #767)
2026-10-02
Rank Moved
Rank dropped 10 spots (#744 → #754)
2026-09-30
Rank Moved
Rank dropped 30 spots (#720 → #750)
2026-09-27
Rank Moved
Rank rose 21 spots (#774 → #753)
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
GitHub → Website → npm: @google-cloud/gemini-cloud-assist-mcp

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 60.1 Grade C
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.4 · Raw JSON