Remote MCP · Endpoint

Pagosa Forest Lodge MCP server

No. Pagosa Forest Lodge answered an MCP handshake 7 hours ago.

UpLast checked 7 hours ago

Server URL

https://pagosaforestlodge.com/mcp

The last check completed an MCP handshake.

Registry name
com.pagosaforestlodge/agent-booking
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
325 ms
Tools exposed
5 tools
Uptime, last 30 days
76.9% from 13 checks
Described by its publisher as
Pagosa Forest Lodge facts, live availability and quotes, and guest-reviewed Lodgify checkout.
Listing
From the official MCP registry (active).
Recent checks of Pagosa Forest Lodge
CheckedResultHandshake
7 hours agoHandshake completed325 ms
4 days agoHandshake completed175 ms
14 days agoFailed - the server returned an HTTP error—
15 days agoFailed - the server returned an HTTP error—
15 days agoFailed - the server returned an HTTP error—
17 days agoHandshake completed189 ms
18 days agoHandshake completed311 ms
19 days agoHandshake completed161 ms
20 days agoHandshake completed330 ms
21 days agoHandshake completed303 ms
23 days agoHandshake completed208 ms
26 days agoHandshake completed230 ms
28 days agoHandshake completed217 ms

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

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