Remote MCP · Endpoint

Fr Judilibre MCP server

No. Fr Judilibre answered an MCP handshake 31 minutes ago.

UpLast checked 31 minutes ago

Server URL

https://gateway.pipeworx.io/fr-judilibre/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/fr-judilibre
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
55 ms
Tools exposed
47 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
French court decisions (Cour de cassation and the judicial courts under it) — search, read a…
Listing
From the official MCP registry (active).
Recent checks of Fr Judilibre
CheckedResultHandshake
31 minutes agoHandshake completed55 ms
3 days agoHandshake completed75 ms
13 days agoHandshake completed1.41 s
13 days agoHandshake completed1.24 s
15 days agoHandshake completed597 ms
16 days agoHandshake completed83 ms
17 days agoHandshake completed939 ms
18 days agoHandshake completed204 ms
18 days agoHandshake completed81 ms
20 days agoHandshake completed261 ms
23 days agoHandshake completed193 ms
25 days agoHandshake completed255 ms
28 days agoHandshake completed61 ms

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

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