Everpop

What the everpop MCP server does

The everpop MCP server is described as a video-to-YouTube-Shorts workflow. It takes video material, creates clips, and publishes those clips as YouTube Shorts. It also produces receipts tied to two measurement points: 48 hours and 7 days.

The key use case is an agent workflow that needs more than clip creation alone. The result includes publication and later measured receipts, giving the workflow defined checkpoints after the Short is published. The supplied description does not specify what each receipt contains, how measurements are calculated, or whether receipts are returned as files, structured responses, or another format.

Tools and capabilities

Based on the available listing, the everpop MCP server supports these capabilities:

• Clip videos into Short-form outputs.
• Publish the resulting clips as YouTube Shorts.
• Provide measured receipts at 48-hour and 7-day checkpoints.

No README is available for this listing, so the names, parameters, return schemas, and invocation details of the MCP tools are not documented here. The description also does not identify supported source video formats, editing controls, YouTube account requirements, publishing options, or receipt fields.

How it works

The documented flow has three broad stages. Video is first clipped into a Short, the resulting clip is published to YouTube as a Short, and the workflow then supplies measured receipts associated with the 48-hour and 7-day marks. The available material does not explain whether these stages run automatically, whether an agent must approve publication, or how the server handles failed uploads or incomplete measurements.

This makes the everpop MCP server most relevant when a developer wants an MCP-based workflow centered on publishing Shorts and checking results on fixed time horizons. It is less suitable for evaluation of detailed editing features, analytics definitions, or operational behavior until those details are documented.

Limitations and notes

The repository README is unavailable in the supplied material. As a result, installation commands, environment variables, licensing, authentication setup, MCP transport, client compatibility, tool schemas, rate limits, supported media inputs, and error handling cannot be confirmed. The source description confirms YouTube Shorts publication and receipts measured at 48 hours and 7 days, but it does not define the metrics included in those receipts.

Before adoption, verify how video is supplied, which YouTube credentials are required, what “measured” means for each receipt, and whether the 48-hour and 7-day checks are scheduled by the server or initiated by the calling workflow.