Remote MCP · Endpoint

Xome MCP server

No. Xome answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://gateway.pipeworx.io/xome/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/xome
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
92 ms
Tools exposed
42 tools
Uptime, last 30 days
94.1% from 17 checks
Described by its publisher as
Xome MCP — US residential foreclosure/REO/short-sale auction calendar and
Listing
From the official MCP registry (active).
Recent checks of Xome
CheckedResultHandshake
1 hour agoHandshake completed92 ms
2 days agoHandshake completed75 ms
4 days agoFailed - the request timed out—
6 days agoHandshake completed68 ms
7 days agoHandshake completed263 ms
8 days agoHandshake completed116 ms
9 days agoHandshake completed74 ms
12 days agoHandshake completed39 ms
14 days agoHandshake completed57 ms
15 days agoHandshake completed146 ms
17 days agoHandshake completed38 ms
18 days agoHandshake completed51 ms
19 days agoHandshake completed39 ms
20 days agoHandshake completed53 ms
21 days agoHandshake completed38 ms
21 days agoHandshake completed174 ms
23 days agoHandshake completed43 ms

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

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