Verified conversions across 205 color spaces: CSS strings, gamut checks, .cube LUTs
Nothing to run from here
FlowScope UX Flow Analyser is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
99/100
trust score
69
downloads in 30d
local
runs on your machine
10
tools declared
What it does
Turn YouTube product demos into structured UX flow reports, and compare demos side by side.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user flowscope-ux-flow-analyser-mcp '--' uvx flowscope-mcp
# 2 — ask your agent for something these tools do
# flowscope_health_check, flowscope_list_videos, flowscope_job_status and 7 more
FlowScope UX Flow Analyser costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
PublisherVerified · since 2026
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts FlowScope UX Flow Analyser as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need uv (docs.astral.sh/uv): uvx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user flowscope-ux-flow-analyser-mcp '--' uvx flowscope-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it asks of you
Nothing is required, but it can take FLOWSCOPE_API_URL (Base URL of the running FlowScope backend. '/api' is appended if absent.), FLOWSCOPE_API_TOKEN (Bearer token, only needed when the backend sits behind an authenticating proxy.), FLOWSCOPE_MAX_WAIT (Default seconds that flowscope_analyze_video waits for a job before returning a job id.) if you want to set them.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
10 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Check that the FlowScope backend is running and that its dependencies (ffmpeg, yt-dlp, an LLM provider key) are ready. Call this before submitting a video so a missing prerequisite is reported as a config problem rather than a failed multi-minute job.
No parameter schema on file.
List videos FlowScope has been asked to analyse, newest first, with the status of each one's latest job. Call this first: results are cached by YouTube video id, so an existing entry means the analysis is free to re-read and must not be resubmitted.
No parameter schema on file.
Report the progress of a video's latest analysis job. Use this to poll after flowscope_analyze_video returns while still running, or to find out why an analysis failed. Poll every 20-30 seconds; do not resubmit the URL.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| video_id | string | yes | The FlowScope video id returned by flowscope_analyze_video. |
Return the finished UX analysis of one video: the ordered user flow, synthesised UX insights, and per-screen findings with the visible UI elements and the narration that accompanies each screen. This is the primary tool for answering UX questions about a video.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| video_id | string | yes | The FlowScope video id. |
| max_frames | integer | no | Maximum screens to include, evenly sampled across the flow. Use 0 for every screen. Defaults to 24 to keep the response small. |
| include_transcript | boolean | no | Include the full transcript text. Off by default because it is long and the per-screen excerpts already carry the relevant narration. |
Compare two or more already-analysed videos and return their common patterns, their divergences, and a per-stage matrix. Requires at least two videos that have finished analysing. The comparison is an LLM call, so it takes a while and costs money; results are cached until one of the videos is…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| video_ids | array | yes | Two or more FlowScope video ids that have finished analysing. |
| force_refresh | boolean | no | Recompute even though a stored comparison exists. |
Submit one or more YouTube URLs for UX analysis. FlowScope downloads each video, transcribes it, extracts and deduplicates screenshots of distinct screens, describes each screen with a vision model, and synthesises the flow. This is slow (minutes per video) and the vision steps cost money, so…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| urls | array | yes | YouTube video URLs to analyse. |
| wait | boolean | no | Block until the analysis finishes (or the wait budget expires). |
| wait_seconds | number | no | Override the wait budget in seconds. 0 uses the server default (FLOWSCOPE_MAX_WAIT, 900s). Ignored when wait is false. |
| force | boolean | no | Re-analyse even if this video id is already stored. Costs money; only use it to deliberately replace an existing analysis. |
| force_local_transcription | boolean | no | Skip YouTube captions and always transcribe the audio locally with Whisper. Slower, but useful when captions are wrong or missing. |
Re-queue the last analysis job for a video after a failure, or start a fresh job when the previous one finished. Stages that already completed are reused, so a retry does not re-download or re-bill them.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| video_id | string | yes | The FlowScope video id to retry. |
Discard a video's frames, per-screen analyses and synthesised flow, then redo extraction and analysis from the downloaded video. Use this after changing the LLM model or prompt. It deletes stored results and spends money again. Any comparison that included this video is dropped too.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| video_id | string | yes | The FlowScope video id to re-analyse. |
Permanently remove a video's analysis from FlowScope. With delete_media true it also deletes the downloaded video and extracted frames from disk, which cannot be undone. Ask the user before using delete_media.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| video_id | string | yes | The FlowScope video id to delete. |
| delete_media | boolean | no | Also delete the downloaded video and frame files from disk. |
Return the actual screenshot for one screen of a video, as an image the caller can look at. Use this when the written report is not enough and the visual layout matters, for example to judge spacing, hierarchy or visual style. Takes the video id and the frame_id from flowscope_get_report.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| video_id | string | yes | The video the frame belongs to, from flowscope_get_report. |
| frame_id | string | yes | The frame_id field on any entry of that report's frames. |
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install FlowScope UX Flow Analyser or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 99 / 100
Release 0.1.1 · scanned 14 Oct 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score99
Findings1 threat · 0 capability
Capabilityminimal
Coveragesource
Verificationrepo
Surface digestb666d3cf2e4469af90f58e6d39ce7214344f469a4ac23042a929ffd2a5efb0b3
Score vectorthreat 100 → client 99
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (10 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| flowscope_health_check | no tags | |
| flowscope_list_videos | no tags | |
| flowscope_job_status | no tags | |
| flowscope_get_report | no tags | |
| flowscope_compare_videos | no tags | |
| flowscope_analyze_video | no tags | |
| flowscope_retry_video | no tags | |
| flowscope_reanalyze_video | no tags | |
| flowscope_delete_video | no tags | |
| flowscope_frame_image | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digestb666d3cf2e4469af
Scanned2026-10-14
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.1.1. Pin a release below and the command asks for exactly that one.
0.1.1
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish FlowScope UX Flow Analyser can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.