Robin Saige we check the tools AI agents call

openFlow

io.github.molkex/omni-flash-veo3-nano-banana

Omni Flash and Veo video, Nano Banana images on Google Flow, from any MCP client

— the operator's own registry description reported

Publisher io.github.molkex · first seen 2026-08-24 · endpoint https://openflowmcp.com/mcp

allow
verdict
rich-slow-solo
cluster
ok_tools
answers
35
tools served

Dependency rating derived

allow
allow — alive & usable · action ● · V n/a
allow — because answers ●, 35 tools legible (band B) ●, no confirmed drift in 2 probes ●; not yet checked: truth (0 runs)

Cluster rich-slow-solo · distinctiveness 0.774 (unusual). Every figure is a percentile or class within the 15,472-server censussee the whole spectrum.

Does it answer? Q1 · observed
answersalive_tools
latency379 ms
vs populationslow
protocolcurrent
authopen
Can it be used? Q4 · observed
tools35
vs populationhigh
capabilities4
harnessB
Did it hold when checked? Q3–Q4 · derived
identitysolo
servers on its host1
verifiabilityunassessed
duplicate inventoryno
drift events0
answers trueno primary

🔏 Signed receipt rr_e4bca2e1243e01a59e411f62 · ed25519 · key rs-rcpt-2026-08 — this rating is tamper-evident; an agent gets the full signature from check_server and can verify it against the published key.

Q1Does it answer?alive & usable — 2 probes ●evidence ↓
Q2What is it?action ● evidence ↓
Q3Can it be checked?V n/a for this kind ◐evidence ↓
Q4Did it hold?harness B · truth not yet run · no drift ●evidence ↓
Q5What company does it keep?rich-slow-solo · 1 on its host (context, not verdict) ◐evidence ↓

● observed · ◐ derived · ○ reported — the verdict synthesizes Q1–Q4; Q5 is context. Methodology →

History observed

Every probe we made, oldest → newest (2 shown, 2026-08-30 → 2026-09-06). Green answered · amber answered-but-walled · red no useful answer. A gap in our cadence is a gap in coverage, not evidence about the server.

changelog (2 events)
datetypewhat changed
2026-09-06outcomeok_tools (was auth_required)
2026-08-30outcomefirst probe: auth_required

What kind of tools these are derived

Verification only means something relative to a tool's NATURE — an email-sender has no "true answer", a generator has no answer key. Classification evidence: classified from tool names/descriptions/annotations WE OBSERVED. What checking applies to each kind (the full methodology →):

naturetoolsmeaning what checking applies
action19changes the worldno true answer exists; we check the CONTRACT (destructive/read-only/idempotent declarations, error legibility) and never fire real actions
generative10creates contentno answer key exists; disclosure + stability checks, never truth verdicts
retrieval-public5serves public factstruth-checkable against a public source — the V-ladder applies in full
unclassified1not classifiable from its textTier-1 only until its tools describe themselves

Tools last seen observed

add_account_token check_credits check_job create_character create_character_from_description create_character_from_photo create_project edit_video extend_video fetch_media flow_dashboard flow_health flow_status generate_character_expression_sheet generate_character_image generate_character_turnaround generate_image generate_scene generate_video generate_video_between_frames generate_video_from_image generate_video_with_reference generate_with_face list_characters list_models music_chat music_credits music_download music_generate music_get music_list music_stems update_character upscale_image upscale_video

Harness readiness observed

Can an agent's harness pick this tool and call it correctly? Graded on the three things an agent reads — name, description, typed parameters. Band B — usable, with rough edges.

legibility checktools passingok
name is clear & specific35/35
has a description35/35
description is substantive33/3533/35
parameters are typed35/35
parameters are described6/356/35

35 of 35 tools graded · 35 with a captured input schema. RS-008, Tier-1 — no domain knowledge, applies to any tool. “Alive” is not the same as “usable”.

Truth checks observed

Not in the Tier-2 trade lane, or not yet checked. Tier-2 re-derives a server's answers against published primary sources — see truth checks.

Protocol conformance observed

2025-06-18
protocol version
session model
server version openFlowAPI

Capabilities: experimental prompts resources tools

Drift observed

No confirmed drift on record. Baseline set 2026-09-06; changes appear here after human review.

raw probe records
probed (UTC) outcomehttpmsprotocol
2026-09-06T06:16:41Zok_tools2003792025-06-18
2026-08-30T06:16:29Zauth_required401398

Watch or embed this verdict

verdict badge

Operators: put the live verdict in your README — it updates with every census, links back here, and is a dated observation, never a warranty:

[![Robin Saige verdict](https://robinsaige.com/badge/io.github.molkex/omni-flash-veo3-nano-banana.svg)](https://robinsaige.com/s/io.github.molkex/omni-flash-veo3-nano-banana)

Depend on it? Subscribe to its change feed — outcome changes and confirmed drift, no account needed. Building on it? The full dossier as JSON — verdict, rating, truth checks, history — stable enough to gate CI on.

← overview

Operator of this server? Everything we hold about it is on this page — free, no account, for anyone. Wrong attribution, stale probe, misclassification? Dispute this record →