Remote MCP · Endpoint

com.wildernesstimes/checklists MCP server

No. com.wildernesstimes/checklists answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.wildernesstimes.com/mcp

The last check completed an MCP handshake.

Registry name
com.wildernesstimes/checklists
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
90 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Wilderness Times packing checklists, 350+ rated tents and gear buying guides. Free, no signup.
Listing
From the official MCP registry (active).
Recent checks of com.wildernesstimes/checklists
CheckedResultHandshake
1 hour agoHandshake completed90 ms
2 days agoHandshake completed138 ms
5 days agoHandshake completed107 ms
7 days agoHandshake completed129 ms
9 days agoHandshake completed350 ms
11 days agoHandshake completed127 ms
13 days agoHandshake completed126 ms
15 days agoHandshake completed129 ms
17 days agoHandshake completed176 ms
19 days agoHandshake completed99 ms
20 days agoHandshake completed129 ms
21 days agoHandshake completed112 ms
22 days agoHandshake completed385 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 com.wildernesstimes/checklists and makes no claim about it beyond what these checks measured.