Remote MCP · Endpoint

Quién Patrocina MCP server

No. Quién Patrocina answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://quienpatrocina.com/mcp

The last check completed an MCP handshake.

Registry name
com.quienpatrocina/quien-patrocina
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
315 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Which brands sponsor Spanish-language podcasts and YouTube channels in Spain and Latin America.
Listing
From the official MCP registry (active).
Recent checks of Quién Patrocina
CheckedResultHandshake
1 hour agoHandshake completed315 ms
3 days agoHandshake completed177 ms
12 days agoHandshake completed301 ms
13 days agoHandshake completed198 ms
15 days agoHandshake completed717 ms
15 days agoHandshake completed260 ms
17 days agoHandshake completed329 ms
18 days agoHandshake completed222 ms
18 days agoHandshake completed304 ms
20 days agoHandshake completed282 ms
22 days agoHandshake completed457 ms
25 days agoHandshake completed386 ms
27 days agoHandshake completed316 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 Quién Patrocina and makes no claim about it beyond what these checks measured.