Back to MCP servers

openFlow — Google Flow (Veo, Nano Banana)

https://server.smithery.ai/molkex/openflow/mcp
● healthy

Generate images and video on Google Flow — Nano Banana for stills, Veo for clips — from Claude Code, Cursor or any MCP client. Google has no public API for Flow; this server is the wire. 31 tools: image generation and upscaling, video (text-to-video, image-to-video, reference-to-video, interpolation, extension), characters that keep the same face across shots, and music with lyrics and stems. Runs on YOUR own Google account — generations spend your own credits, no markup. Images are free with no daily limit; video needs a subscription ($6/month, $3/month on a yearly plan), payable by card or directly in USDT on TRON, BSC, TON or Solana. Get a key at https://openflowmcp.com — instant, no card. Pass it as Authorization: Bearer <key>.

Transport
streamable-http
Auth
smithery_api_key
Cost
—
Protocol revision
2025-11-25
negotiated, not declared

MCP readiness

B · 87/100

Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here C+, 70.0/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ

Valid MCP handshake 10/10 initialize and tools/list both answered.
Live MCP endpoint 24/25 Endpoint answers the MCP initialize handshake (3183 ms); slow response -1.
Protocol revision 8/10 Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28.
Signed descriptor n/a No MCP standard defines a signed server descriptor.
Uptime (30 days) 15/15 30/30 probes succeeded over 30 days (100%).
Tool declaration 10/10 Lists 54 tool(s) with descriptions.
Verified identity 5/10 Publisher declared (repository, package or homepage); claim this listing to verify domain control.
Freshness + modern flags 4/5 seen in a source within 7 days.
Auth declaration 2/5 Declares credential scheme: smithery_api_key.
Applicable criteria total 90 points, scaled to 100.
Responsiveness: Slow (3183 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).
Measured 2026-11-11.
Nine criteria, the same as the A2A readiness score, read from our daily MCP probe (initialize + tools/list) and 30-day probe history. No MCP standard defines a signed server descriptor, so that criterion is n/a and the other 90 points are scaled to 100. Grades: A>=90, B>=75, C>=60, D>=40, F<40. Display only: search order uses the quality grade.

Compared with peers

Against 53,039 reachable MCP servers in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.

Readiness
Higher than 88% of peers
This listing 87 · peer median 81
Latency
Faster than 6% of peers
This listing 1,093 ms · peer median 326 ms

Where it loses the most points, and how to win them back

  • Verified identity −5 — Claim the listing and prove control of its domain.
    Now: Publisher declared (repository, package or homepage); claim this listing to verify domain control.
  • Auth declaration −3 — State how to authenticate (an auth scheme, or that none is needed).
    Now: Declares credential scheme: smithery_api_key.
  • Protocol revision −2 — Support the current protocol revision.
    Now: Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28.

How many agent tools actually work · All statistics

Listed in

Directories this entry was found in.

How to connect

MCP endpoint (streamable-http)
https://server.smithery.ai/molkex/openflow/mcp
JSON-RPC initialize probe
curl -X POST https://server.smithery.ai/molkex/openflow/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'
Homepage
https://openflowmcp.com
Listed at (smithery)
https://openflowmcp.com