Remote MCP · Endpoint
X (Twitter) Trends API MCP server
No. X (Twitter) Trends API answered an MCP handshake 11 hours ago.
UpLast checked 11 hours ago
Server URL
https://x-twitter.api.trendsapi.ai/mcp
The last check completed an MCP handshake.
- Registry name
- ai.trendsapi/x-twitter
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-03-26
- Handshake latency
- 144 ms
- Tools exposed
- Not measured yet
- Uptime, last 30 days
- 100% from 17 checks
- Described by its publisher as
- X trending topics and discussion volume over time. Free key at trendsapi.ai
- Website
- https://trendsapi.ai/trends
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 11 hours ago | Handshake completed | 144 ms |
| 2 days ago | Handshake completed | 110 ms |
| 4 days ago | Handshake completed | 137 ms |
| 5 days ago | Handshake completed | 145 ms |
| 7 days ago | Handshake completed | 120 ms |
| 8 days ago | Handshake completed | 94 ms |
| 9 days ago | Handshake completed | 114 ms |
| 12 days ago | Handshake completed | 143 ms |
| 13 days ago | Handshake completed | 139 ms |
| 15 days ago | Handshake completed | 124 ms |
| 16 days ago | Handshake completed | 139 ms |
| 17 days ago | Handshake completed | 155 ms |
| 19 days ago | Handshake completed | 143 ms |
| 19 days ago | Handshake completed | 126 ms |
| 20 days ago | Handshake completed | 103 ms |
| 21 days ago | Handshake completed | 139 ms |
| 23 days ago | Handshake completed | 121 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 X (Twitter) Trends API and makes no claim about it beyond what these checks measured.