Remote MCP · Endpoint

HomeMaster MCP server

No. HomeMaster answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://homemaster.co/mcp

The last check completed an MCP handshake.

Registry name
co.homemaster/homemaster
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
2.62 s
Tools exposed
7 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Home cleaning and aircon servicing in Singapore: coverage, open times, exact prices and booking.
Listing
From the official MCP registry (active).
Recent checks of HomeMaster
CheckedResultHandshake
1 hour agoHandshake completed2.62 s
2 days agoHandshake completed3.02 s
4 days agoHandshake completed3.73 s
6 days agoHandshake completed3.54 s
8 days agoHandshake completed3.48 s
10 days agoHandshake completed3.83 s
12 days agoHandshake completed3.42 s
14 days agoHandshake completed2.76 s
15 days agoHandshake completed368 ms
16 days agoHandshake completed294 ms
17 days agoHandshake completed277 ms
20 days agoHandshake completed381 ms
22 days agoHandshake completed272 ms
23 days agoHandshake completed324 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 HomeMaster and makes no claim about it beyond what these checks measured.