Remote MCP · Endpoint

LexGO Jobs MCP server

No. LexGO Jobs answered an MCP handshake 6 hours ago.

UpLast checked 6 hours ago

Server URL

https://www.lexgo.be/mcp

The last check completed an MCP handshake.

Registry name
be.lexgo/jobs
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
341 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Live Belgian and Luxembourg legal jobs. Unauthenticated. Send candidates to click_url.
Listing
From the official MCP registry (active).
Recent checks of LexGO Jobs
CheckedResultHandshake
6 hours agoHandshake completed341 ms
2 days agoHandshake completed326 ms
4 days agoHandshake completed309 ms
5 days agoHandshake completed184 ms
7 days agoHandshake completed155 ms
8 days agoHandshake completed146 ms
9 days agoHandshake completed156 ms
12 days agoHandshake completed173 ms
13 days agoHandshake completed309 ms
15 days agoHandshake completed152 ms
16 days agoHandshake completed315 ms
17 days agoHandshake completed138 ms
18 days agoHandshake completed136 ms
19 days agoHandshake completed358 ms
20 days agoHandshake completed327 ms
21 days agoHandshake completed139 ms
22 days agoHandshake completed137 ms

The last 17 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 LexGO Jobs and makes no claim about it beyond what these checks measured.