Remote MCP · Endpoint

com.la-truite/resort MCP server

No. com.la-truite/resort answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://www.la-truite.com/mcp/

The last check completed an MCP handshake.

Registry name
com.la-truite/resort
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
415 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Live availability and commission-free booking links for resort La Truite d'Argent, Belgian Ardennes
Listing
From the official MCP registry (active).
Recent checks of com.la-truite/resort
CheckedResultHandshake
1 hour agoHandshake completed415 ms
2 days agoHandshake completed306 ms
4 days agoHandshake completed316 ms
6 days agoHandshake completed303 ms
8 days agoHandshake completed358 ms
10 days agoHandshake completed312 ms
12 days agoHandshake completed323 ms
14 days agoHandshake completed308 ms
15 days agoHandshake completed299 ms
16 days agoHandshake completed310 ms
17 days agoHandshake completed300 ms
20 days agoHandshake completed272 ms
22 days agoHandshake completed297 ms
23 days agoHandshake completed356 ms

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

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