Remote MCP · Endpoint

Lucernel MCP server

No. Lucernel answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

https://lucernel.com/mcp

The last check completed an MCP handshake.

Registry name
com.lucernel/lucernel
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
76 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Public Lucernel apps and articles: list, search, and analyze published content.
Website
https://lucernel.com/docs/mcp
Listing
From the official MCP registry (active).
Recent checks of Lucernel
CheckedResultHandshake
5 hours agoHandshake completed76 ms
9 days agoHandshake completed91 ms
10 days agoHandshake completed80 ms
11 days agoHandshake completed123 ms
12 days agoHandshake completed91 ms
14 days agoHandshake completed106 ms
14 days agoHandshake completed89 ms
15 days agoHandshake completed75 ms
17 days agoHandshake completed113 ms
19 days agoHandshake completed216 ms
21 days agoHandshake completed495 ms
24 days agoHandshake completed106 ms
26 days agoHandshake completed98 ms
28 days agoHandshake completed108 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.

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