Back to MCP servers
● healthy

YouTube transcripts, comment sentiment and the moments viewers react to, plus channel stats.

Transport
streamable-http
Auth
—
Cost
—
Protocol revision
—

MCP readiness

D · 43/100

Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here C+, 56.7/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ

Valid MCP handshake 0/10 Handshake needs credentials (HTTP 401); not readable anonymously.
Live MCP endpoint 15/25 Endpoint requires authentication or payment (393 ms).
Protocol revision 0/10 No protocol revision reported by initialize.
Signed descriptor n/a No MCP standard defines a signed server descriptor.
Uptime (30 days) 15/15 31/31 probes succeeded over 30 days (100%).
Tool declaration 0/10 No tools listed by tools/list.
Verified identity 7/10 Namespace verified by the official MCP Registry (GitHub or DNS proof at publish time).
Freshness + modern flags 2/5 seen within 30 days.
Auth declaration 0/5 How to authenticate is not stated.
Applicable criteria total 90 points, scaled to 100.
Responsiveness: Responsive (393 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).
Measured 2026-11-11.
Nine criteria, the same as the A2A readiness score, read from our daily MCP probe (initialize + tools/list) and 30-day probe history. No MCP standard defines a signed server descriptor, so that criterion is n/a and the other 90 points are scaled to 100. Grades: A>=90, B>=75, C>=60, D>=40, F<40. Display only: search order uses the quality grade.

Compared with peers

Against 53,021 reachable MCP servers in our daily snapshot (2026-11-12 01:39 UTC). Display only; it does not change search order.

Readiness
Higher than 15% of peers
This listing 43 · peer median 81
Latency
Faster than 86% of peers
This listing 125 ms · peer median 326 ms

Where it loses the most points, and how to win them back

  • Valid MCP handshake −10 — Complete the MCP handshake without errors.
    Now: Handshake needs credentials (HTTP 401); not readable anonymously.
  • Live MCP endpoint −10 — Answer initialize and tools/list at the declared endpoint.
    Now: Endpoint requires authentication or payment (393 ms).
  • Protocol revision −10 — Support the current protocol revision.
    Now: No protocol revision reported by initialize.

How many agent tools actually work · All statistics

Adoption signals

Public signals from outside this directory, shown for context. They do not change search order or grades.

GitHub
★ 2 · 0 forks
last push 2026-10-24

Listed in

Directories this entry was found in.

mcp-registry since 2026-10-13

How to connect

MCP endpoint (streamable-http)
https://mcp.apify.com?tools=fetch-actor-details,tubetext/youtube-transcript-fast,tubetext/youtube-shorts-scraper,tubetext/youtube-tiktok-comments-api,tubetext/youtube-channel-analytics,tubetext/socialblade-scraper,tubetext/shot-by-shot-video-analysis
JSON-RPC initialize probe
curl -X POST https://mcp.apify.com?tools=fetch-actor-details,tubetext/youtube-transcript-fast,tubetext/youtube-shorts-scraper,tubetext/youtube-tiktok-comments-api,tubetext/youtube-channel-analytics,tubetext/socialblade-scraper,tubetext/shot-by-shot-video-analysis \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'
Homepage
https://apify.com/tubetext/youtube-transcript-fast
Source code
https://github.com/LMSlay/tubetext-mcp