Remote MCP · Endpoint
Competitor Tracking Trends MCP MCP server
No. Competitor Tracking Trends MCP answered an MCP handshake 2 hours ago.
UpLast checked 2 hours ago
Server URL
https://competitor-tracking.api.trendsmcp.ai/mcp
The last check completed an MCP handshake.
- Registry name
- ai.trendsmcp/competitor-tracking
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-03-26
- Handshake latency
- 120 ms
- Tools exposed
- Not measured yet
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- Brand and competitor trend volume over time, with growth signals. Free key at trendsmcp.ai
- Website
- https://trendsmcp.ai/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Handshake completed | 120 ms |
| 1 day ago | Handshake completed | 117 ms |
| 3 days ago | Handshake completed | 135 ms |
| 3 days ago | Handshake completed | 114 ms |
| 4 days ago | Handshake completed | 229 ms |
| 5 days ago | Handshake completed | 119 ms |
| 7 days ago | Handshake completed | 127 ms |
| 10 days ago | Handshake completed | 79 ms |
| 12 days ago | Handshake completed | 95 ms |
| 15 days ago | Handshake completed | 131 ms |
| 17 days ago | Handshake completed | 145 ms |
| 19 days ago | Handshake completed | 100 ms |
| 21 days ago | Handshake completed | 128 ms |
| 23 days ago | Handshake completed | 113 ms |
| 25 days ago | Handshake completed | 114 ms |
| 26 days ago | Handshake completed | 167 ms |
| 28 days ago | Handshake completed | 78 ms |
| 29 days ago | Handshake completed | 142 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 29 responding of 29.
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 Competitor Tracking Trends MCP and makes no claim about it beyond what these checks measured.