Remote MCP · Endpoint

CaLesVaut MCP server

No. CaLesVaut answered an MCP handshake 53 minutes ago.

UpLast checked 53 minutes ago

Server URL

https://calesvaut.fr/mcp

The last check completed an MCP handshake.

Registry name
fr.calesvaut/calesvaut
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
413 ms
Tools exposed
11 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Is this listing too expensive? French property sales (DVF), crime, rents, risks, schools
Listing
From the official MCP registry (active).
Recent checks of CaLesVaut
CheckedResultHandshake
53 minutes agoHandshake completed413 ms
3 days agoHandshake completed314 ms
12 days agoHandshake completed365 ms
13 days agoHandshake completed143 ms
15 days agoHandshake completed161 ms
15 days agoHandshake completed353 ms
17 days agoHandshake completed448 ms
18 days agoHandshake completed344 ms
18 days agoHandshake completed322 ms
20 days agoHandshake completed292 ms
22 days agoHandshake completed167 ms
25 days agoHandshake completed376 ms
27 days agoHandshake completed368 ms
29 days agoHandshake completed351 ms

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

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