Remote MCP · Endpoint

Code civil (France) MCP server

No. Code civil (France) answered an MCP handshake 2 days ago.

UpLast checked 2 days ago

Server URL

https://mcp.arxo.io/mcp/code-civil

The last check completed an MCP handshake.

Registry name
io.arxo/code-civil
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
307 ms
Tools exposed
21 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
French Civil Code (LEGI) as executable rules: facts and a legal date in, answers with grounds out
Listing
From the official MCP registry (active).
Recent checks of Code civil (France)
CheckedResultHandshake
2 days agoHandshake completed307 ms
3 days agoHandshake completed388 ms
3 days agoHandshake completed305 ms
5 days agoHandshake completed300 ms
6 days agoHandshake completed307 ms
7 days agoHandshake completed308 ms
8 days agoHandshake completed803 ms
9 days agoHandshake completed326 ms
11 days agoHandshake completed315 ms
13 days agoHandshake completed323 ms
16 days agoHandshake completed319 ms
18 days agoHandshake completed341 ms
21 days agoHandshake completed309 ms
22 days agoHandshake completed310 ms
25 days agoHandshake completed101 ms

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

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 Code civil (France) and makes no claim about it beyond what these checks measured.