Remote MCP · Endpoint

France Dvf MCP server

No. France Dvf answered an MCP handshake 12 minutes ago.

UpLast checked 12 minutes ago

Server URL

https://gateway.pipeworx.io/france-dvf/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/france-dvf
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
98 ms
Tools exposed
47 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
france-dvf — France's official property-transfer price records ('Demandes de valeurs foncieres'…
Listing
From the official MCP registry (active).
Recent checks of France Dvf
CheckedResultHandshake
12 minutes agoHandshake completed98 ms
9 days agoHandshake completed111 ms
9 days agoHandshake completed54 ms
11 days agoHandshake completed118 ms
12 days agoHandshake completed95 ms
13 days agoHandshake completed61 ms
14 days agoHandshake completed90 ms
15 days agoHandshake completed236 ms
16 days agoHandshake completed69 ms
19 days agoHandshake completed225 ms
22 days agoHandshake completed94 ms
24 days agoHandshake completed364 ms
26 days agoHandshake completed93 ms
28 days agoHandshake completed961 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 France Dvf and makes no claim about it beyond what these checks measured.