Home / MCP registry index / ai.cueframe/cueframe

CueFrame

ai.cueframe/cueframe in the official MCP registry. Endpoint https://api.cueframe.ai/v1/mcp. Source: github.com/cueframe-ai/cueframe-mcp.

The registry describes it as: Turn footage into finished video: reframing, captions behind the subject, motion graphics, renders.

We read its 92 tools on 2026-10-21. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Tools it advertises

editorial_run_source editorial_list_briefs editorial_list_runs editorial_get_run editorial_list_evidence editorial_findings_list editorial_create_brief editorial_create_run editorial_inspect_source editorial_sample_motion editorial_inspect_audio editorial_inspect_transcript editorial_findings_append editorial_integrate editorial_apply compose apply_composition validate_composition create_render preview_frame preview_component preview_clip score_composition consult resume create_brief get_brief list_briefs get_checkpoint list_checkpoints update_brief delete_brief select_candidate create_component list_catalog resolve_builtin_component list_templates get_template apply_template get_component_source get_media_context get_transcript prepare_media get_media_facts list_media download_media get_render refresh_render_url create_project new_composition get_composition list_compositions delete_composition list_projects derive_composition import_media generate_media create_upload finalize_upload search_resources and 32 more

Run this server? Show the check in your README

The badge reflects the latest weekly read: MCP tool check badge

Markdown
[![MCP tool check](https://lazaretto.dev/mcp-registry/ai-cueframe-cueframe/badge.svg)](https://lazaretto.dev/mcp-registry/ai-cueframe-cueframe)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.