Remote MCP · Endpoint

Chaletiste MCP server

No. Chaletiste answered an MCP handshake 3 hours ago.

UpLast checked 3 hours ago

Server URL

https://chaletiste.fr/api/mcp

The last check completed an MCP handshake.

Registry name
fr.chaletiste/chaletiste
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
472 ms
Tools exposed
12 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Compare French wooden kit cabins: prices, sizes, assembly time, delivery, budget and permits.
Listing
From the official MCP registry (active).
Recent checks of Chaletiste
CheckedResultHandshake
3 hours agoHandshake completed472 ms
2 days agoHandshake completed463 ms
4 days agoHandshake completed435 ms
6 days agoHandshake completed206 ms
8 days agoHandshake completed264 ms
10 days agoHandshake completed402 ms
11 days agoHandshake completed380 ms
13 days agoHandshake completed1.07 s
13 days agoHandshake completed576 ms
16 days agoHandshake completed570 ms
18 days agoHandshake completed498 ms
19 days agoHandshake completed433 ms
21 days agoHandshake completed425 ms
22 days agoHandshake completed388 ms
23 days agoHandshake completed706 ms

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

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