Remote MCP · Endpoint

Ridgerunner MCP server

No. Ridgerunner answered an MCP handshake 6 hours ago.

UpLast checked 6 hours ago

Server URL

https://mcp.ridgerunner.com/mcp

The last check completed an MCP handshake.

Registry name
com.ridgerunner/outdoor-gear
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
61 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Search hunting, fishing, camping and outdoor gear from brands worldwide on Ridgerunner
Listing
From the official MCP registry (active).
Recent checks of Ridgerunner
CheckedResultHandshake
6 hours agoHandshake completed61 ms
9 days agoHandshake completed52 ms
10 days agoHandshake completed61 ms
11 days agoHandshake completed59 ms
12 days agoHandshake completed124 ms
14 days agoHandshake completed46 ms
15 days agoHandshake completed58 ms
15 days agoHandshake completed74 ms
17 days agoHandshake completed63 ms
19 days agoHandshake completed62 ms
22 days agoHandshake completed61 ms
24 days agoHandshake completed103 ms
26 days agoHandshake completed66 ms
28 days agoHandshake completed122 ms

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

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