Remote MCP · Endpoint

Finished Listing: stage an empty room MCP server

No. Finished Listing: stage an empty room answered an MCP handshake 34 minutes ago.

UpLast checked 34 minutes ago

Server URL

https://finishedlisting.fernwaylabs.com/mcp

The last check completed an MCP handshake.

Registry name
com.fernwaylabs/finished-listing-stage
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
180 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 12 checks
Described by its publisher as
Virtual staging of one empty room from a public listing photo, labelled, original returned.
Listing
From the official MCP registry (active).
Recent checks of Finished Listing: stage an empty room
CheckedResultHandshake
34 minutes agoHandshake completed180 ms
3 days agoHandshake completed123 ms
13 days agoHandshake completed295 ms
13 days agoHandshake completed127 ms
15 days agoHandshake completed126 ms
16 days agoHandshake completed96 ms
17 days agoHandshake completed91 ms
18 days agoHandshake completed105 ms
18 days agoHandshake completed178 ms
20 days agoHandshake completed134 ms
22 days agoHandshake completed175 ms
25 days agoHandshake completed106 ms

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

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 Finished Listing: stage an empty room and makes no claim about it beyond what these checks measured.