mcp-registry/com.frapea/editor · v0.2.0
As of 2026-10-19 23:47 UTC, the Frapea Editor MCP server is up with a Glimind reliability score of 91/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
A video editor in your browser that your AI drives: cuts, captions, multicam, motion titles, export.
Claude Code
claude mcp add --transport http frapea-editor-mcp-server https://app.frapea.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"frapea-editor-mcp-server": {
"type": "http",
"url": "https://app.frapea.com/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
1 tool definition(s) exceed ~1,200 tokens each (largest: set_clip_properties, ~3,139).
Move long reference material out of descriptions (link a doc or expose a resource), drop repeated examples, and collapse large enums. Trimming these to ~600 tokens saves ~2,539 tokens every session. How to fix →
64 of 64 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
64 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.
Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →
15 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
7 parameter(s) across 2 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
Loading this server's tool list costs an agent ~21,240 tokens before any work — more than 95% of MCP servers.
Split rarely-used tools into a separate server or a toolset the client can enable, or expose one "search tools" entry point. Many agents load every connected server's tools into every request. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
In the last 30 days: 0 tool(s) removed and 3 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 2 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.frapea%2Feditor/fixes
{
"name": "add_clips",
"description": "Places media segments on a timeline. Each clip: mediaRef (from get_media, 'timeline:<id>' to NEST another timeline as a clip, 'solid:#rrggbb' , 'motion:<id>' for a MOTION composition (create_motion_composition) for a generated solid-colour matte, 'adjustment:' for an adjustment clip — no picture of its own, its effects/masks/opacity grade everything below it — or 'text:' for a title, restyled via set_clip_properties' `text`), atFrame (timeline position), sourceInSec/sourceOutSec (the segment of ",
"inputSchema": {
"type": "object",
"required": [
"projectId",
"timelineId",
"clips",
"token"
],
"properties": {
"clips": {
"type": "array",
"description": "[{mediaRef, atFrame, sourceInSec, sourceOutSec, trackId?}] — segments in playback order; trackId targets a specific track (default V1/A1)."
},
"token": {
"type": "string",
"description": "The session token `connect` returned. Pass it on every call — it says which browser to drive."
},
"projectId": {
"type": "string",
"description": "Project id from get_projects."
},
"timelineId": {
"type": "string",
"description": "Target timeline id from get_timeline."
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}{
"name": "add_sfx",
"description": "frapea's BUILT-IN sound-effects pack — synthesized, licence-free, no API key, no download wait. Reach for this FIRST; use search_sounds only for something the pack does not cover (ambience, foley, a specific real-world object). Call with no `ids` to get the catalogue: each sound carries what it sounds like AND when to use it. Call with `ids` to copy them into the project's media pool as `sfx-<id>.wav` at the Library root; each result gives a mediaRef ready for add_clips on an audio track. Adding",
"inputSchema": {
"type": "object",
"required": [
"projectId",
"token"
],
"properties": {
"id": {
"type": "string",
"description": "Convenience: a single sound id."
},
"ids": {
"type": "array",
"items": {
"type": "string"
},
"description": "Sound ids to add (e.g. ['whip','thump','ding']). Omit to list the pack."
},
"token": {
"type": "string",
"description": "The session token `connect` returned. Pass it on every call — it says which browser to drive."
},
"projectId": {
"type": "string",
"description": "Project id from get_projects."
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}{
"name": "close_project",
"description": "Navigates the user's Frapea tab back to the project manager and releases this session's headless runtime for the project.",
"inputSchema": {
"type": "object",
"required": [
"projectId",
"token"
],
"properties": {
"token": {
"type": "string",
"description": "The session token `connect` returned. Pass it on every call — it says which browser to drive."
},
"projectId": {
"type": "string",
"description": "Project id from get_projects."
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": true,
"idempotentHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.frapea/editor"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.frapea/editor"}) over MCP.
set_clip_properties ~3,139 tokensgenerate_voiceover ~730 tokenscreate_motion_composition ~568 tokensmanage_effects ~559 tokensset_keyframes ~539 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fcom.frapea%2Feditor?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.frapea%2Feditor?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.frapea%2Feditor.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.frapea%2Feditor.svg :target: https://glimind.com/server/mcp-registry%2Fcom.frapea%2Feditor?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:338be785da99cd50…, first seen 2026-10-18, included at leaf 21553 of 29,518. Version history · verify what your client received.
Compare: most reliable media servers · most reliable communication servers · most reliable ml servers · most reliable browser servers · most reliable files servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-19 23:47 UTC, the Frapea Editor MCP server is up with a Glimind reliability score of 91/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Frapea Editor MCP server advertises 64 tools, including add_clips, add_sfx, apply_layout, await_user_action, bind_face.
Point your MCP client at this streamable-http endpoint: https://app.frapea.com/mcp
Glimind scanned all 64 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.