Remote MCP · Endpoint

Wehome MCP server

No. Wehome answered an MCP handshake 20 hours ago.

UpLast checked 20 hours ago

Server URL

https://www.wehome.me/mcp

The last check completed an MCP handshake.

Registry name
me.wehome/stays
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
592 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 6 checks
Described by its publisher as
Search homestays in South Korea by area, dates, guests, and budget, with links to book on Wehome.
Listing
From the official MCP registry (active).
Recent checks of Wehome
CheckedResultHandshake
20 hours agoHandshake completed592 ms
11 days agoHandshake completed540 ms
11 days agoHandshake completed546 ms
12 days agoHandshake completed527 ms
14 days agoHandshake completed586 ms
15 days agoHandshake completed550 ms

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

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