Remote MCP · Endpoint

PodLearn MCP server

No. PodLearn answered an MCP handshake 6 days ago.

UpLast checked 6 days ago

Server URL

https://podlearn.ai/mcp

The last check completed an MCP handshake.

Registry name
io.github.blutrich/podlearn
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
610 ms
Tools exposed
25 tools
Uptime, last 30 days
100% from 13 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
6 days agoHandshake completed610 ms
7 days agoHandshake completed619 ms
7 days agoHandshake completed455 ms
9 days agoHandshake completed972 ms
10 days agoHandshake completed410 ms
11 days agoHandshake completed726 ms
12 days agoHandshake completed855 ms
13 days agoHandshake completed662 ms
15 days agoHandshake completed500 ms
17 days agoHandshake completed737 ms
20 days agoHandshake completed650 ms
22 days agoHandshake completed481 ms
24 days agoHandshake completed690 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 PodLearn and makes no claim about it beyond what these checks measured.