# io.github.tryflask/flask (remote · api.flask.do)

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

- Trust score: 81/100 (high trust)
- Change this week: +8
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `api.flask.do`: 81/100 (this document), [markdown](https://verifymcp.io/servers/tryflask-flask/api-mcp-mcp.md), [page](https://verifymcp.io/servers/tryflask-flask/api-mcp-mcp)

## Channel facts

- Endpoint: `https://api.flask.do/api/mcp/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 94/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 74/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 4959 tokens (~309/item across 16 items; 16 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http tryflask-flask https://api.flask.do/api/mcp/mcp
```

### Codex

```toml
[mcp_servers.tryflask-flask]
url = "https://api.flask.do/api/mcp/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "tryflask-flask": {
      "type": "remote",
      "url": "https://api.flask.do/api/mcp/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add tryflask-flask --url https://api.flask.do/api/mcp/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  tryflask-flask:
    url: "https://api.flask.do/api/mcp/mcp"
```

### Other

```json
{
  "mcpServers": {
    "tryflask-flask": {
      "type": "http",
      "url": "https://api.flask.do/api/mcp/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 80, +5)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-28 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 73, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 73)

First indexed and scored.

## MCP tools (16)

### `contents` (~105 tokens)

Browse contents. Without folder_id: lists what's at the team's top level (root) — both folders and assets that live directly at root. With folder_id: opens that folder and returns its child folders and assets (videos/media). Each item includes its URL.

Input parameters:

- `folder_id` (string): Folder to open — omit to see team root
- `limit` (number): Page size (default 20, max 100)
- `offset` (number): Items to skip for pagination

### `feedback_list` (~142 tokens)

List top-level feedback on an asset. Returns each item's text body, tags (by name), author, timestamp, and reply_count. Recording items also include the recording's AI summary and the transcript for that segment of the recording. Items with visual attachments carry images (attached image files) and/or has_drawing: true (a drawing made on the asset) - call get_annotated_frames to see them. Use feedback_get to read full reply threads.

Input parameters:

- `asset_id` (string, required): Asset to list feedback for
- `limit` (number): Page size (default 20, max 100)
- `offset` (number): Items to skip for pagination

### `feedback_get` (~145 tokens)

Get a single feedback item with its full reply thread. Returns the item's text body, tags (by name), author, video timestamp, recording summary/transcript, visual attachments (images / has_drawing - render them with get_annotated_frames), and all nested replies. Pass transcript: "full" to get the recording's complete transcript instead of just this segment's slice (replies always carry their own segment slice).

Input parameters:

- `element_id` (string, required): Feedback item ID to retrieve
- `transcript` (string): Transcript scope for recording items: "segment" (default) returns only this segment's slice of the recording transcript; "full" returns the recording's complete transcript

### `wait_for_feedback` (~162 tokens)

Wait for NEW feedback on an asset. Blocks up to timeout_seconds (default 45) and returns as soon as feedback newer than `since` arrives, or times out with an empty list. To listen continuously, call it again with the returned next_since. Use this after uploading a video for review instead of repeatedly calling feedback_list.

Input parameters:

- `asset_id` (string, required): Asset to watch for new feedback
- `since` (string): ISO timestamp — only feedback created after this is returned. Omit on the first call (defaults to now, i.e. waits for the NEXT feedback). On subsequent calls pass the next_since from the previous res…
- `timeout_seconds` (number): How long to wait before returning empty (10-50, default 45)

### `feedback_post` (~234 tokens)

Create a feedback comment on an asset, as the connected user. PREFER passing timestamp (seconds into the video) whenever the source material has one - e.g. when importing feedback from an email like 'at 0:42 the logo is wrong', convert 0:42 to 42. Without timestamp the comment is a general (non-anchored) note. tags applies the team's EXISTING tags by name (see the tags tool); statuses are tags too. Use reply_to to reply in an existing thread. Cannot attach recordings, drawings, or images.

Input parameters:

- `asset_id` (string, required): Asset to comment on
- `content` (string, required): The comment text (plain text)
- `reply_to` (string): Feedback item id to reply to (threads the comment under it)
- `tags` (array): Tag NAMES to apply (must already exist in the team - see the tags tool)
- `timestamp` (number): Video time in SECONDS the comment refers to (e.g. 72.5 for 1:12.5). Strongly preferred when known; omit for a general comment.

### `feedback_update` (~184 tokens)

Edit an existing feedback item. content (replaces the text) and timestamp (video time in seconds) can only be changed on the connected user's OWN comments. add_tags / remove_tags apply the team's existing tags by NAME and work on ANY feedback item you can comment on (labels and statuses are collaborative - e.g. add the 'Done' tag to mark feedback resolved). Provide at least one of content, timestamp, add_tags, remove_tags.

Input parameters:

- `add_tags` (array): Tag NAMES to add (must already exist in the team)
- `content` (string): New comment text (fully replaces the existing text; own comments only)
- `element_id` (string, required): Feedback item to edit
- `remove_tags` (array): Tag NAMES to remove
- `timestamp` (number): New video time in SECONDS the comment refers to (own comments only)

### `get_annotated_frames` (~165 tokens)

Supplementary visuals for a feedback item. For recording items: the media under review with the reviewer's drawing rendered in, plus their shared SCREEN when they demonstrated something (e.g. a Photoshop/Figma mockup); webcam frames are NOT included, and the transcript is returned marked [FRAME N]. Also works for text comments that carry visuals: a standalone drawing (has_drawing: true) is rendered onto the frame it was drawn over, and attached images (images array) are returned as frames. If a visual reference is still unclear, call get_frame to drill into a specific moment (at) or spoken word/phrase (word). Returns up to 12 images.

Input parameters:

- `element_id` (string, required): The feedback item (element) to get annotated frames for

### `get_frame` (~156 tokens)

Drill into a recording for MORE visual detail: get the exact frame at a specific time (at) or when a specific word/phrase was spoken (word). Use when get_annotated_frames did not show what a reference ('this','here','that') means, or to see a moment the transcript mentions. Returns the asset frame at that moment (plus the active shared screen, if any) and a transcript snippet around it.

Input parameters:

- `at` (number): recording time in seconds
- `element_id` (string, required): The recording feedback item (element) to drill into
- `source` (string): limit to the asset frame or the shared-screen frame
- `word` (string): a word or short phrase the reviewer spoke

### `asset_status` (~44 tokens)

Check the processing status of a video asset. Returns progress percentage for videos being processed, or confirms the asset is ready.

Input parameters:

- `asset_id` (string, required): Asset ID to check

### `permission_get` (~89 tokens)

See who has access to a folder and their permission levels (full_access, comment, view, none). Returns team members with their roles, plus link and team-member default access levels.

Input parameters:

- `folder_id` (string, required): Folder to check permissions for
- `limit` (number): Page size for members (default 20, max 100)
- `offset` (number): Members to skip for pagination

### `search` (~57 tokens)

Search across your team's folders, assets, and feedback by text. Always returns all three categories together.

Input parameters:

- `limit` (number): Max results per category (default 10, max 50)
- `query` (string, required): Text to search for

### `recent_activity` (~87 tokens)

Get the latest comments across your team, newest first. Returns a mix of text and recording comments with author, timestamp, and a link to jump into the conversation. Each item has a `type` field ("text" or "recording") so you can filter client-side if needed.

Input parameters:

- `limit` (number): Number of recent comments to return (default 20, max 100)

### `tags` (~118 tokens)

List the team's tags and show the share of each tag (plus an 'untagged' bucket) across a scope. Scope defaults to the whole team; pass folder_id to narrow to one folder, or asset_id to narrow to one asset. Shares are count_with_tag / total_elements and do NOT sum to 100% because elements can carry multiple tags.

Input parameters:

- `asset_id` (string): Narrow to this asset (mutually exclusive with folder_id)
- `folder_id` (string): Narrow to this folder (mutually exclusive with asset_id)

### `upload_video` (~283 tokens)

Upload a video from a public URL (a direct video file link or a Google Drive share link) into Flask. Flask downloads it, stores it, and starts processing. Returns the new asset_id — poll asset_status(asset_id) until status is "ready" before linking to it. folder_id is OPTIONAL: omit it to upload to the team's top level (root). Free to use for up to 100 MCP uploads; beyond that the user needs a plan at https://flask.do/plan. You still need edit access on the folder if one is given. For a LOCAL file on disk, use upload_file_start instead.

Input parameters:

- `folder_id` (string): Optional folder to upload into (you must have edit access — check with permission_get if unsure). Omit to upload to the team's top level (root).
- `title` (string): Title for the new asset (defaults to "Video from URL")
- `version_of` (string): Upload as a NEW VERSION of an existing asset instead of a separate asset. Accepts the id of a version stack or of any existing video asset (standalone or already in a stack). The new upload becomes t…
- `video_url` (string, required): Public URL of the video to import — a direct video file URL or a Google Drive share link

### `upload_file_start` (~337 tokens)

Start uploading a LOCAL video file from the user's machine into Flask. Returns the shareable Flask link immediately, plus a presigned upload URL. After calling this, upload the file bytes with the curl command from next_step, then call upload_file_complete. folder_id is OPTIONAL: omit it to upload to the team's top level (root). Max file size 5GB. Free to use for up to 100 MCP uploads; beyond that the user needs a plan at https://flask.do/plan. You still need edit access on the folder if one is given.

Input parameters:

- `content_type` (string): MIME type of the file (defaults to video/mp4)
- `file_size` (integer, required): Exact size of the local file in bytes (e.g. from `stat -f%z <file>` on macOS or `stat -c%s <file>` on Linux)
- `folder_id` (string): Optional folder to upload into (you must have edit access — check with permission_get if unsure). Omit to upload to the team's top level (root).
- `title` (string): Title for the new asset (defaults to "Untitled Video")
- `version_of` (string): Upload as a NEW VERSION of an existing asset instead of a separate asset. Accepts the id of a version stack or of any existing video asset. The new upload is attached to the version stack immediately…

### `upload_file_complete` (~120 tokens)

Finalize a local file upload started with upload_file_start. Call this only AFTER the curl PUT has finished successfully. Verifies the file landed in storage and starts video processing. Safe to retry.

Input parameters:

- `asset_id` (string, required): The asset_id returned by upload_file_start
- `version_of` (string): Pass the same value given to upload_file_start. The version is normally already attached at start; this is a no-op safety net that re-attaches only if that failed. The link returned is the version st…

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/tryflask-flask/api-mcp-mcp#diagnostics

## Score history

- 2026-08-03: 81
- 2026-08-02: 81
- 2026-08-01: 80
- 2026-07-31: 80
- 2026-07-30: 75
- 2026-07-29: 75
- 2026-07-28: 74
- 2026-07-27: 73
- 2026-07-26: 73

## Links

- Remote endpoint: https://api.flask.do/api/mcp/mcp
- Repository: https://github.com/tryflask/skills
- Website: https://flask.do/mcp
- Changelog RSS feed: https://verifymcp.io/servers/tryflask-flask/api-mcp-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/tryflask-flask/api-mcp-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/tryflask-flask/api-mcp-mcp