Remote MCP · Endpoint

Nl Rechtspraak MCP server

No. Nl Rechtspraak answered an MCP handshake 4 days ago.

UpLast checked 4 days ago

Server URL

https://gateway.pipeworx.io/nl-rechtspraak/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/nl-rechtspraak
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
117 ms
Tools exposed
46 tools
Uptime, last 30 days
92.9% from 14 checks
Described by its publisher as
Netherlands court decisions (uitspraken en conclusies) — search by court, legal domain and date…
Listing
From the official MCP registry (active).
Recent checks of Nl Rechtspraak
CheckedResultHandshake
4 days agoHandshake completed117 ms
4 days agoHandshake completed233 ms
5 days agoHandshake completed886 ms
7 days agoHandshake completed873 ms
8 days agoHandshake completed817 ms
9 days agoHandshake completed424 ms
10 days agoHandshake completed730 ms
11 days agoHandshake completed163 ms
12 days agoHandshake completed1.03 s
15 days agoHandshake completed107 ms
18 days agoHandshake completed141 ms
20 days agoHandshake completed975 ms
22 days agoHandshake completed2.57 s
24 days agoFailed - the request timed out—

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

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