Remote MCP · Endpoint

Track Podcasts MCP server

No. Track Podcasts answered an MCP handshake 45 minutes ago.

UpLast checked 45 minutes ago

Server URL

https://trackpodcasts.com/api/mcp

The last check completed an MCP handshake.

Registry name
com.trackpodcasts/podcast-sponsors
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
5.61 s
Tools exposed
5 tools
Uptime, last 30 days
84.6% from 13 checks
Described by its publisher as
Who sponsors which podcasts, from transcribed ad reads. Free: 10 calls/day with no key, 25 with one.
Listing
From the official MCP registry (active).
Recent checks of Track Podcasts
CheckedResultHandshake
45 minutes agoHandshake completed5.61 s
3 days agoHandshake completed105 ms
12 days agoHandshake completed73 ms
13 days agoFailed - the request timed out—
14 days agoHandshake completed136 ms
15 days agoHandshake completed255 ms
16 days agoHandshake completed57 ms
17 days agoHandshake completed93 ms
18 days agoHandshake completed92 ms
19 days agoFailed - the request timed out—
22 days agoHandshake completed103 ms
25 days agoHandshake completed162 ms
27 days agoHandshake completed1.10 s

The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 11 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 Track Podcasts and makes no claim about it beyond what these checks measured.