Remote MCP · Endpoint

Trend MCP server

No. Trend answered an MCP handshake 42 minutes ago.

UpLast checked 42 minutes ago

Server URL

https://trend.ondo.sh/mcp

The last check completed an MCP handshake.

Registry name
sh.ondo/trend
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
242 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
What rose on GitHub and in Korean shopping search each day, as published on trend.ondo.sh
Listing
From the official MCP registry (active).
Recent checks of Trend
CheckedResultHandshake
42 minutes agoHandshake completed242 ms
3 days agoHandshake completed221 ms
13 days agoHandshake completed207 ms
13 days agoHandshake completed202 ms
15 days agoHandshake completed580 ms
15 days agoHandshake completed208 ms
17 days agoHandshake completed205 ms
18 days agoHandshake completed202 ms
18 days agoHandshake completed209 ms
20 days agoHandshake completed288 ms
22 days agoHandshake completed332 ms
25 days agoHandshake completed204 ms
27 days agoHandshake completed205 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 Trend and makes no claim about it beyond what these checks measured.