Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/AceDataCloud/NanoBananaMCPWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/acedatacloud/nanobananamcp/nano-banana)<a href="https://agentmods.dev/mcp/acedatacloud/nanobananamcp/nano-banana"><img src="https://agentmods.dev/badge/mcp/acedatacloud/nanobananamcp/nano-banana/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/acedatacloud/nanobananamcp/nano-banana"><img src="https://agentmods.dev/badge/mcp/acedatacloud/nanobananamcp/nano-banana.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket warn
Grade A, and why
nano-banana scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"nano-banana": {
"command": "uvx",
"args": [
"--from",
"mcp-nanobanana-pro==2026.10.19.3",
"mcp-nanobanana-pro"
]
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 4d ago First seen · 10 lines scan A a37e014c18db
nano-banana is an MCP server published in the GitHub repository AceDataCloud/NanoBananaMCP (7 stars, last pushed 5d ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-20.
Other mcp servers, from other repositories
mcp-flux-pro
MCP Server for Flux AI Image Generation via AceDataCloud API. Runs locally from the mcp-flux-pro Python package. Needs 1 environment variable to run.
mcp-seedream-pro
MCP Server for ByteDance Seedream AI Image Generation via AceDataCloud API. Runs locally from the mcp-seedream-pro Python package. Needs 1 environment variable to run.
mcp-midjourney
MCP Server for Midjourney AI Image Generation via AceDataCloud API. Runs locally from the mcp-midjourney Python package. Needs 1 environment variable to run.
z-image-mcp
RunAPI MCP server for Z Image: create tasks, poll status, check pricing. Runs locally from the @runapi.ai/z-image-mcp npm package. Needs 1 environment variable to run.
jimeng4-mcp
An MCP server for Jimeng AI, a Volcengine service that generates and works with multiple types of media. It supports the service’s listed 4.0, 3.1, and 3.0 models.
openai-image-mcp
MCP server "openai-image-mcp" as configured in aleslanger/OpenAI-image-mcp-server. Runs locally from the openai-image-mcp npm package.