Is Nanobanana MCP Server safe to use?

Nanobanana MCP Server has an HVTrust score of 33.7/100 (Grade D), ranked #1243 of 1328 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Nanobanana MCP Server?

Nanobanana MCP Server scores 33.7/100 on HVTracker's evidence-weighted HVTrust scale. It has 396 GitHub stars and is categorized under MCP Servers.

Nanobanana MCP Server

zhongweili/nanobanana-mcp-server

AI image generation MCP server powered by Google Gemini, with smart model selection and 4K output

MCP Servers Python Grade D Listed MIT

33.7/100

Rank #1243 of 1328

Compare Nanobanana MCP Server

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-18 · 113d ago

Recent change

Rank +7

Is Nanobanana MCP Server safe? Nanobanana MCP Server scores 33.7/100 (Grade D), ranked #1243 of 1328 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 1.4/10; 7% of recent commits are signed; last pushed 2026-05-18. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#740 Tomyud1 Godot MCP — 34.1 (D) → #741 MCP Interactive Terminal — 34.0 (D) → #743 Chrome MCP Server — 33.7 (D) → #744 MCP Explorium — 33.5 (D) →

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-09-08

Rank Moved

Rank dropped 12 spots (#1231 → #1243)

2026-09-07

Rank Moved

Rank dropped 12 spots (#1219 → #1231)

2026-09-06

Scorecard Added

OSSF Scorecard: 1.4/10

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 1.4/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.

Refresh maintenance signals The repo was last pushed 113 days ago. Fresh activity helps separate stable projects from stale ones.

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

34.5

Activity sub-score · out of 100

#742

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

Activity & Reach

Stars

396

Forks

117

Last Push

2026-05-18

113 days ago

Commits (4 wk)

Downloads (7d)

1,971

pypi

HN mentions (30d)

—

Open Issues

Rank Change

▼12

was #1231

Analysis

HVTrust Dimensions vs MCP Servers

33.7 / 100 · 100.0% confidence

Nanobanana MCP Server MCP Servers average (778 agents)

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

2.1 / 25

7.8 below avg 9.9

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.6 below avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

9.7 / 17

2.3 below avg 12.0

Maintenance60% last-push freshness · 40% commit activity

4.5 / 20

7.7 below avg 12.2

AdoptionLog-scaled stars · package downloads

10.6 / 20

3.7 above avg 6.9

Activity Inputs

34.5 / 100

StarsRepository reach

15.6 / 30

FreshnessLast push recency

9.3 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

9.6 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

1.4 / 10

OpenSSF Scorecard · scanned Sep 6, 2026

Signed Commits

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 0

CII-Best-Practices 0

Code-Review 0

Contributors 0

Dangerous-Workflow -1

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 0

Packaging -1

Pinned-Dependencies -1

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions -1

Vulnerabilities 0

Is Nanobanana MCP Server safe?

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

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

Does Nanobanana MCP Server have an OpenSSF Scorecard?

Nanobanana MCP Server has an OpenSSF Scorecard score of 1.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 Nanobanana MCP Server actively maintained?

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

What license does Nanobanana MCP Server use?

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

Are Nanobanana MCP Server's commits signed?

7% of the last 100 commits to Nanobanana MCP Server 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

Nanobanana MCP Server appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

1 detected

Public provider/service dependencies detected.

Google Gemini

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

Warning

1 package source mismatch detected

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 Nanobanana MCP Server'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-08-16

Activity Went Stale

No commits for 90 days

Maintain Nanobanana MCP Server?

For maintainers

HVTrust scores Nanobanana MCP Server 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-08

Rank Moved

Rank dropped 12 spots (#1231 → #1243)

2026-09-07

Rank Moved

Rank dropped 12 spots (#1219 → #1231)

2026-09-06

Scorecard Added

OSSF Scorecard: 1.4/10

2026-09-06

Rank Moved

Rank rose 87 spots (#1306 → #1219)

2026-09-06

HVTrust Changed

HVTrust up 14.5pts (19.3 → 33.8)

2026-09-03

Rank Moved

Rank dropped 15 spots (#1276 → #1291)

2026-09-02

Rank Moved

Rank dropped 18 spots (#1258 → #1276)

2026-09-01

Rank Moved

Rank dropped 17 spots (#1241 → #1258)

2026-08-31

Rank Moved

Rank dropped 25 spots (#1216 → #1241)

2026-08-30

Rank Moved

Rank dropped 17 spots (#1199 → #1216)

2026-08-29

Rank Moved

Rank dropped 24 spots (#1175 → #1199)

2026-08-28

Rank Moved

Rank dropped 18 spots (#1157 → #1175)

2026-08-27

Rank Moved

Rank dropped 14 spots (#1143 → #1157)

2026-08-26

Rank Moved

Rank dropped 58 spots (#1085 → #1143)

2026-08-25

Rank Moved

Rank dropped 11 spots (#1074 → #1085)

2026-08-16

Activity Went Stale

No commits for 90 days

2026-08-16

Rank Moved

Rank dropped 41 spots (#1028 → #1069)

2026-08-13

Rank Moved

Rank dropped 10 spots (#1020 → #1030)

2026-08-12

Rank Moved

Rank rose 16 spots (#1036 → #1020)

2026-08-10

Rank Moved

Rank dropped 59 spots (#969 → #1028)

2026-08-08

Newly Listed

First tracked at rank #965

GitHub → PyPI: nanobanana-mcp-server

Embed Badge Badge guide for maintainers →

For maintainers

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