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://www.reguscilabs.com/api/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
261 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Read lab information, submit approved inquiries, and subscribe to Pulse with explicit consent.
Listing
From the official MCP registry (active).
Recent checks of RegusciLabs Innovation Lab
CheckedResultHandshake
1 hour agoHandshake completed261 ms
2 days agoHandshake completed549 ms
4 days agoHandshake completed246 ms
6 days agoHandshake completed168 ms
8 days agoHandshake completed246 ms
10 days agoHandshake completed249 ms
12 days agoHandshake completed148 ms
14 days agoHandshake completed203 ms
16 days agoHandshake completed165 ms
17 days agoHandshake completed229 ms
18 days agoHandshake completed147 ms
21 days agoHandshake completed152 ms
22 days agoHandshake completed162 ms
24 days agoHandshake completed308 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.