Remote MCP · Endpoint

PodLearn MCP server

No. PodLearn answered an MCP handshake 20 hours ago.

UpLast checked 20 hours ago

Server URL

https://httiyebjgxxwtgggkpgw.supabase.co/functions/v1/mcp-server-streamable

The last check completed an MCP handshake.

Registry name
io.github.blutrich/podlearn
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
638 ms
Tools exposed
25 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Search 4M+ podcasts & YouTube, transcribe any episode, search transcripts, generate AI lessons.
Listing
From the official MCP registry (active).
Recent checks of PodLearn
CheckedResultHandshake
20 hours agoHandshake completed638 ms
11 days agoHandshake completed628 ms
11 days agoHandshake completed792 ms
12 days agoHandshake completed543 ms
14 days agoHandshake completed601 ms
15 days agoHandshake completed621 ms
15 days agoHandshake completed2.21 s
16 days agoHandshake completed464 ms
18 days agoHandshake completed703 ms
20 days agoHandshake completed594 ms
22 days agoHandshake completed742 ms
25 days agoHandshake completed599 ms
27 days agoHandshake completed609 ms
29 days agoHandshake completed505 ms

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

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