Remote MCP · Endpoint

Laudex MCP server

No. Laudex answered an MCP handshake 3 hours ago.

UpLast checked 3 hours ago

Server URL

https://laudex.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.laudex/laudex
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.57 s
Tools exposed
3 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Find MCP servers, APIs, tools and skills by intent. Free key: POST /api/agents/register
Listing
From the official MCP registry (active).
Recent checks of Laudex
CheckedResultHandshake
3 hours agoHandshake completed1.57 s
9 days agoHandshake completed70 ms
10 days agoHandshake completed163 ms
11 days agoHandshake completed110 ms
12 days agoHandshake completed134 ms
14 days agoHandshake completed85 ms
14 days agoHandshake completed131 ms
15 days agoHandshake completed82 ms
17 days agoHandshake completed103 ms
19 days agoHandshake completed47 ms
21 days agoHandshake completed129 ms
24 days agoHandshake completed118 ms
26 days agoHandshake completed68 ms
28 days agoCredentials required—

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

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