Remote MCP · Endpoint

lurq MCP server

No. lurq answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

https://api.lurq.run/mcp

The last check completed an MCP handshake.

Registry name
io.github.jadenryu/lurq
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
32 ms
Tools exposed
16 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Verify npm packages before your AI agent installs them: hallucinations, advisories, API drift.
Listing
From the official MCP registry (active).
Recent checks of lurq
CheckedResultHandshake
5 hours agoHandshake completed32 ms
2 days agoHandshake completed36 ms
4 days agoHandshake completed37 ms
5 days agoHandshake completed25 ms
7 days agoHandshake completed35 ms
8 days agoHandshake completed24 ms
9 days agoHandshake completed41 ms
12 days agoHandshake completed31 ms
13 days agoHandshake completed23 ms
15 days agoHandshake completed26 ms
16 days agoHandshake completed25 ms
17 days agoHandshake completed28 ms
19 days agoHandshake completed23 ms
19 days agoHandshake completed24 ms
20 days agoHandshake completed25 ms
21 days agoHandshake completed127 ms
22 days agoHandshake completed196 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 lurq and makes no claim about it beyond what these checks measured.