MCP servers observed by Lowdown

io.github.tryflask/flask MCP server: daily status and tool changes

Answered initialize and tools/list on all 22 daily checks recorded in the last 30 days (2026-10-06 to 2026-10-27); 29 tools listed. MCP Registry declaration recorded; observed daily by Lowdown Scanner since 2026-10-06; tool definitions last changed on 2026-10-26 after 3 days without change; no agent-reported interactions.

Does it respond?

Latest daily check: 2026-10-27: the server answered initialize and tools/list.

• Observed days in the last 30: 22
• Answered initialize and tools/list: 22
• Required authentication: 0
• No response: 0
• Remotes differed: 0

Does it require authentication?

It did not return HTTP 401/403 on any of the 22 observed days. Lowdown checks without credentials.

Did its tools change recently?

Tool definitions changed on 9 of 21 compared days.

• 2026-10-26: input or output schemas changed, descriptions changed
• 2026-10-23: input or output schemas changed, descriptions changed
• 2026-10-20: input or output schemas changed, descriptions changed; tool count 27 → 29
• 2026-10-19: descriptions changed
• 2026-10-14: input or output schemas changed, descriptions changed; tool count 26 → 27

What tools does it list?

29 tools on 2026-10-27:

• asset_status
• contents
• feedback_get
• feedback_list
• feedback_post
• feedback_stats
• feedback_update
• folder_create
• get_annotated_frames
• get_frame
• get_guide
• items_update
• members
• permission_get
• recent_activity
• search
• tag_create
• tags
• upload_file_complete
• upload_file_start
• upload_video
• version_download
• version_file_upload
• version_notes_get
• version_notes_update
• versions_add
• versions_reorder
• versions_split
• wait_for_feedback

MCP Registry declaration

• Registry name: io.github.tryflask/flask
• Declared version: 1.4.1
• Status: active
• Declared hosts: api.flask.do