Remote MCP · Endpoint
RivalSweeper Signals MCP server
No. RivalSweeper Signals answered an MCP handshake 2 hours ago.
UpLast checked 2 hours ago
Server URL
https://mcp.rivalsweeper.com/mcp
The last check completed an MCP handshake.
- Registry name
- com.rivalsweeper/signals
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 338 ms
- Tools exposed
- 37 tools
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- 37 eCommerce competitor-intel tools: prices, promos, ads, AI visibility. Plan-included or prepaid.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Handshake completed | 338 ms |
| 1 day ago | Handshake completed | 326 ms |
| 2 days ago | Handshake completed | 358 ms |
| 3 days ago | Handshake completed | 334 ms |
| 4 days ago | Handshake completed | 356 ms |
| 5 days ago | Handshake completed | 387 ms |
| 7 days ago | Handshake completed | 374 ms |
| 9 days ago | Handshake completed | 415 ms |
| 12 days ago | Handshake completed | 308 ms |
| 14 days ago | Handshake completed | 970 ms |
| 16 days ago | Handshake completed | 304 ms |
| 18 days ago | Handshake completed | 303 ms |
| 20 days ago | Handshake completed | 309 ms |
| 22 days ago | Handshake completed | 310 ms |
| 25 days ago | Handshake completed | 294 ms |
| 26 days ago | Handshake completed | 340 ms |
| 27 days ago | Handshake completed | 386 ms |
| 29 days ago | Handshake completed | 364 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 RivalSweeper Signals and makes no claim about it beyond what these checks measured.