FlowScope UX Flow Analyser
PYPI · FLOWSCOPE-MCP
Turn YouTube product demos into structured UX flow reports, and compare demos side by side.
Available components
Last scanned (3 hours ago)
Scores higher than 60% of PyPI servers
Category Design and Media
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 28 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 17 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability82
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1204 tokens (~109/item across 11 items; 10 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
- Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (90% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +4
- Stability: unverified → 0.23 ▲ functional
- 18 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 17 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 14 Oct 26 +15
- Malware scan: pass → unverified ▼ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Tool coverage: 0 functional
- First check of Schema quality: fail functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: 100 functional
- First check of Tool coverage: 90 functional
- First check of Schema quality: good functional
- 12 Oct 26 39
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 24 Oct 2026 · Analysed pypi/flowscope-mcp@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 28 packages
| Packages resolved | 28 |
|---|---|
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
flowscope_analyze_video Analyse a YouTube product demo ~164
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 check flowscope_list_videos first -- an already-analysed video is reused for free and immediately. By default this waits for completion and returns the reports; if the analysis needs longer than wait_seconds it returns status 'running' with video ids to poll.
| Name | Type | Req | Description |
|---|---|---|---|
| force | boolean | – | – |
| force_local_transcription | boolean | – | – |
| urls | array | yes | – |
| wait | boolean | – | – |
| wait_seconds | number | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | Plain-language summary of what happened. |
| reports | array | – | Filled in only when every video finished within the wait budget. |
| reused_count | integer | – | – |
| started_count | integer | – | – |
| status | string | yes | 'done', 'reused', 'running' or 'error'. |
| videos | array | – | – |
No examples provided.
flowscope_compare_videos Compare the UX of several videos ~95
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 re-analysed.
| Name | Type | Req | Description |
|---|---|---|---|
| force_refresh | boolean | – | – |
| video_ids | array | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| common_patterns | array | – | What the products share. |
| divergences | array | – | Where they differ. |
| estimated_cost_usd | – | – | – |
| message | string | – | Why the comparison failed, when ok is false. |
| ok | boolean | – | False when the comparison failed. |
| report_markdown | string | – | The comparison rendered as Markdown. |
| stage_matrix | array | – | Per-stage, per-product breakdown. |
| video_ids | array | – | – |
No examples provided.
flowscope_delete_video Delete a video and its analysis ~65
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.
| Name | Type | Req | Description |
|---|---|---|---|
| delete_media | boolean | – | – |
| video_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| job_id | – | – | – |
| message | string | yes | – |
| ok | boolean | yes | – |
| status | – | – | – |
| video_id | string | yes | – |
No examples provided.
flowscope_frame_image View a screen screenshot ~86
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.
| Name | Type | Req | Description |
|---|---|---|---|
| frame_id | string | yes | – |
| video_id | string | yes | – |
No output schema declared.
No examples provided.
flowscope_get_report Read a video's UX report ~84
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.
| Name | Type | Req | Description |
|---|---|---|---|
| include_transcript | boolean | – | – |
| max_frames | integer | – | – |
| video_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| channel | – | – | – |
| duration_seconds | – | – | – |
| flow_steps | array | – | Ordered user flow. |
| frames | array | – | Per-screen findings, in video order. |
| message | string | – | Why the report is missing, when ok is false. |
| note | string | – | Caveats about this report, if any. |
| ok | boolean | – | False when the report could not be read. |
| report_markdown | string | – | The whole report rendered as Markdown. |
| screen_count | integer | – | Number of distinct screens analysed. |
| status | – | – | Latest job status. |
| title | – | – | – |
| transcript_excerpt | – | – | Transcript text, present only when include_transcript was true. |
| transcript_source | – | – | – |
| truncated | boolean | – | True when frames were dropped to respect max_frames. |
| ux_insights | array | – | Synthesised UX observations. |
| video_id | string | yes | – |
| youtube_url | string | – | – |
No examples provided.
flowscope_health_check Check FlowScope readiness ~63
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| advice | string | – | What to do about blocking_problems, if any. |
| backend_url | string | yes | Base URL this server is talking to. |
| blocking_problems | array | – | Human-readable list of reasons analysis would fail; empty when ok is true. |
| ffmpeg_available | boolean | yes | ffmpeg present; required for frame extraction. |
| ffmpeg_version | – | – | Detected ffmpeg version. |
| llm_comparison_model | string | – | Model used for comparisons. |
| llm_provider | string | – | Default provider. |
| llm_providers_available | array | – | Providers with credentials, e.g. ['openai']. |
| llm_synthesis_model | string | – | Model used to synthesise the flow. |
| llm_vision_model | string | – | Model used for the frame (vision) stage. |
| ok | boolean | yes | True when the backend answered and can analyse videos. |
| yt_dlp_available | boolean | yes | yt-dlp importable; required to download videos. |
No examples provided.
flowscope_job_status Check analysis progress ~67
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.
| Name | Type | Req | Description |
|---|---|---|---|
| video_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| error_message | – | – | – |
| is_terminal | boolean | yes | True when the job finished, successfully or not. |
| job_id | – | – | – |
| next_action | string | yes | What the caller should do next. |
| percent_complete | – | – | Null when the total is unknown. |
| progress_current | integer | – | – |
| progress_total | integer | – | – |
| stage_detail | – | – | – |
| stage_label | string | yes | Human-readable version of status. |
| status | string | yes | queued|downloading|...|synthesizing|done|error |
| video_id | string | yes | – |
No examples provided.
flowscope_list_videos List analysed videos ~66
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | – |
| videos | array | yes | – |
No examples provided.
flowscope_reanalyze_video Redo the derived analysis for a video ~74
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.
| Name | Type | Req | Description |
|---|---|---|---|
| video_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| job_id | – | – | – |
| message | string | yes | – |
| ok | boolean | yes | – |
| status | – | – | – |
| video_id | string | yes | – |
No examples provided.
flowscope_retry_video Retry a failed analysis ~64
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.
| Name | Type | Req | Description |
|---|---|---|---|
| video_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| job_id | – | – | – |
| message | string | yes | – |
| ok | boolean | yes | – |
| status | – | – | – |
| video_id | string | yes | – |
No examples provided.
How do I install the FlowScope UX Flow Analyser MCP server?
FlowScope UX Flow Analyser runs locally as a PyPI package, launched with uvx flowscope-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · flowscope-mcp
claude mcp add davidngugi-flowscope -- uvx flowscope-mcp
What is the FlowScope UX Flow Analyser MCP server?
FlowScope UX Flow Analyser is an MCP server listed in the public MCP registry as io.github.DavidNgugi/flowscope. Turn YouTube product demos into structured UX flow reports, and compare demos side by side. This page covers its PyPI package (flowscope-mcp).
Is the FlowScope UX Flow Analyser MCP server safe to use?
FlowScope UX Flow Analyser scores 59 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 24 October 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the FlowScope UX Flow Analyser MCP server expose?
FlowScope UX Flow Analyser exposes 10 tools: flowscope_health_check, flowscope_list_videos, flowscope_job_status, flowscope_get_report, flowscope_compare_videos, and 5 more. Their descriptions and schemas cost roughly 828 tokens of context every time the server is loaded.
Is the FlowScope UX Flow Analyser MCP server still maintained?
FlowScope UX Flow Analyser is still listed as active in the MCP registry. We last reached this channel on 24 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the FlowScope UX Flow Analyser MCP server under?
FlowScope UX Flow Analyser declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.