Remote MCP · Endpoint

AIHOT MCP server

No. AIHOT answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://aihot.news/api/mcp

The last check completed an MCP handshake.

Registry name
io.github.KKKKhazix/aihot
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
314 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Chinese AI news: search topics, explore hot events, and read daily, weekly and monthly briefs.
Listing
From the official MCP registry (active).
Recent checks of AIHOT
CheckedResultHandshake
2 hours agoHandshake completed314 ms
1 day agoHandshake completed1.32 s
3 days agoHandshake completed274 ms
3 days agoHandshake completed768 ms
4 days agoHandshake completed764 ms
5 days agoHandshake completed1.20 s
7 days agoHandshake completed2.87 s
10 days agoHandshake completed717 ms
12 days agoHandshake completed1.14 s
15 days agoHandshake completed718 ms
17 days agoHandshake completed366 ms
19 days agoHandshake completed258 ms
21 days agoHandshake completed984 ms
23 days agoHandshake completed2.18 s
25 days agoHandshake completed756 ms

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