Remote MCP · Endpoint

RegusciLabs Documentation MCP server

No. RegusciLabs Documentation answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.reguscilabs.com/docs

The last check completed an MCP handshake.

Registry name
com.reguscilabs.www/documentation
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
247 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Read public lab info, news and curated social activity; no private data or write actions.
Listing
From the official MCP registry (active).
Recent checks of RegusciLabs Documentation
CheckedResultHandshake
1 hour agoHandshake completed247 ms
22 hours agoHandshake completed179 ms
1 day agoHandshake completed386 ms
2 days agoHandshake completed1.43 s
4 days agoHandshake completed280 ms
7 days agoHandshake completed156 ms
9 days agoHandshake completed172 ms
12 days agoHandshake completed192 ms
14 days agoHandshake completed270 ms
16 days agoHandshake completed182 ms
18 days agoHandshake completed270 ms
20 days agoHandshake completed180 ms
22 days agoHandshake completed155 ms
23 days agoHandshake completed245 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 Documentation and makes no claim about it beyond what these checks measured.