Remote MCP · Endpoint
WireTensors MCP server
No. WireTensors answered an MCP handshake 2 hours ago.
UpLast checked 2 hours ago
Server URL
https://wiretensors.ai/mcp
The last check completed an MCP handshake.
- Registry name
- ai.wiretensors/wiretensors
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 256 ms
- Tools exposed
- 6 tools
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- Neutral, verified AI tool reviews — search, compare and get recommendations across 260+ tools.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Handshake completed | 256 ms |
| 2 days ago | Handshake completed | 164 ms |
| 4 days ago | Handshake completed | 178 ms |
| 6 days ago | Handshake completed | 150 ms |
| 7 days ago | Handshake completed | 157 ms |
| 9 days ago | Handshake completed | 154 ms |
| 10 days ago | Handshake completed | 46 ms |
| 11 days ago | Handshake completed | 228 ms |
| 14 days ago | Handshake completed | 45 ms |
| 15 days ago | Handshake completed | 161 ms |
| 17 days ago | Handshake completed | 210 ms |
| 18 days ago | Handshake completed | 140 ms |
| 19 days ago | Handshake completed | 133 ms |
| 20 days ago | Handshake completed | 152 ms |
| 21 days ago | Handshake completed | 153 ms |
| 22 days ago | Handshake completed | 173 ms |
| 23 days ago | Handshake completed | 209 ms |
| 24 days ago | Handshake completed | 244 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 WireTensors and makes no claim about it beyond what these checks measured.