mcp-registry/one.cutclip/cutclip · registry v1.0.0 · server reports v0.0.1
Also listed as github/leovegas/cutclip-mcp
claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server. Other clientsAs of 2026-11-22 14:48 UTC, the CutClip.one MCP server is up with a Glimind reliability score of 90/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
AI video editor your agent can drive: plan scenes, edit a multi-track timeline, and render MP4s.
Point your MCP client at this streamable-http endpoint: https://cutclip.one/api/mcp
3 tool definition(s) exceed ~1,200 tokens each (largest: timeline.batch, ~1,402).
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,240 tokens every session. How to fix →
111 of 111 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 →
111 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 →
111 tool name(s) contain "." or exceed 64 characters, which OpenAI-compatible function calling rejects (^[a-zA-Z0-9_-]{1,64}$).
Use "_" or "-" instead of "." and keep names to 64 characters, so clients built on OpenAI-style tool calling don't have to rename (or drop) them. How to fix →
373 parameter(s) across 108 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 →
42 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 →
3 tool(s) have descriptions under 20 characters.
Say when to use the tool and what it returns, not just its name restated ("Get weather" → "Current weather for a city: temperature, conditions, wind. Use for 'now', not forecasts."). How to fix →
Loading this server's tool list costs an agent ~24,775 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 →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 108 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fone.cutclip%2Fcutclip/fixes
{
"name": "asset_capture_frame",
"description": "Grab one frame of a video asset (e.g. a take) as a new PNG image asset. timeMs is the position in the video itself, not on the timeline. Save the result with shot.add_still, location.add_reference or character.add_reference.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"projectId",
"assetId",
"timeMs"
],
"properties": {
"timeMs": {
"type": "number",
"minimum": 0
},
"assetId": {
"type": "string"
},
"projectId": {
"type": "string"
}
},
"additionalProperties": false
}
}{
"name": "asset_get",
"description": "Fetch one asset's metadata (type, source, mime type, duration/dimensions if known) plus a downloadUrl for its file: a plain HTTP GET, no auth header needed, valid 24h (call again for a fresh one)",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"assetId"
],
"properties": {
"assetId": {
"type": "string"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "asset_list",
"description": "List every asset uploaded/generated for a project (§11.7)",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"projectId"
],
"properties": {
"projectId": {
"type": "string"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": 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/one.cutclip/cutclip"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/one.cutclip/cutclip"}) over MCP.
timeline.batch ~1,402 tokensshot.update ~1,335 tokensproject.import ~1,303 tokensshot.create ~1,144 tokensscenario.update ~1,003 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.
Shows whether the server is live and its agent-readiness score; it updates within the hour.
[](https://glimind.com/server/mcp-registry%2Fone.cutclip%2Fcutclip?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fone.cutclip%2Fcutclip?ref=badge"><img src="https://glimind.com/badge/mcp-registry%2Fone.cutclip%2Fcutclip.svg" alt="MCP server status"></a>
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:3de07a01efcca741…, first seen 2026-11-17, included at leaf 319180 of 384,037. Version history · verify what your client received.
Compare: most reliable media 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?ref=install-server
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp?ref=install-server"
}
}
}
A free Glimind key lets your agent check whether a server works right now before it calls it, and switch to a live one when it doesn't. No signup, no card.
As of 2026-11-22 14:48 UTC, the CutClip.one MCP server is up with a Glimind reliability score of 90/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
CutClip.one MCP server advertises 111 tools, including asset.capture_frame, asset.get, asset.list, asset.replace_placeholder, asset.upload.
Point your MCP client at this streamable-http endpoint: https://cutclip.one/api/mcp
Glimind scanned all 111 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.