Remote MCP · Endpoint

RegusciLabs Innovation Lab MCP server

No. RegusciLabs Innovation Lab answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.reguscilabs.com/mcp

The last check completed an MCP handshake.

Registry name
com.reguscilabs.www/innovation-lab
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
333 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Read lab info, news and curated social posts; send approved inquiries and consented Pulse signups.
Listing
From the official MCP registry (active).
Recent checks of RegusciLabs Innovation Lab
CheckedResultHandshake
1 hour agoHandshake completed333 ms
22 hours agoHandshake completed175 ms
1 day agoHandshake completed238 ms
2 days agoHandshake completed175 ms
4 days agoHandshake completed201 ms
7 days agoHandshake completed229 ms
9 days agoHandshake completed293 ms
12 days agoHandshake completed166 ms
14 days agoHandshake completed254 ms
16 days agoHandshake completed210 ms
18 days agoHandshake completed269 ms
20 days agoHandshake completed156 ms
22 days agoHandshake completed168 ms
24 days agoHandshake completed263 ms

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

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