Remote MCP · Endpoint

Edifiable MCP server

No. Edifiable answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://edifiable.fr/mcp

The last check completed an MCP handshake.

Registry name
fr.edifiable/edifiable
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
76 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
French land-use plans (PLU): what a zone or a street allows, cited at the article. No key.
Listing
From the official MCP registry (active).
Recent checks of Edifiable
CheckedResultHandshake
1 hour agoHandshake completed76 ms
2 days agoHandshake completed67 ms
4 days agoHandshake completed45 ms
5 days agoHandshake completed44 ms
7 days agoHandshake completed67 ms
8 days agoHandshake completed265 ms
9 days agoHandshake completed38 ms
12 days agoHandshake completed33 ms
13 days agoHandshake completed75 ms
15 days agoHandshake completed49 ms
16 days agoHandshake completed71 ms
18 days agoHandshake completed45 ms
19 days agoHandshake completed60 ms
20 days agoHandshake completed48 ms
20 days agoHandshake completed40 ms
21 days agoHandshake completed36 ms
22 days agoHandshake completed111 ms

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

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