Remote MCP · Endpoint

Sigwren MCP server

No. Sigwren answered an MCP handshake 17 hours ago.

UpLast checked 17 hours ago

Server URL

https://mcp.sigwren.com/public

The last check completed an MCP handshake.

Registry name
com.sigwren/sigwren
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
235 ms
Tools exposed
11 tools
Uptime, last 30 days
100% from 12 checks
Described by its publisher as
Trail and ultra running: your Sigwren training, plus race courses, pacing and fuelling for anyone.
Listing
From the official MCP registry (active).
Recent checks of Sigwren
CheckedResultHandshake
17 hours agoHandshake completed235 ms
11 days agoHandshake completed206 ms
12 days agoHandshake completed419 ms
12 days agoHandshake completed280 ms
14 days agoHandshake completed214 ms
15 days agoHandshake completed176 ms
16 days agoHandshake completed214 ms
17 days agoHandshake completed217 ms
18 days agoHandshake completed243 ms
20 days agoHandshake completed499 ms
22 days agoHandshake completed177 ms
25 days agoHandshake completed268 ms

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

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