Robin Saige we check the tools AI agents call

flask

io.github.tryflask/flask

Feedback layer for video. Reviewers talk through feedback; agents read it as structured comments.

— the operator's own registry description reported

Publisher io.github.tryflask · first seen 2026-08-12 · endpoint https://api.flask.do/api/mcp/mcp

allow
verdict
mid-slow-solo
cluster
ok_tools
answers
17
tools served

Dependency rating derived

allow — mid-slow-solo — safe to depend on

Cluster mid-slow-solo · distinctiveness 0.506 (moderate). Every figure is a percentile or class within the 11,094-server censussee the whole spectrum.

Reach — can an agent get to it?
answersalive_tools
latency382 ms
vs populationslow
protocolcurrent
authopen
Use — can it use it?
tools17
vs populationmid
capabilities3
harnessA
Trust — can it rely on it?
identitysolo
servers on its host1
verifiabilityunassessed
duplicate inventoryno
drift events0
answers trueno primary

🔏 Signed receipt rr_75997839e1900f80e66f0d5f · 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.

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. This server's 17 tools, classified, with what checking applies to each kind (the full methodology →):

naturetoolsmeaning what checking applies
retrieval-public12serves public factstruth-checkable against a public source — the V-ladder applies in full
action5changes the worldno true answer exists; we check the CONTRACT (destructive/read-only/idempotent declarations, error legibility) and never fire real actions

Tools last seen

asset_status contents feedback_get feedback_list feedback_post feedback_stats feedback_update get_annotated_frames get_frame permission_get recent_activity search tags upload_file_complete upload_file_start upload_video wait_for_feedback

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 A — an agent can pick and call these reliably.

legibility checktools passingok
name is clear & specific17/17
has a description17/17
description is substantive17/17
parameters are typed17/17
parameters are described17/17

17 of 17 tools graded · 17 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
1.0.0
server version flask

Capabilities: prompts resources tools

Drift

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

History observed

Every probe we made, oldest → newest (2 shown, 2026-08-12 → 2026-08-14). 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 (1 events)
datetypewhat changed
2026-08-12outcomefirst probe: ok_tools
raw probe records
probed (UTC) outcomehttpmsprotocol
2026-08-14T20:00:16Zok_tools2003822025-06-18
2026-08-12T05:35:29Zok_tools2002582025-06-18

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.tryflask/flask.svg)](https://robinsaige.com/s/io.github.tryflask/flask)

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