Remote MCP · Endpoint

Socials Homes Docs MCP server

No. Socials Homes Docs answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://www.socials.homes/mcp/docs

The last check completed an MCP handshake.

Registry name
homes.socials/socials-homes-docs
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
73 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
How Socials Homes works: pricing, FAQ, a terms summary and housing guides for people moving abroad.
Listing
From the official MCP registry (active).
Recent checks of Socials Homes Docs
CheckedResultHandshake
1 hour agoHandshake completed73 ms
1 day agoHandshake completed225 ms
3 days agoHandshake completed125 ms
3 days agoHandshake completed118 ms
4 days agoHandshake completed149 ms
5 days agoHandshake completed165 ms
7 days agoHandshake completed90 ms
10 days agoHandshake completed124 ms
12 days agoHandshake completed70 ms
15 days agoHandshake completed167 ms
17 days agoHandshake completed226 ms
19 days agoHandshake completed333 ms
21 days agoHandshake completed44 ms

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

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