Remote MCP · Endpoint

News by Hottub MCP server

No. News by Hottub answered an MCP handshake 6 hours ago.

UpLast checked 6 hours ago

Server URL

https://hottub.news/mcp

The last check completed an MCP handshake.

Registry name
news.hottub/hottub-news
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
103 ms
Tools exposed
12 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
World news for agents: stories across languages, with prospects ready for CRM by Hottub. No key.
Listing
From the official MCP registry (active).
Recent checks of News by Hottub
CheckedResultHandshake
6 hours agoHandshake completed103 ms
9 days agoHandshake completed211 ms
10 days agoHandshake completed162 ms
11 days agoHandshake completed195 ms
12 days agoHandshake completed127 ms
14 days agoHandshake completed186 ms
15 days agoHandshake completed166 ms
15 days agoHandshake completed97 ms
17 days agoHandshake completed264 ms
19 days agoHandshake completed154 ms
22 days agoHandshake completed272 ms
24 days agoHandshake completed227 ms
26 days agoHandshake completed156 ms
28 days agoHandshake completed55 ms

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

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