Remote MCP · Endpoint

Trends API MCP server

No. Trends API answered an MCP handshake 6 hours ago.

UpLast checked 6 hours ago

Server URL

https://api.trendsapi.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.trendsapi/trends
Transport
Streamable HTTP
Protocol negotiated
2025-03-26
Handshake latency
99 ms
Tools exposed
Not measured yet
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Trend data from Google, TikTok, Amazon, Reddit, YouTube, Steam, npm and more as JSON
Listing
From the official MCP registry (active).
Recent checks of Trends API
CheckedResultHandshake
6 hours agoHandshake completed99 ms
2 days agoHandshake completed99 ms
4 days agoHandshake completed91 ms
5 days agoHandshake completed173 ms
7 days agoHandshake completed107 ms
8 days agoHandshake completed98 ms
9 days agoHandshake completed181 ms
12 days agoHandshake completed97 ms
13 days agoHandshake completed89 ms
15 days agoHandshake completed86 ms
16 days agoHandshake completed95 ms
17 days agoHandshake completed129 ms
18 days agoHandshake completed156 ms
19 days agoHandshake completed87 ms
20 days agoHandshake completed359 ms
21 days agoHandshake completed91 ms
22 days agoHandshake completed112 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 Trends API and makes no claim about it beyond what these checks measured.