updated 2026-11-11 00:08 UTC

Nanobanana MCP Server

Repository

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

MCP Servers Python Listed MIT

Is Nanobanana MCP Server safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 1.9 / 10
Provenance None
Signed commits 7%
Last push 22d ago
Compare Nanobanana MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Nanobanana MCP Server scores 41.3/100 (Grade D), ranked #1190 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 1.9/10; 7% of recent commits are signed; last pushed 2026-10-20. Every point is earned from checkable signals — never paid placement. How scoring works →

How Nanobanana MCP Server 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 Nanobanana MCP Server 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/zhongweili/nanobanana-mcp-server, MIT, last pushed 2026-10-20. 7% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Weak

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

    • Code Review0
    • Branch Protection0
    • Signed Releasesn/a
    • Dangerous Workflown/a
    • Token Permissionsn/a
    • Pinned Dependenciesn/a
    All 18 Scorecard checks
    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 4
    Packaging -1
    Pinned-Dependencies -1
    SAST 0
    Security-Policy 0
    Signed-Releases -1
    Token-Permissions -1
    Vulnerabilities 0

  3. Published packages Source mismatch

    • PyPI nanobanana-mcp-server Source link points to nano-banana/mcp-server, not this repo No build attestation

    A package whose source link names another repository may belong to a different project, or the project may have moved. HVTracker treats it as a mismatch until that is confirmed. Know which? Suggest a correction

Changes to this chain

  • 2026-09-23 Package-provenance drift warning: package metadata no longer clearly points at this repo
  • 2026-09-06 OSSF Scorecard: 1.4/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 Nanobanana MCP Server’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 Nanobanana MCP Server compares in MCP Servers

  1. #682 Claude Context 41.5 +0.2
  2. #683 Open Notebook MCP 41.3 ±0
  3. #684 Nanobanana MCP Server 41.3 this agent
  4. #685 Deployhq MCP Server 41.2 −0.1
  5. #686 Awesome Agent Skills MCP 41.1 −0.2

Bars show each HVTrust score; the tick marks Nanobanana MCP Server’s 41.3.

Where the 41.3 comes from

HVTrust dimensions vs the MCP Servers average

41.3 / 100 · 100.0% confidence

Nanobanana MCP Server MCP Servers average (779 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
2.7 / 25
8.1 below avg 10.8
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.9 below avg 13.7
Transparency50% declared license · 50% OSSF Scorecard
10.1 / 17
2.2 below avg 12.3
Maintenance60% last-push freshness · 40% commit activity
10.5 / 20
1.8 below avg 12.3
AdoptionLog-scaled stars · package downloads
11.2 / 20
3.6 above 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-01
Rank Moved
Rank dropped 21 spots (#1157 → #1178)
2026-10-28
Rank Moved
Rank rose 11 spots (#1165 → #1154)
2026-10-27
Rank Moved
Rank dropped 17 spots (#1148 → #1165)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 1.9/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
47.3
Activity sub-score · out of 100
#684
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 →

Signals refreshed 2026-11-11 00:08 UTC · Repo last pushed 22 days ago

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
404
Forks
114
Last Push
2026-10-20
22 days ago
Commits (4 wk)
0
Downloads (7d)
5,147
pypi
HN mentions (30d)
—
Open Issues
1
Rank Change
▼1
was #1189

Analysis

Activity Inputs

47.3 / 100
StarsRepository reach
15.6 / 30
FreshnessLast push recency
21.9 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
9.6 / 20

Common questions about Nanobanana MCP Server

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.9/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?
Maintained. Last push was 22 days ago.
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?
6% 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.
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-09-27
Activity Resumed
Activity resumed
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Google Gemini
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Drift Warning Raised
Package-provenance drift warning: package metadata no longer clearly points at this repo
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
Rank 22HVTrust 3Score 2Stale 1Scorecard 1Delisted 1Listed 1Drift 1MCP 1Surface 1Fresh 1
2026-11-01
Rank Moved
Rank dropped 21 spots (#1157 → #1178)
2026-10-28
Rank Moved
Rank rose 11 spots (#1165 → #1154)
2026-10-27
Rank Moved
Rank dropped 17 spots (#1148 → #1165)
2026-10-27
Activity Score Changed
Activity score down 6pts (59 → 53)
2026-10-20
Rank Moved
Rank dropped 11 spots (#1128 → #1139)
2026-10-15
Rank Moved
Rank rose 21 spots (#1144 → #1123)
2026-10-09
Rank Moved
Rank dropped 15 spots (#1110 → #1125)
2026-09-27
Activity Resumed
Activity resumed
2026-09-27
Rank Moved
Rank rose 164 spots (#1272 → #1108)
2026-09-27
HVTrust Changed
HVTrust up 10.0pts (32.7 → 42.7)
2026-09-27
Activity Score Changed
Activity score up 27pts (32 → 59)
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Google Gemini
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Drift Warning Raised
Package-provenance drift warning: package metadata no longer clearly points at this repo
2026-09-23
Rank Moved
Rank dropped 18 spots (#1250 → #1268)
2026-09-23
HVTrust Changed
HVTrust up 17.2pts (15.6 → 32.8)
2026-09-22
Newly Listed
First tracked at rank #1250
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-08
Rank Moved
Rank dropped 11 spots (#1231 → #1242)
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)
GitHub → PyPI: nanobanana-mcp-server

Embed Badge Badge guide for maintainers →

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