Remote MCP · Endpoint

Faceabot YouTube transcript MCP server

No. Faceabot YouTube transcript answered an MCP handshake 42 minutes ago.

UpLast checked 42 minutes ago

Server URL

https://youtube.faceabot.com/mcp

The last check completed an MCP handshake.

Registry name
com.faceabot/youtube
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
3.06 s
Tools exposed
2 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
What is said in a YouTube video: transcript with timestamps, title and channel. Free, no key.
Listing
From the official MCP registry (active).
Recent checks of Faceabot YouTube transcript
CheckedResultHandshake
42 minutes agoHandshake completed3.06 s
3 days agoHandshake completed389 ms
12 days agoHandshake completed96 ms
12 days agoHandshake completed47 ms
14 days agoHandshake completed73 ms
15 days agoHandshake completed63 ms
16 days agoHandshake completed268 ms
17 days agoHandshake completed117 ms
18 days agoHandshake completed76 ms
19 days agoHandshake completed74 ms
22 days agoHandshake completed87 ms
25 days agoHandshake completed59 ms
27 days agoHandshake completed341 ms

The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 13 responding of 13.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with Faceabot YouTube transcript and makes no claim about it beyond what these checks measured.