Remote MCP · Endpoint

theRoom MCP server

No. theRoom answered an MCP handshake 20 minutes ago.

UpLast checked 20 minutes ago

Server URL

https://luizaurio.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.luizaurio/theroom
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
80 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Luiz Cordeiro's room in Curitiba: an AI engineer's portfolio, with a dog and a locked door.
Listing
From the official MCP registry (active).
Recent checks of theRoom
CheckedResultHandshake
20 minutes agoHandshake completed80 ms
3 days agoHandshake completed102 ms
14 days agoHandshake completed101 ms
14 days agoHandshake completed161 ms
15 days agoHandshake completed927 ms
16 days agoHandshake completed189 ms
18 days agoHandshake completed169 ms
18 days agoHandshake completed824 ms
19 days agoHandshake completed105 ms
21 days agoHandshake completed111 ms
23 days agoHandshake completed144 ms
25 days agoHandshake completed102 ms
28 days agoHandshake completed105 ms

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

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