Gemini Cloud Assist MCP
An MCP Server for Gemini Cloud Assist; provides tools to assist with your tasks on GCP
Is Gemini Cloud Assist MCP safe? Promising trust profile, but some evidence still deserves review.
Compare Gemini Cloud Assist MCP
How does it stack up against its MCP Servers neighbours?
Pick any agent to compare →In detail: Gemini Cloud Assist MCP scores 57.3/100 (Grade C), ranked #757 of 1378 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; 25% of recent commits are signed; no published advisory affects its latest release (@google-cloud/gemini-cloud-assist-mcp); last pushed 2026-10-16. 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.
- Publish build provenance for its packagesnpm publish --provenance from CI +14.7 → 72.0 B · #187 of 781
- Raise the OSSF Scorecard from 4.7 to 9.0lowest checks: CII-Best-Practices 0, Code-Review 0, Dependency-Update-Tool 0 +9.0 → 66.3 B · #273 of 781
- Sign every commit25% signed today +3.8 → 61.1 C · #353 of 781
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.
-
Source Partly signed
github.com/GoogleCloudPlatform/gemini-cloud-assist-mcp, Apache-2.0, last pushed 2026-10-16. 25% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.
-
Review and release Mixed
OpenSSF Scorecard rates the repository's practices 4.7/10 (scanned Oct 3, 2026). The checks that decide who can get a change released:
- Code Review0
- Branch Protection6
- Signed Releasesn/a
- Dangerous Workflow10
- Token Permissions7
- Pinned Dependencies4
All 18 Scorecard checks
Binary-Artifacts 10Branch-Protection 6CI-Tests -1CII-Best-Practices 0Code-Review 0Contributors 10Dangerous-Workflow 10Dependency-Update-Tool 0Fuzzing 0License 10Maintained 1Packaging -1Pinned-Dependencies 4SAST 0Security-Policy 0Signed-Releases -1Token-Permissions 7Vulnerabilities 10 -
Published packages Linked, not attested
- npm @google-cloud/gemini-cloud-assist-mcp Source link points back to this repo No build attestation
Without a build attestation, nothing proves the published files were built from this repository.
-
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-10-16).
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.
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
- #407 OrangePro 57.4 +0.1
- #408 OpenSTAAD MCP Server 57.3 ±0
- #409 Gemini Cloud Assist MCP 57.3 this agent
- #410 OpenResearch MCP 57.3 ±0
- #411 OpenROAD MCP 57.2 −0.1
Bars show each HVTrust score; the tick marks Gemini Cloud Assist MCP’s 57.3.
Where the 57.3 comes from
HVTrust dimensions vs the MCP Servers average
57.3 / 100 · 100.0% confidenceGemini Cloud Assist MCP MCP Servers average (781 agents)
Quick Trust Read
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
Activity & Reach
Analysis
Activity Inputs
53.7 / 100Common questions about Gemini Cloud Assist MCP
Does Gemini Cloud Assist MCP publish package provenance?
Does Gemini Cloud Assist MCP have an OpenSSF Scorecard?
Is Gemini Cloud Assist MCP actively maintained?
What license does Gemini Cloud Assist MCP use?
Are Gemini Cloud Assist MCP's commits signed?
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
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 signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
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.
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.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/gemini-cloud-assist-mcp)
<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
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