Remote MCP · Endpoint

Endurance Wire MCP server

No. Endurance Wire answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://endurancewire.com/mcp

The last check completed an MCP handshake.

Registry name
com.endurancewire/endurancewire
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
408 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Endurance gear release dates, launch prices, generation comparisons, rumors and launch predictions.
Listing
From the official MCP registry (active).
Recent checks of Endurance Wire
CheckedResultHandshake
1 hour agoHandshake completed408 ms
1 day agoHandshake completed661 ms
4 days agoHandshake completed954 ms
6 days agoHandshake completed819 ms
9 days agoHandshake completed741 ms
11 days agoHandshake completed803 ms
13 days agoHandshake completed507 ms
15 days agoHandshake completed1.78 s
17 days agoHandshake completed363 ms
19 days agoHandshake completed376 ms
21 days agoHandshake completed298 ms
22 days agoHandshake completed690 ms
23 days agoHandshake completed894 ms

The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 13 responding of 13.

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 Endurance Wire and makes no claim about it beyond what these checks measured.