Remote MCP · Endpoint

Luma MCP server

No. Luma answered an MCP handshake 42 minutes ago.

UpLast checked 42 minutes ago

Server URL

https://gateway.pipeworx.io/luma/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/luma
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
70 ms
Tools exposed
48 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Luma (lu.ma) event discovery.
Listing
From the official MCP registry (active).
Recent checks of Luma
CheckedResultHandshake
42 minutes agoHandshake completed70 ms
8 days agoHandshake completed96 ms
9 days agoHandshake completed83 ms
11 days agoHandshake completed72 ms
12 days agoHandshake completed93 ms
13 days agoHandshake completed87 ms
14 days agoHandshake completed172 ms
15 days agoHandshake completed152 ms
16 days agoHandshake completed303 ms
19 days agoHandshake completed58 ms
22 days agoHandshake completed83 ms
24 days agoHandshake completed503 ms
26 days agoHandshake completed127 ms
28 days agoHandshake completed97 ms

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

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