Remote MCP · Endpoint

Chaletiste MCP server

No. Chaletiste answered an MCP handshake 1 hour ago.

UpLast checked 1 hour 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
215 ms
Tools exposed
12 tools
Uptime, last 30 days
100% from 14 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
1 hour agoHandshake completed215 ms
9 days agoHandshake completed594 ms
10 days agoHandshake completed577 ms
11 days agoHandshake completed522 ms
12 days agoHandshake completed398 ms
14 days agoHandshake completed413 ms
14 days agoHandshake completed479 ms
15 days agoHandshake completed488 ms
17 days agoHandshake completed530 ms
19 days agoHandshake completed510 ms
21 days agoHandshake completed472 ms
24 days agoHandshake completed443 ms
26 days agoHandshake completed472 ms
28 days agoHandshake completed463 ms

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

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.