mcpbeat

ClipForge MCP Server

io.github.chriphil70/clipforge
answering

ClipForge is answering right now. Last checked 13 min ago.

Trim, watermark, extract audio, and convert video to 9:16 vertical via API or MCP tools.

Uptime history 2 hours of history
2 hours agonow
100.0%
Uptime 24h
5 of 5 checks
—
Tools
hidden behind auth
505 ms
Response time
average over 24h
API key or OAuth
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 13 min ago.

run in your terminal
claude mcp add clipforge --transport http https://budding-retrograde--clipforge.apify.actor/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "clipforge": {
      "url": "https://budding-retrograde--clipforge.apify.actor/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.clipforge]
url = "https://budding-retrograde--clipforge.apify.actor/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "clipforge": {
      "url": "https://budding-retrograde--clipforge.apify.actor/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "clipforge": {
      "url": "https://budding-retrograde--clipforge.apify.actor/mcp"
    }
  }
}

This endpoint answered with an authorization challenge — the server is running, but you need an API key or OAuth to use it.

Endpoints

URLTransportStateLatencyChecked
https://budding-retrograde--clipforge.apify.actor/mcp streamable-http needs key 452 ms 13 min ago

ClipForge — questions

Answers built from our own checks of this server.

Why is there no tool list for ClipForge?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is ClipForge working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 5 of 5 checks got a reply (100.0%), average response time 505 ms. The bar chart above shows every period we have measured.
How do I connect ClipForge?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own key or an OAuth login: it refuses anonymous clients.
Does ClipForge need an API key?
Yes. Every time we knock, ClipForge answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.
How fast is ClipForge?
It answers our handshake in 505 ms on average, which is faster than 23% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.