MCP YouTube Transcript
An MCP server retrieving transcripts of YouTube videos
제작자가 쓴 설명(영어 원문)
Turns any URL into SEO metadata, contacts, tech stack, and AI-ready Markdown, in one call.
이 세 가지는 절대 하나의 점수로 합치지 않아요. 의견, 측정, 인기는 서로 다른 것이니까요.
이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.
쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.
x-api-host, x-api-key비밀로 표시된 값은 내 계정의 열쇠예요. 절대 다른 사람과 공유하거나 채팅에 붙여 넣지 마세요.
필요한 것
어떤 앱을 쓰세요?
위에서 앱을 고르세요. 기억해 두었다가 다음부터는 버튼에 “…에 설치”라고 표시해요.
이 주소는 요청 header에 키가 필요한데, 커넥터 추가 메뉴에서는 넣을 수 없어요. 대신 Claude Code, Cursor, VS Code를 쓰세요.
터미널에서 이 명령어를 실행하세요
claude mcp add --transport http rapidapi-metadata-extractor https://mcp.rapidapi.com --header 'x-api-host: your-value' --header 'x-api-key: your-value'실행하기 전에 빈 값을 채워 주세요.
프로젝트의 .cursor/mcp.json 또는 ~/.cursor/mcp.json에 붙여 넣으세요
{
"mcpServers": {
"rapidapi-metadata-extractor": {
"url": "https://mcp.rapidapi.com",
"headers": {
"x-api-host": "your-value",
"x-api-key": "your-value"
}
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
프로젝트의 .vscode/mcp.json에 붙여 넣으세요
{
"servers": {
"rapidapi-metadata-extractor": {
"type": "http",
"url": "https://mcp.rapidapi.com",
"headers": {
"x-api-host": "your-value",
"x-api-key": "your-value"
}
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
이 주소는 요청 header에 키가 필요한데, 커넥터 추가 메뉴에서는 넣을 수 없어요. 대신 Claude Code, Cursor, VS Code를 쓰세요.
선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.
x-api-host 필수 HTTP headerx-api-key 비밀 필수 HTTP header이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.
아직 이 서버의 도구 목록을 읽지 않았어요. 엔드포인트는 차례대로 돌아가며 점검해요.
누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 6일 점검
레지스트리 이름이 GitHub 계정 JosejuX 기준으로 확인되었고, 이 계정이 저장소를 소유하고 있어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
아직 점검하지 않았어요. 엔드포인트는 차례대로 돌아가며 점검해요
아직 점검하지 않았어요. 엔드포인트는 차례대로 돌아가며 점검해요
아직 점검하지 않았어요. 엔드포인트를 점검할 때 도구 목록을 읽어요
레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.
해당하는 기본 점검 1개 중 1개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.
입력해야 할 값: x-api-host, x-api-key
제작자의 클라우드에서 실행돼요. 설치 없이 인터넷으로 연결하지만, 보내는 내용은 제작자의 서버를 거쳐요.
GitHub 저장소는 마지막으로 – 변경됐고, 최신 버전(1.0.0)은 3개월 전 레지스트리에 올라왔어요.
Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. URL로 연결되기 때문에, 원격 MCP 서버를 지원하는 앱(예: 개발자 모드의 ChatGPT)에서도 쓸 수 있어요.
같은 카테고리에는: MCP YouTube Transcript, Google Analytics MCP, BibiGPT YouTube Video Summarizer
같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.
카드 보는 법:★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i
An MCP server retrieving transcripts of YouTube videos
GA4 MCP server for AI agents: schema discovery, server-side aggregation, analysis-ready defaults.
AI video summarizer: summarize and transcribe YouTube, Bilibili, TikTok and podcast videos.
제작자의 저장소에서 쓰인 그대로 가져왔어요. PopNx MCP가 검토하거나 보증한 내용이 아니에요. HTML, 이미지, 스크립트는 제거했어요. 링크를 누르면 이 사이트를 벗어나요.
Extract SEO, technologies, contacts, products, social profiles, security signals, and AI-ready content from any public website — with one API call.
Free to try. No signup required for the demo.
🎮 Try the Live Demo • 🔑 Get Free API Key on RapidAPI • 📖 API Documentation • ⚡ Code Examples
Paste a URL, get real results in seconds — webmetadataextractor.com runs the actual pipeline live, no API key needed. Try your own site, or one of these:
/demo/extractis the same no-key route the live demo page above uses (see "Honest Limitations" — it's rate-limited per IP, not a documented/stable API endpoint). For integrating in code, use/api/v1/extractwith a RapidAPI key as shown below.
Or call it directly (swap in your key from RapidAPI for production use):
curl "https://web-metadata-and-contact-extractor.p.rapidapi.com/api/v1/extract?url=github.com" \
-H "X-RapidAPI-Key: YOUR_KEY" -H "X-RapidAPI-Host: web-metadata-and-contact-extractor.p.rapidapi.com"
| Use case | What you get | |
|---|---|---|
| 🧲 | Lead generation | Find companies on a given tech stack (e.g. Shopify) with a weak SEO score, then prioritize outreach. |
| 🤖 | AI agents | Feed markdown_content and structured JSON straight into an agent or RAG pipeline as clean, LLM-ready context for any URL. |
| 🔎 | SEO audits | Run the 14-point on-page score plus graded security headers across a URL list, on a schedule. |
| 🛒 | Ecommerce | Pull product name/price/currency/availability/brand from Schema.org, OpenGraph, and Microdata — cross-checked for conflicts. |
| 🕵️ | Competitive intelligence | Track a competitor's tech stack, metadata, and product data over time by re-checking the same URL list. |
Example: lead generation — flag Shopify sites with a weak SEO score
import requests
RAPIDAPI_KEY = "YOUR_RAPIDAPI_KEY" HEADERS = { "X-RapidAPI-Key": RAPIDAPI_KEY, "X-RapidAPI-Host": "web-metadata-and-contact-extractor.p.rapidapi.com", } BASE = "https://web-metadata-and-contact-extractor.p.rapidapi.com/api/v1/extract"
for url in ["shop-a.com", "shop-b.com", "shop-c.com"]: data = requests.get(BASE, headers=HEADERS, params={"url": url}).json() if "Shopify" in data["detected_technologies"] and data["seo_score_percentage"] < 60: print(f"{url}: Shopify + {data['seo_score_percentage']}% SEO -> outreach candidate")
</details>
Example: AI agent tool call — clean Markdown for any URL
import requests
def read_url_as_markdown(url: str) -> str: """Tool function an LLM agent can call to read any public webpage.""" resp = requests.get( "https://web-metadata-and-contact-extractor.p.rapidapi.com/api/v1/markdown", headers={"X-RapidAPI-Key": "YOUR_KEY", "X-RapidAPI-Host": "web-metadata-and-contact-extractor.p.rapidapi.com"}, params={"url": url}, ).json() return resp["markdown_content"]
</details>
| Feature | Detail |
|---|---|
| ⚡ Ultra-Fast Performance | ~150–300ms live fetch. Powered by selectolax (C-Lexbor parser), Rust ORJSON, uvloop, HTTP/2 multiplexing, async DNS (non-blocking), 5-min DNS TTL cache. |
| 🧠 Adaptive SPA Byte Limit | Auto-detects React, Next.js, Vue, Angular, Nuxt, Svelte, Gatsby, Remix, Astro and expands download to 256 KB for richer data extraction. Static sites stay at 64 KB. |
| 🛡️ IP-Pinned Anti-SSRF Shield | DNS resolved once, IP validated against private/loopback/cloud-metadata ranges, connection pinned to IP with TLS SNI. Eliminates DNS Rebinding & Redirect SSRF. |
| 🎯 Rich SEO & OpenGraph Metadata | Title, Description, OG Image, OG Type, OG URL, OG Video, Favicon, Canonical URL, Language, Author, Theme Color, Robots directive, hreflang tags, H1 headings, image count. |
| 📧 Contact Extractor | Public emails and phone numbers with smart DOM cleaning to eliminate false positives. Phones are additionally normalized (phone_details) via libphonenumber — E.164 format, ISO country code, and possible/valid flags — for numbers that include a country code; numbers without one aren't guessed. |
| 📲 Social Profile Finder | Auto-detects 20 platforms: Twitter/X, LinkedIn, Facebook, Instagram, GitHub, YouTube, Telegram, TikTok, Threads, Bluesky, Mastodon, Discord, Reddit, Pinterest, Medium, GitLab, Vimeo, Dribbble, Behance, Snapchat. |
| 🛠️ 40+ Tech Stack Detector | WordPress, Shopify, WooCommerce, Webflow, React, Next.js, Vue, Angular, Svelte, TailwindCSS, Stripe, GA4, and more across CMS/ecommerce, frameworks, and analytics/payment/hosting categories. |
| 📦 Schema.org JSON-LD + Product Parser | Parses all structured data schemas AND auto-extracts Product price, currency, availability, brand, rating and review count. |
| 🎯 Multi-Source Data Quality & Conflict Detection | Product price/currency/availability/brand are cross-checked across three distinct structured encodings — JSON-LD, OpenGraph's product extension, and schema.org Microdata. product_field_confidence reports a per-field confidence score (more of these encodings agreeing = higher confidence, same philosophy as tech-stack detection) and which source won. When they genuinely disagree, a SOURCE_CONFLICT warning names the field, every value found, and which one was chosen and why. A top-level quality object (score, rendered: false, sources_used, warnings) summarizes response trustworthiness for programmatic consumers. Caveat: these three encodings often come from the same underlying product record on a given site, so agreement means "internally consistent," not "independently verified" — see Honest Limitations below. |
| 📊 On-Page SEO Health Audit Score | 14-point automated on-page technical SEO diagnostic (0–100%) with actionable warnings list, plus a structured seo_checks breakdown (check id, passed, severity, evidence) for programmatic use. |
| 🔗 Internal vs External Link Classifier | Categorizes up to 100 hyperlinks per page. |
| 🤖 AI & LLM Clean Markdown Reader | Converts article text to clean Markdown for ChatGPT, Claude, RAG, and AI agents. Includes word count and reading time. |
| 📡 RSS / Atom Feed Discovery | Auto-discovers RSS and Atom feed URLs. |
| 🔒 Graded Security Headers Audit | HSTS, CSP, X-Frame-Options, X-Content-Type-Options, Referrer Policy, Permissions Policy — each graded missing/weak/reasonable/strong from its actual value (e.g. a CSP with unsafe-inline scores as weak, not as "present = full credit"), not just presence, rolled into the percentage score. /api/v1/security additionally returns security_header_grades with the per-header breakdown. |
| 🚀 15-Min In-Memory Cache | Cached responses served in < 0.01 ms server-side processing time. |
| ⚡ Multi-Worker + Auto-Reconnect Redis | uvicorn --workers N multi-process cluster (set via the WORKERS env var; gunicorn is a listed dependency for anyone who prefers it as the process manager, but the shipped Dockerfile launches uvicorn directly). Distributed rate limiting via Redis with startup ping validation, automatic reconnect every 30s, and immediate degraded_fallback status propagation to /health/details. |
| 🔒 Split `/health` + `/health/details` | Minimal public liveness probe (/health). Full operational details (Redis mode, status, engine) secured via HEALTH_DETAILS_SECRET header on /health/details. |
| 🧯 Per-Host Circuit Breaker | Trips after repeated timeouts/connection failures/5xx to one host, fails fast during the cooldown window instead of burning the full connect+read timeout budget on every request, and probes recovery automatically (never trips on ordinary 4xx). |
| 🧩 Request Single-Flight + DNS Coalescing | Concurrent requests for the same URL (or the same hostname's DNS lookup) share one in-flight fetch instead of hammering the origin N times. |
| 🩹 Negative-Result Cache | Short-TTL caching of recent upstream failures (DNS/timeout/5xx) so a broken target fails fast instead of repeating the same slow failure for every request during an outage. |
| 🧱 Adaptive Byte-Limit Hardening | Streaming byte cap is enforced on the *decoded* chunk, closing a decompression-bomb gap where a small gzip/br payload could otherwise expand to megabytes in a single read. Response headers are also count- and size-bounded. |
| 🏷️ Structured Error Codes | Every error response carries a machine-readable error.code / error.retryable object (e.g. SSRF_BLOCKED, UPSTREAM_TIMEOUT, CIRCUIT_OPEN) alongside the existing detail string — fully additive, v1 contract unchanged. |
| 📈 Prometheus Metrics + Structured JSON Logs | /metrics exposes request/cache/SSRF/circuit-breaker/rate-limit counters and latency histograms. Every log line is a JSON object with request_id for end-to-end tracing; known-sensitive fields are redacted automatically. |
| 🧠 Confidence-Scored Tech Detection | /api/v1/tech-stack now also returns technology_details: per-technology confidence score, matched evidence, and category (cms/ecommerce/framework/analytics/payment/hosting/…), alongside the original flat list. |
| 📦 Deeper Product & JSON-LD Parsing | Traverses @graph and top-level JSON-LD arrays (not just top-level objects), extracting SKU, MPN, GTIN/ISBN, seller, condition, price range, and images. |
| 🔎 Unicode-Aware SEO & Keywords | Keyword extraction now matches non-ASCII scripts correctly (accented/Cyrillic/etc. content), and the SEO audit adds lang attribute, viewport, noindex, multi-H1, Twitter Card, and structured-data checks. |
| ⚡ Lazy Extraction Per Endpoint | Specialized endpoints only run the extractors they actually need instead of the full pipeline — `/sec
앞부분만 보여 드려요. 나머지는 저장소에서 읽어 보세요