Remote MCP · Endpoint

Estimatiz MCP server

No. Estimatiz answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://www.estimatiz.fr/api/mcp.php

The last check completed an MCP handshake.

Registry name
fr.estimatiz.www/estimatiz
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
290 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
French property estimates from DVF sales, with price range, limitations and a shareable report.
Listing
From the official MCP registry (active).
Recent checks of Estimatiz
CheckedResultHandshake
1 hour agoHandshake completed290 ms
3 days agoHandshake completed279 ms
13 days agoHandshake completed281 ms
14 days agoHandshake completed371 ms
15 days agoHandshake completed313 ms
16 days agoHandshake completed280 ms
18 days agoHandshake completed280 ms
18 days agoHandshake completed279 ms
19 days agoHandshake completed284 ms
21 days agoHandshake completed337 ms
22 days agoHandshake completed276 ms
25 days agoHandshake completed291 ms
27 days agoHandshake completed278 ms
30 days agoHandshake completed277 ms

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

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