Remote MCP · Endpoint

TranscriptYT MCP server

No. TranscriptYT answered an MCP handshake 46 minutes ago.

UpLast checked 46 minutes ago

Server URL

https://transcript-yt.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.rajdeep-automation/transcriptyt
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
76 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
YouTube transcripts for AI agents: text, JSON, SRT, or VTT in 150+ languages, with AI fallback.
Listing
From the official MCP registry (active).
Recent checks of TranscriptYT
CheckedResultHandshake
46 minutes agoHandshake completed76 ms
3 days agoHandshake completed109 ms
13 days agoHandshake completed1.79 s
13 days agoHandshake completed207 ms
15 days agoHandshake completed99 ms
16 days agoHandshake completed109 ms
17 days agoHandshake completed504 ms
18 days agoHandshake completed320 ms
18 days agoHandshake completed75 ms
20 days agoHandshake completed85 ms
22 days agoHandshake completed372 ms
25 days agoHandshake completed105 ms
27 days agoHandshake completed345 ms
30 days agoHandshake completed1.63 s

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

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 TranscriptYT and makes no claim about it beyond what these checks measured.