Remote MCP · Endpoint

star365 HQ MCP server

No. star365 HQ answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.star365.site/mcp

The last check completed an MCP handshake.

Registry name
site.star365/hq
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
516 ms
Tools exposed
15 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Keyless web, GitHub, YouTube and Reddit search and read. Delegated shop, booking and signup.
Listing
From the official MCP registry (active).
Recent checks of star365 HQ
CheckedResultHandshake
1 hour agoHandshake completed516 ms
2 days agoHandshake completed557 ms
4 days agoHandshake completed513 ms
5 days agoHandshake completed498 ms
7 days agoHandshake completed500 ms
8 days agoHandshake completed497 ms
9 days agoHandshake completed503 ms
12 days agoHandshake completed496 ms
13 days agoHandshake completed574 ms
15 days agoHandshake completed495 ms
16 days agoHandshake completed499 ms
18 days agoHandshake completed503 ms
19 days agoHandshake completed501 ms
20 days agoHandshake completed514 ms
21 days agoHandshake completed507 ms
21 days agoHandshake completed508 ms
23 days agoHandshake completed499 ms

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

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