OpusClip MCP server

Checked 2026-09-07. Alive: yes. Handshake: gated.

Category: media-design. API and field schema.

Facts
idopus-pro--opusclip-mcp
nameOpusClip
registry_nameio.github.opus-pro/opusclip
repo_urlhttps://github.com/opus-pro/opusclip-mcp
endpoint_urlhttps://mcp.opus.pro/mcp
transportmixed
aliveyes
liveness_reasonnot available
check_reachableyes
check_recent_commityes
check_installableyes
handshake_statusgated
handshake_checked_at2026-09-07T18:09:14Z
handshake_protocol_versionnot available
handshake_auth_hintBearer error="invalid_request", resource_metadata="https://mcp.opus.pro/mcp/.well-known/oauth-protected-resource"
handshake_auth_discoverableresource_metadata
handshake_failure_layernone
handshake_latency_ms655
handshake_tools_statenot available
handshake_tool_countnot available
maintenance_statusactive
last_commit_at2026-09-04T03:17:48Z
categorymedia-design
license_spdxMIT
How to install or connect

Connect your MCP client to https://mcp.opus.pro/mcp.

What the checks mean

alive combines the applicable repository, package, and endpoint checks. A null result is not verifiable, not a failure. The MCP handshake is a separate structural probe and is not a security audit. Read the methodology.