Remote MCP · Endpoint

AI Rechtshulp MCP server

No. AI Rechtshulp answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://app.ai-rechtshulp.nl/mcp

The last check completed an MCP handshake.

Registry name
io.github.smrht/ai-rechtshulp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
523 ms
Tools exposed
16 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Search Dutch and EU case law with ECLI sources and verify quotes against the judgment.
Listing
From the official MCP registry (active).
Recent checks of AI Rechtshulp
CheckedResultHandshake
1 hour agoHandshake completed523 ms
3 days agoHandshake completed477 ms
12 days agoHandshake completed215 ms
13 days agoHandshake completed448 ms
15 days agoHandshake completed568 ms
15 days agoHandshake completed449 ms
17 days agoHandshake completed454 ms
18 days agoHandshake completed459 ms
18 days agoHandshake completed627 ms
20 days agoHandshake completed697 ms
22 days agoHandshake completed456 ms
25 days agoHandshake completed437 ms
27 days agoHandshake completed471 ms
29 days agoHandshake completed451 ms

The last 14 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 AI Rechtshulp and makes no claim about it beyond what these checks measured.