Remote MCP · Endpoint
Google Trends API MCP server
No. Google Trends API answered an MCP handshake 2 hours ago.
UpLast checked 2 hours ago
Server URL
https://google-trends.api.trendsapi.ai/mcp
The last check completed an MCP handshake.
- Registry name
- ai.trendsapi/google-trends
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-03-26
- Handshake latency
- 158 ms
- Tools exposed
- Not measured yet
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- Google Trends search interest over time with growth metrics. Free key at trendsapi.ai
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Handshake completed | 158 ms |
| 2 days ago | Handshake completed | 88 ms |
| 4 days ago | Handshake completed | 196 ms |
| 6 days ago | Handshake completed | 80 ms |
| 7 days ago | Handshake completed | 118 ms |
| 9 days ago | Handshake completed | 108 ms |
| 10 days ago | Handshake completed | 132 ms |
| 11 days ago | Handshake completed | 207 ms |
| 14 days ago | Handshake completed | 83 ms |
| 15 days ago | Handshake completed | 85 ms |
| 17 days ago | Handshake completed | 120 ms |
| 18 days ago | Handshake completed | 130 ms |
| 19 days ago | Handshake completed | 145 ms |
| 20 days ago | Handshake completed | 112 ms |
| 21 days ago | Handshake completed | 91 ms |
| 22 days ago | Handshake completed | 94 ms |
| 23 days ago | Handshake completed | 115 ms |
| 24 days ago | Handshake completed | 119 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 18 responding of 18.
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 Google Trends API and makes no claim about it beyond what these checks measured.