mcpbeat

YouTube Video Summarizer (pay-per-call) MCP Server

io.github.JonTelep/summarize-vid
answering

YouTube Video Summarizer (pay-per-call) is answering right now. Last checked 9 min ago. It exposes 3 tools.

Summarize YouTube videos or fetch transcripts. Pay-per-call via x402 (USDC on Base), no account.

Uptime history 43 hours of history
43 hours agonow
100.0%
Uptime 24h
91 of 91 checks
3
Tools
read from the server
394 ms
Response time
average over 24h
open, no key
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 9 min ago.

run in your terminal
claude mcp add summarize-vid --transport http https://mcp.sumvid.app/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "summarize-vid": {
      "url": "https://mcp.sumvid.app/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.summarize-vid]
url = "https://mcp.sumvid.app/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "summarize-vid": {
      "url": "https://mcp.sumvid.app/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "summarize-vid": {
      "url": "https://mcp.sumvid.app/mcp"
    }
  }
}

Available tools 3

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

new
list_new_channel_videos
New videos on a YouTube channel since your last poll — stateless channel monitoring, no accounts or webhooks. Pass a channel URL, @handle, or channel id, plus an optional cursor (`since_video_id` or `since`, an ISO 8601 timezone-aware timestamp) from your last call. Returns new video ids/titles/publish times, newest first, plus `newest_video_id` to use as your next cursor. Pay-per-call via x402 (USDC on Base), no account or API key. An unresolvable channel or a naive `since` timestamp returns an error and is not charged.
summarize
summarize_youtube_video
Summarize a YouTube video with Claude and return the summary text, in any of 100+ output languages (`language` param, BCP-47). Pay-per-call via x402 (USDC on Base) — no account or API key. Cheaper than pulling the full transcript into your own context. A bad URL or a video without captions returns an error and is not charged.
youtube
get_youtube_transcript
Fetch the raw transcript text of a YouTube video (no model run — the cheaper SKU), in any of 100+ languages (`language` param, BCP-47). Pay-per-call via x402 (USDC on Base), no account. A video without captions returns an error and is not charged.

Endpoints

URLTransportStateLatencyChecked
https://mcp.sumvid.app/mcp streamable-http answering 371 ms 9 min ago

YouTube Video Summarizer (pay-per-call) — questions

Answers built from our own checks of this server.

What can YouTube Video Summarizer (pay-per-call) do?
It exposes 3 tools, read directly from the server on our last check. Among them: get_youtube_transcript, list_new_channel_videos, summarize_youtube_video. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is YouTube Video Summarizer (pay-per-call) working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 394 ms. The bar chart above shows every period we have measured.
How do I connect YouTube Video Summarizer (pay-per-call)?
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.
Does YouTube Video Summarizer (pay-per-call) need an API key?
No. YouTube Video Summarizer (pay-per-call) completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 3 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is YouTube Video Summarizer (pay-per-call)?
It answers our handshake in 394 ms on average, which is faster than 35% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.