Remote MCP · Endpoint

Lex-Ray MCP server

No. Lex-Ray answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://lexray.simmons-simmons.com/mcp/

The last check completed an MCP handshake.

Registry name
law.lexray/lexray
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
383 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Structured EU and UK legislation: public metadata, free sample articles, and entitled full text.
Website
https://lexray.simmons-simmons.com/gdpr/a5
Listing
From the official MCP registry (active).
Recent checks of Lex-Ray
CheckedResultHandshake
1 hour agoHandshake completed383 ms
1 day agoHandshake completed426 ms
3 days agoHandshake completed405 ms
5 days agoHandshake completed373 ms
8 days agoHandshake completed400 ms
10 days agoHandshake completed416 ms
12 days agoHandshake completed636 ms
14 days agoHandshake completed420 ms
16 days agoHandshake completed382 ms
18 days agoHandshake completed611 ms
20 days agoHandshake completed410 ms
22 days agoHandshake completed377 ms
23 days agoHandshake completed389 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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with Lex-Ray and makes no claim about it beyond what these checks measured.