Remote MCP · Endpoint

Pod Researcher MCP server

No. Pod Researcher answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://gateway.pipeworx.io/pod-researcher/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/pod-researcher
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
69 ms
Tools exposed
48 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
pod-researcher — podcast prospecting for guest booking and sponsorship.
Listing
From the official MCP registry (active).
Recent checks of Pod Researcher
CheckedResultHandshake
2 hours agoHandshake completed69 ms
2 days agoHandshake completed89 ms
4 days agoHandshake completed62 ms
6 days agoHandshake completed66 ms
8 days agoHandshake completed56 ms
9 days agoHandshake completed61 ms
11 days agoHandshake completed58 ms
12 days agoHandshake completed65 ms
14 days agoHandshake completed44 ms
16 days agoHandshake completed45 ms
17 days agoHandshake completed79 ms
19 days agoHandshake completed40 ms
20 days agoHandshake completed918 ms
21 days agoHandshake completed1.13 s
22 days agoHandshake completed2.46 s

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

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