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
90 ms
Tools exposed
44 tools
Uptime, last 30 days
94.1% from 17 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 completed90 ms
2 days agoHandshake completed65 ms
4 days agoFailed - the request timed out—
5 days agoHandshake completed65 ms
7 days agoHandshake completed71 ms
8 days agoHandshake completed77 ms
9 days agoHandshake completed58 ms
12 days agoHandshake completed93 ms
13 days agoHandshake completed50 ms
15 days agoHandshake completed100 ms
17 days agoHandshake completed41 ms
18 days agoHandshake completed43 ms
19 days agoHandshake completed42 ms
20 days agoHandshake completed109 ms
21 days agoHandshake completed37 ms
21 days agoHandshake completed51 ms
23 days agoHandshake completed68 ms

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

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.