Remote MCP · Endpoint

Podcast Parser MCP server

No. Podcast Parser answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://gateway.pipeworx.io/podcast-parser/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/podcast-parser
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
166 ms
Tools exposed
52 tools
Uptime, last 30 days
94.4% from 18 checks
Described by its publisher as
podcast-parser (CanonCannon) — what gets repeated across 162 tracked podcasts.
Website
https://pipeworx.io/packs/podcast-parser
Repository
https://github.com/pipeworx-io/mcp-podcast-parser
Listing
From the official MCP registry (active).
Recent checks of Podcast Parser
CheckedResultHandshake
1 hour agoHandshake completed166 ms
20 hours agoHandshake completed129 ms
2 days agoHandshake completed115 ms
3 days agoHandshake completed125 ms
4 days agoHandshake completed136 ms
5 days agoHandshake completed117 ms
6 days agoHandshake completed206 ms
8 days agoHandshake completed126 ms
11 days agoHandshake completed93 ms
13 days agoHandshake completed68 ms
16 days agoHandshake completed75 ms
18 days agoHandshake completed65 ms
20 days agoHandshake completed90 ms
22 days agoHandshake completed65 ms
24 days agoFailed - the request timed out—
26 days agoHandshake completed65 ms
27 days agoHandshake completed71 ms
29 days agoHandshake completed77 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

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